Commit Handling for Synchronous Write Scenarios

[Former Member]

Hello gurus,

I have to use syncronous interfaces between SAP and custom UI application. SAP will both be client and server in different scenarios. I would like to know how I can achieve consistency for write operations with commit handling mechanisms, both for PI 7.0 and PI 7.1. Proxies will be used on SAP side.

All helpful hints/linkd/docs will be very much appreciated and rewarded.

Thank you for your input.

Gökhan

[Former Member · Accepted solution]

Hi Gokhan,

I believe you refer to the server proxy coding where the write operations are performed.

If you are using ABAP server proxy, then the coding should be similar to the way you handle SAP LUW in any ABAP program. In the method of your ABAP proxy class, you can group several BAPI calls or changes to several tables into one LUW and just the do the commit at the very end.

You need to create update FM to updae your tables and call them in update task mode.

For example.

LOOP AT <your incoming message table>

CALL <BAPI> IN UPDATE TASK

CALL <custom FM to update tables> IN UPDATE TASK

ENDLOOP.

CALL BAPI_TRANSACTION_COMMIT.

Regards,

Lim...

[JoelTrinidade]

Hi Gokhan,

Please elaborate on what do you mean "consistency for write operations with commit handling mechanisms".

Rgds

joel