topic Re: processing happens only in debug mode. in Application Development and Automation Discussions

processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 05:18:51 GMT

Hi,

I am calling an RFC enabled FM BAPI_ALM_NOTIF_DATA_MODIFY and BAPI_ALM_NOTIF_SAVE to modify the data of a notification. These function modules are called within another FM which is also a RFC called in background as a separate task. The problem here is that, the data gets modified fine only when I am in the debugging mode and execute it. But if I execute without going to the debug mode, I cannot modify the notification data. Kindly suggest why this is happening and what the solution is. Thanks

Re: processing happens only in debug mode.

lijisusan_mathews — Thu, 13 Oct 2011 05:21:04 GMT

Trying calling a wait for 2 sec and commit and then try

Re: processing happens only in debug mode.

kesavadas_thekkillath — Thu, 13 Oct 2011 05:22:05 GMT

have you called BAPI_TRANSACTION_COMMIT too ?

Kesav

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 05:31:47 GMT

Hi,

I have tried the wait option but doesn't work. I do not think I can use a commit statement because the Function module inside which I am calling these 2 FMs is inturn being called within an enhancement section. This main FM is called in background task as a separate unit. Can I use a commit work inside such a FM inspite of the fact that it is called inside an enhancement section?

Re: processing happens only in debug mode.

lijisusan_mathews — Thu, 13 Oct 2011 05:38:30 GMT

just call BAPI_TRANSACTION_COMMIT after the FM

Re: processing happens only in debug mode.

kesavadas_thekkillath — Thu, 13 Oct 2011 05:39:01 GMT

Oh Sorry for the suggestion !!! Didnt get your question properly.


This main FM is called in background task as a separate unit

Does this enhancement gets triggered after the actual transactional flow, i.e actual commit of the transaction ?

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 05:42:49 GMT

Hi Smitha,

According to the BAPI documentation Commit work BAPI is required.

Try calling the BAPI in Update task.

Thanks,

Anmol.

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 05:47:08 GMT

Yes there is a function module inside the enhancement section which does the save of the order. When i checked in debug mode, I found that the main FM gets triggered as soon as the order save FM is executed. And I believe that there is a commit work inside this order save FM. Is there any other way I can run around this without using a commit work?

Re: processing happens only in debug mode.

kesavadas_thekkillath — Thu, 13 Oct 2011 05:50:33 GMT


And I believe that there is a commit work inside this order save FM

If your functions are gettign called after the actual commit work of the transaction then a commit work is required for your operations else try to perform your operations in background task before tha actual commit of the transaction.

Kesav

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 06:01:17 GMT

Ok here is a brief decsription of what I am actually doing. I have an enhancement section where the order save happens. Just before the order save FM, I am calling a custom FM which is RFC enabled. I call this FM in background task as a separate unit. Inside this FM, I am calling NOTIF_MODIFY and NOTIF_SAVE FMs. One more thing I am doing here is, calling of another FM (STATUS_CHANGE_INTERN) to change the notification status. This is happening perfectly fine even when I am not using any commit work. The only problem is with NOTIF_DATA_MODIFY. If commit work was the solution then why is it working fine in the debug mode and why is the notif status getting updated? There should be some other reason for this. Is it the way I am calling these 2 FMs. Both BAPI_ALM_NOTIF_DATA_MODIFY and BAPI_ALM_NOTIF_SAVE are RFCs. Is there a specific way I have to call these FMs?

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 06:02:38 GMT

One other thing to add to this is that, I have tried calling these 2 FMs using a background task. But still the same problem.

Re: processing happens only in debug mode.

kesavadas_thekkillath — Thu, 13 Oct 2011 06:04:58 GMT


If commit work was the solution then why is it working fine in the debug mode and why is the notif status getting updated?

Commit happens implicitly in each steps while debugging.

Note that RFC called as background task only gets executed when the comit work gets triggered, this is the reason i asked that whether your code is written after or before the actual commit of the transaction.

Kesav

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 06:05:16 GMT

hi,

Bapi_commit_transaction is a function module as well and you can use it with in your function module if not.

you can write an executable program and can write you bapi_commit_transaction in the that executable program and can use call transaction 'ztcode'.

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 06:09:41 GMT

I have written the background task FM before the order save FM which does the commit work. So what should I do to overcome this problem of execution happening only in debug mode?

Re: processing happens only in debug mode.

kesavadas_thekkillath — Thu, 13 Oct 2011 06:14:10 GMT

What is the standard fm called by the transaction and the place where you have applied your enhancement ? let me check it

Kesav

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 06:18:48 GMT

Within the standar include LCOIHF2V, there is an exhancement section called ENHANCEMENT-SECTION FCODE_BU2_04 SPOTS ES_SAPLCOIH. I am calling my RFC FM just before CO_ZV_ORDER_POST.

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 06:19:28 GMT

Within the standard include LCOIHF2V, there is an exhancement section called ENHANCEMENT-SECTION FCODE_BU2_04 SPOTS ES_SAPLCOIH. I am calling my RFC FM just before CO_ZV_ORDER_POST.

Re: processing happens only in debug mode.

kesavadas_thekkillath — Thu, 13 Oct 2011 06:55:44 GMT

Hi,

I think so your custom result is overwritten by the actual function in the queue . So you have to add you code just before the actual commit work of the transaction. in debugging mode may be your custom code executes first and the data is immediately replicated, did you check hitting f8 in debugiing mode after your code gets executed. Verify the result after F8, it will not be your desired result.

Kesav

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 07:12:33 GMT

Hi,

I did just as per what you said. That is set an enternal breakpoint in my FM, executed the transaction and waited till my FM gets triggered. And then simply pressed an F8. And it works fine this way.

Re: processing happens only in debug mode.

Former Member — Thu, 13 Oct 2011 07:15:57 GMT

Hi,

are you using a different destination when calling the function module (f.i. DESTINATION 'NONE')? If that is the case, the you should call function BAPI_TRANSACTION_COMMIT with the same destination. If not, could you copy the exact way you call the function here?

Roy