These steps indicate a general guideline for troubleshooting problems with asynchronous publish. Generally, if there were issues with publishing the document, the errors will be displayed on the UI of the Contract that is being published. However, in certain cases, there may be a breakdown in the behind -the-scenes machinery, errors related to configuration, that are not easily visible. In such cases, the status of the publishing of the document usually freezes at a point. Defining the point, at which the document’s status has frozen is challenging since the time for status change will be different for different kinds of documents and system landscapes. The time may increase or decrease based on the latency in communication between the ERP, PI, CLM system or the actual time taken to process these requests within the system. The time also depends on the size of the contract document being published and is affected by the number of line items, pricing conditions, supplier entered attributes, line item attributes etc.
In general, the following numbers can be used as indicative numbers for the time taken to complete the publish process:
For 1000 line items ~ 150 seconds
For 2000 line items ~ 500 seconds
For 3000 line items ~ 800 seconds
Keep in mind that these numbers are indicative only and do not represent performance benchmarks. The time taken to process requests will differ based on the factors described above.
SAP Sourcing and Contract Life Cycle Management 11.0
Asynchronous, Publish, Master Agreements, Troubleshooting guide, MA, ERP, ECC, Outline Agreement, OA etc. , KBA , SRM-ESO-INT-ERP , ERP Integration for SAP Sourcing & CLM , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.