3391018 - Performance recommendations for Journal Entry - Post API - S/4HANA Cloud

How to develop the performance of the Journal Entry - Post API in S/4HANA Cloud environment?

SAP S/4HANA Cloud

Performance recommendations of Journal Entry - Post API

Synchronized Call:

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 we have one call at a time in Q system, then we should expect 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.

A-Synchronised Call: Performance Recommendations for Q system.

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-Synchronised calls. NOTE: System is dynamically throttling number of messages processed in parallel
3. If we have one call at a time in Q system, then we should expect 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.)

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.

There are also few general performance recommendations to consider:

1. Batching Requests: If the API supports it, consider batching multiple journal entries into a single API call. This reduces the overhead associated with establishing a new connection for each API call.

2. Throttling: Be mindful of the API rate limits. Sending too many requests in a short period might get your API access temporarily blocked.

3. Error Handling: Have robust error handling to manage any API or network errors. For instance, if an API call fails, you might want to implement a retry mechanism with exponential backoff.

4. Validation: Validate data before sending it to the API to reduce the likelihood of failed API calls.

5. Optimization: Only send necessary fields in your API requests to reduce the payload size and improve performance.

6. Async Processing: If the application supports it, consider making API calls asynchronously to prevent blocking other operations.

SAP Community Post: Are there performance recommendations for Journal Entry - Post API?

performance, api, post journal entry, journal entry - post, performance recommendations,  , KBA , AC-INT-2CL , Accounting Interface (Public Cloud) , How To