SAP Knowledge Base Article - Public

2892387 - Post Journal Entry API Performance Recommendations

Symptom

Journal Entry Post API may suffer poor performance if it is used to post a large bulk of journal entries.

Environment

SAP S/4HANA Cloud

Reproducing the Issue

Use Journal Entry - Post API to create a large bulk of journal entries.

Resolution

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.

Synchronized Call: Performance Recommendations for Q system.

  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.

 

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 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.)

Keywords

API, performance, Journal Entry - Post, synchronize, a-synchronised , KBA , AC-INT , Accounting Interface , How To

Product

SAP S/4HANA Cloud all versions