Post COMMIT DB update in ABAP RAP

[ilja_mihailovs]

Hi experts,

Looking for an advice to perform an additional DB update after RAP runtime has performed its own COMMIT ENTITIES statement. Reason for that being - BAPI that is being used to maintain data doesn't allow for custom fields to be passed over and I have to update these fields via a direct DB update - and you can't do a DB update to a record that doesn't exist yet :).

I could, of course, issue a PUT request right after POST request (to do an update), however that would result in two API calls which I want to avoid.

Another option would be an own commit in aRFC function module and then an UPDATE statement which would be committed by a RAP framework, but, perhaps, there are other cleaner options?

[Ramjeekorada]

Hi Ilja,

You can define an event in behaviour definition and raise it at the end of processing in your saver class . So that it will be executed after RAP commit work.

Best wishes,

Ramjee Korada