Using Call Transaction 

You should try to use function modules to update the database rather than resorting to a call transaction, as call transactions have a significant performance overhead. The advantage of using call transactions is that, if an error occurs, the user can reprocess the IDoc by going through the transaction’s input screens.

If you use a function module to process a single IDoc, as described above, but where the function module uses a call transaction to post the application data to the database, the application data is posted in a different logical unit of work from that in which the IDoc status data is posted. A call transaction does a ‘commit work’ when it has been successfully executed.

The solution to this problem is to modify the transaction so that it updates the IDoc status data when the application data is updated, i.e. when the IDoc is successfully processed. Note: this only applies to successfully processed IDocs; errors are handled in the same way as before.

See also:

·       ALE -Enabled Transactions

·       Call Transaction Successful

·       Call Transaction Failed

·       Import Parameters in CALL TRANSACTION

·       Export Parameters in CALL TRANSACTION