topic Re: BDC Commit work problem in Application Development and Automation Discussions

BDC Commit work problem

Former Member — Thu, 09 Jun 2016 06:40:08 GMT

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??

Re: BDC Commit work problem

Sandra_Rossi — Thu, 09 Jun 2016 10:29:52 GMT

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'.

Re: BDC Commit work problem

Former Member — Thu, 09 Jun 2016 10:40:32 GMT

I am using CALL TRANSACTION method. I am not using "options from" keyword.

Re: BDC Commit work problem

Sandra_Rossi — Thu, 09 Jun 2016 11:20:53 GMT

Do use "options from" keyword -> more information in the ABAP documentation.

Re: BDC Commit work problem

Sandra_Rossi — Thu, 09 Jun 2016 11:22:42 GMT

But I have no idea why it works in development.

Re: BDC Commit work problem

pranay570708 — Thu, 09 Jun 2016 11:42:21 GMT

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.

Re: BDC Commit work problem

Former Member — Thu, 09 Jun 2016 12:22:15 GMT

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?

Re: BDC Commit work problem

Former Member — Thu, 09 Jun 2016 12:43:24 GMT

I used " options from" but still it dint work.

Re: BDC Commit work problem

pranay570708 — Thu, 09 Jun 2016 12:51:49 GMT

Instead of changing batch user id, ask your BASIS team to provide necessary authorization to batch user id same as development system.

Re: BDC Commit work problem

Sandra_Rossi — Thu, 09 Jun 2016 13:44:26 GMT

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?

Re: BDC Commit work problem

Former Member — Thu, 09 Jun 2016 16:29:16 GMT

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!

Re: BDC Commit work problem

Former Member — Thu, 09 Jun 2016 16:32:57 GMT

"SAP_WAPI_CREATE_EVENT" this FM is not getting called in Dev system. The customer configured it in quality and not in Dev.