3398269 - Performance suggestion when using API Journal Entry - Post

This KBA introduces what is the best performance experience when posting with Journal Entry - Post.

SAP S/4HANA Cloud

• Journal Entry - Post (Synchronize)

1. No more than 100 documents with average 2-3 lines per document in one API Call.
2. No more than 15 Parallel API Synchronized calls.
3. If there is one call at a time in Q system, then it is expected to process 5 financial documents (having 2-3 line items per document) per second.
4. With this rate, it would take 20 seconds for 100 documents. And if we extrapolate, to process 250,000 postings in such a way it would take 14 hours without considering parallelisation. This time can be reduced to 1.5 hours to 2 hours by running not more than 15 parallel API calls at the same time.

• Journal Entry - Post (A-Synchronize)

1. No more than 1000 documents and no more than 10,000 lines (average 1000 per document) in the whole file in one API Call.
2. No more than 30 Parallel API A-Synchronized calls. NOTE: System is dynamically throttling number of messages processed in parallel.
3. If there is one call at a time in Q system, then it is expected to process 2 financial documents (having 2-3 line items per document) per second. And for large documents with many lines – 20 line items per second (approx.)

• Other possible reason for the performance issues:

The newly created customer custom fields need time to be updated in the background tables. If an API is executed during the table activation the program could be dumped because the table is inactive at that moment.

Note: The Performance and Times are for guideline purposes and may change depending on the resources used by other processes / tenants on the same client as well as the Journal Entry Post relevant customizing, such as Document Splitting setting. 

Journal Entry - Post, performance, journal entries, line items. , KBA , AC-INT-2CL , Accounting Interface (Public Cloud) , Problem