cancel
Showing results for 
Search instead for 
Did you mean: 

Problem in JCO Commit Block

Former Member
0 Kudos

I am having a scenario where in, I am executing multiple BAPIs in sequence. In this I am executing BAPI_GOODSMVT_CREATE and then Using JCO commit block to commit. This BAPI is returning Delivery number, same delivery number I am passing to custom BAPI to pack HUID in sequence.

Now, I am able to generate Delivery number but generated delivery number is not existing in SAP. Commit is executed successfully after BAPI_GOODSMVT_CREATE bapi execution.But custom BAPI throws as error as Delivery number doesn't exist. Can anyone suggest solution for this problem.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Try a pause action block. Sometimes a BAPI can return but the record is still locked or processing for a little bit in SAP. Even after a commit.

Former Member
0 Kudos

I have configured Pause block and increased delay to 10000MS. But no result.

Former Member
0 Kudos

Are you doing a EndSession after commit , then pause and call the second BAPI(using the new JCO Interface I presume.).? If not then give it a try.

Former Member
0 Kudos

Hey!!! I am able to execute transaction succesfully without doing any changes to my earlier transaction. I just changed Material used to generate delivery, it is working fine now. Only for one particular material transaction returns error, delivery is getting returned by BAPI, but delivery is not created in SAP. Any idea, what may be the problem??

Former Member
0 Kudos

Can't say. How's the behavior in SAP, for that material?

Former Member
0 Kudos

try putting in a PAUSE action before calling the second BAPI.