Problem with BAPI_TRANSACTION_COMMIT

[former_member431412]

I am using the FM BAPI_ALM_ORDER_MAINTAIN. This FM is a RFC. When I execute BAPI_ALM_ORDER_MAINTAIN, I have confirmed that the return information indicates success. When I execute the BAPI_TRANSACTION_COMMIT, the FM terminiates witha short dump

Error analysis

A RAISE statement in the program "SAPLCOZV" raised the excepti

condition "DUMP_STATUS_INCONSYSTENCY_FRE".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

-

To make this even more confusing, I have a different FM (Not an RFC) that uses the same two FM's with the same data. When I run this FM, I get no error and the update is succesful.

Any help would be greatly appreciated.

[former_member431412]

I found the coding problem. Howver, I think SAP should fix the Transaction commit so it handles errors appropriately.

[Former Member]

Can you please elaborate the code you have fixed, as we have encountered similar issue.

Regards

[Former Member]

Dear Scott,

Can you please let me know the solution for this issue, i am also facing the same problem for iw21.

Thanks in Advance,

Regards,

Syed Taj

[former_member431412]

There was a problem with the order where one of the phase indicators in AUFK (PHAS0, PHAS1, PHAS2, PHAS3) and AFIH-IPHAS were not showing the same status. I believe in oru case,AUFK-PHAS0 = X(CRTD) and AFIH-IPHAS = '2' (Released)

If your problem is similar, be sure to check JEST to see what status the order is in.

We wrote a program to update AUFK=PHAS* and AFIH-IPHAS to match what was indicated in JEST.

I hope this helps you. feel free to ask more questions if needed

Scott