‎2016 Jun 09 7:40 AM
Hi,
I am checking one BDC for posting document in tcode F-32. The message "Document posted" has been called after the "Commit work and wait" statement (SAP Std report statement). But when I execute the transaction BDC not going forward after the "Commit work" statement, it not executing the code. It is working fine in development system but not working in quality.
Can anybody tell me why it is happening??
‎2016 Jun 09 11:29 AM
That's a frequent issue. Is the BDC done via a batch input session (SM35) or via a CALL TRANSACTION in a custom ABAP program?
In the second case, you may run it with "OPTIONS FROM" keyword followed by a structure with component RACOMMIT (continue after commit) to be set to 'X'.
‎2016 Jun 09 11:29 AM
That's a frequent issue. Is the BDC done via a batch input session (SM35) or via a CALL TRANSACTION in a custom ABAP program?
In the second case, you may run it with "OPTIONS FROM" keyword followed by a structure with component RACOMMIT (continue after commit) to be set to 'X'.
‎2016 Jun 09 11:40 AM
I am using CALL TRANSACTION method. I am not using "options from" keyword.
‎2016 Jun 09 12:20 PM
Do use "options from" keyword -> more information in the ABAP documentation.
‎2016 Jun 09 1:43 PM
‎2016 Jun 09 2:44 PM
Based on your initial assumption <not going forward after the "Commit work" statement>, I assumed you did a debug step by step, so you probably noticed that after the commit work, SAP did jump right after your CALL TRANSACTION. The only case this situation may arise is the consequence of using CALL TRANSACTION without RACOMMIT = 'X'. Could you post your modified code, just to make sure you did it correctly, please?
‎2016 Jun 09 5:29 PM
Hi Sandra,
It worked with "options with". I dint activate the FM after I changed the code(my mistake the previous time). Thanks a ton!
‎2016 Jun 09 12:22 PM
‎2016 Jun 09 5:32 PM
"SAP_WAPI_CREATE_EVENT" this FM is not getting called in Dev system. The customer configured it in quality and not in Dev.
‎2016 Jun 09 12:42 PM
Hi Sravani,
The problem might be with authorizaion on the BATCH userid that is used to run the job in the production system. The batch userid will have the correct authority to perform updates in the development that's why it works there.
‎2016 Jun 09 1:22 PM
Can we change the batch user id. Actually the commit statement is inside "SAP_WAPI_CREATE_EVENT". if yes, what is the right way to resolve the issue?
‎2016 Jun 09 1:51 PM
Instead of changing batch user id, ask your BASIS team to provide necessary authorization to batch user id same as development system.