• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Hey there, to be fair, I didn't work with an ABAP Cloud system yet but from all the things I've read so far the I would say the answer for you would be the usage of bgPF in this case.

Some great insights for you:

• SAP LUW in ABAP Cloud (explains why 'IN UPDATE TASK' is no longer available/needed)
• Quick Intro to bgPF (YT)
• bgPF explained by SW Heroes
• Official Docs of bgPF (also includes insights on the `controlled SAP LUW` for ABAP Cloud)

bgPF isn't equivalent to Update task at all.

What is the function module doing currently? And at which point are you calling these commit entities?

As shown in the example, I am creating a Billing Document using the standard RAP BO.

For sake of simplicity, lets consider this scenario: I would like to insert some data into my custom table, within the V1 update sequence. If I do not do that within the same V1-LUW, I risk having disconnected/orphaned data between my table & standard table.

I think your only 'clean-core' option for now is to use BGPF (the uncontrolled version). Within the method, you can call the MODIFY ENTITIES to create the billing document. Afterwards, call the COMMIT ENTITIES and see the response if there are any errors. And then subsequently, update the custom table at the last stage. The probability of the custom table update failing is very low.

If you do not want to use BGPF, what you can do is called the MODIFY ENTITIES from a custom action, then call the CONVERT KEY statement in the save_modified to retrieve the generated billing document and subsequently update the custom table.

I am not sure if there is any other way to do it as of the moment. I have tested the different variations and some of them fail due to some restrictions in the RAP framework.

If you are familiar with how V1 updates work, then you would know this is not the same as doing via V1 update (which is what I responded to wridgeu as well ☝️).

I am familiar with it and I understand your end goal. But what I am saying is that I haven't found a clean core solution for this yet. Unfortunately, there are a lot of restrictions in place to achieving this, we can only be creative with our solution and see what works for now. the bgpf has both controlled and uncontrolled version. The "controlled" version is supposed to be the solution for bundling the updates where we have a MODIFY and SAVE phase. However, the controlled version also has its own restrictions related to released RAP BO consumption.

Let me know if you found a better solution to this, it would be a very big help.

According to the link given by @wridgeu (SAP LUW in ABAP Cloud (explains why 'IN UPDATE TASK' is no longer available/needed)) you now update directly the database in the late-save phase, so in your case call without IN UPDATE TASK:

CALL FUNCTION lv_func.

@Sandra_Rossi How would I do that call in my example? I am using I_BillingDocumentTP, a standard behavior definition. I won't have access to code within Late-Save phase, isn't it? If it were Custom Behavior definition, then I agree, Late-Save phase can be a solution.

Hello Juwin,

If you are calling I_BillingDocumentTP inside your custom RAP BO , once the call is successful without any failed entries , you can directly update the custom table using Unmanaged save in your RAP BO .
Another solution would be to use Local Consumption of RAP Business Events (Database Table Modification) to update your custom table.

Best Regards,

Siva