Optimization of BAPI in mass upload for purchase order history in SAP S/4HANA

[AuroraLLR]

Hello community,

I am working on a mass upload development in SAP S/4HANA that uses two BAPIs:

BAPI_DOCUMENT_POST (to post accounting entries).

BAPI_HISTORY_XX (to update the purchase order history when a line item contains a PO and its corresponding item).

The process works correctly, but I am facing a performance issue:

Multiple accounting documents are processed, each with several line items.

Whenever a line item has a PO, the history BAPI is executed.

Since this is a mass upload, the BAPI is executed for each line item, making the process very slow.

The ABAP developer working on this mentioned that there might be an SAP note to optimize this process, but we are unsure where to look.

Questions:

Is there any SAP note specifically to improve performance in this type of process in S/4HANA?

Has anyone faced a similar issue and found an efficient solution?

Would it be advisable to group the updates and call the BAPI only once per PO? If so, how could this be implemented without compromising data integrity?

I would greatly appreciate any guidance or shared experiences.

Thanks in advance!

[Sandra_Rossi]

Do the mass upload in parallel processes. After that, if still slow, check the SQL execution plans. These two topics have been discussed a lot in the forum.

[AuroraLLR]

Thank you for your response! I appreciate your suggestion regarding parallel processing and checking the SQL execution plans.

To better understand the parallel processing approach, I have the following questions:

What is the recommended way to implement parallel processing for a mass upload in SAP S/4HANA when using BAPIs? Would you suggest CALL FUNCTION IN BACKGROUND TASK, Asynchronous RFC (aRFC), or another method?

Since one of the BAPIs updates the purchase order history, would parallel processing cause any issues with data consistency? How can I ensure that updates do not conflict with each other?

If SQL performance is a concern, which specific tools or transactions should I use in SAP S/4HANA to analyze SQL execution plans for this scenario?

Thanks again for your help! Looking forward to your insights.