topic Re: How to avoid commit work in call transaction in Application Development and Automation Discussions

How to avoid commit work in call transaction

Former Member — Thu, 02 Feb 2006 16:12:25 GMT

Hi,

I have to process several account entries using call transaction (one call for each entry) but these entries are related and if, for example, the third entry fails none of the previous entries will be stored in the system (that is 1st, 2nd and third entry will fail and the process stop).

So I need to control when occurs the commit work, that in my case it will be at the end of the account entries.

Is this possible?

thanks in advance

Re: How to avoid commit work in call transaction

christian_wohlfahrt — Thu, 02 Feb 2006 16:42:56 GMT

Hi Javier!

No.

Call transaction is per definition a complete business transaction, so commit work is essential part.

Either you find a way to make your changes with one call transaction (switching to new account entry without leaving the transaction) or you trigger storno (cancel) bookings in case of a failure.

Regards,

Christian

Re: How to avoid commit work in call transaction

Former Member — Thu, 02 Feb 2006 16:57:12 GMT

If possible, try to combine the three transactions into one.

Or - before posting any of the transactions, try to simulate them. You can check the message table to see if there were any errors. Don't proceed if there are any. This won't be perfect because I think the transaction could fail even if it simulates OK.

Or - post the first two. If the third one fails, back the other two out (reversals). I've had to do this (for budget documents). It works, but it's clumsy.

Rob

Re: How to avoid commit work in call transaction

Former Member — Thu, 02 Feb 2006 18:32:28 GMT

On second thought, use a BAPI (BAPI_ACC_GL_POSTING_POST for one). I think you should be able to do several postings before doing a commit.

Rob

Re: How to avoid commit work in call transaction

hymavathi_oruganti — Fri, 03 Feb 2006 04:35:43 GMT

TO BYPASS THE COMMIT WORK EXECUTED BY TRANSACTION, WE HAVE UPDATE BUNDLING TECHNIQUES.

WITH THESE TECHNIQUES WE CAN BYPASS THE SYSTEM COMMIT UNTIL WE GIVE COMMIT BEXPLICITLY.

PERFORM ...........ON COMMIT

CALL <FN> ON UPDATE TASK.

Re: How to avoid commit work in call transaction

Former Member — Fri, 03 Feb 2006 05:02:04 GMT

There should be a test or simulate option on these transactions. Do that to check if there are any errors, and if all of them pass, then do the actual call transaction with commit.

Srinivas

Re: How to avoid commit work in call transaction

Former Member — Fri, 03 Feb 2006 05:02:26 GMT

Hi Javier,

1. U are using CALL TRANSACTION usin BDCDATA

in your program.

2. Instead,

Write this code

in a new FM (of type UPDATE MODULE - Start Immd.)

3. Now create another program,

and call this FM (passing parameters of 1 entry)

for each ENTRY in a loop.

4. After the loop is completed,

write COMMIT WORK.

5 This will solve your problem .

regards,

amit m.

Re: How to avoid commit work in call transaction

christian_wohlfahrt — Fri, 03 Feb 2006 07:48:10 GMT

Hi Hymavathi, Amit!

In update tasks only restricted possibilities are available:

"While an update function module is processed in an update work process, you are not allowed to execute the statements SUBMIT, CALL DIALOG, CALL SCREEN, CALL TRANSACTION, COMMIT WORK, ROLLBACK WORK and all other statements that provoke a database commit."(help call function in update task)

So this can't be used to bundle several call transactions - because a transaction is still per definition a complete unit and an update task can only work for one unit or work.

This perform ... on commit / call .. in update task can be used to bundle several direct table updates (on Z-tables of course and FM calls, but nothing more.

Regards,

Christian