Professional Documents
Culture Documents
Purchase Order Histroy Limitation - SAP Community
Purchase Order Histroy Limitation - SAP Community
Purchase Order Histroy Limitation - SAP Community
Community Topics Groups Answers Blogs Events Programs Resources What's New
Search Questions and Answers
Former Member
Apr 09, 2010 at 08:25 PM
We have the business requirement to process selective SAP purchase orders which grow in size to over 500,000 line items due to the PO history. However, the size of
the PO has become problamatic regarding the amount of time it takes to run on our server. Our basis team has informed us the threshold for the PO history is
approximately 30,000 line items. The scenario for this large POs is most prevalent for our CATS process where a batch job creates Service Entry heets from time
keeping entries. A specific time sheet per contingent worker is processed at least 10 lines per week as orkers are asked to split time between lunch. The contingent
worker charges time against 4-5 work orders in a given eek, which in addition to splitting time can be 25 line items per week per user. So this translates to 25 line
items on the SES and 25 line items on an ERS Invoice. The current SAP limitation is forcing us to shorten the PO duration to 2 months instead of the anticipated 1
year life cycle. Also the processing time for approving the SES and processing the invoice takes approximately 24 hours because of the PO history. We need a
resolution to at least make the PO last for a year, and would very much appreciate any insights on if anyone runs a similar process without encourtering our stated
issues.
Assigned Tags
MM (Materials Management)
Similar Questions
PO release strategy issue
Muni Sudhakar Thaiyuri Jun 03, 2013
Service Entry Sheet PO Amt varies from Amt figuring in LIMITS-Actual Val
Former Member May 11, 2007
1 Answer
Former Member
Apr 11, 2010 at 03:12 PM
Hi there,
0
Please kindly consider the notes I attached to your message.
should be used here. Or you should close the purchase order and create
a new one. Surely we have technical restrictions and can not just
https://answers.sap.com/questions/7213570/purchase-order-histroy-limitation.html 1/3
6/29/22, 1:05 PM Purchase Order Histroy Limitation | SAP Community
support the processing of such huge data volume.
As far as I can tell from here, using the aggregation transaction ME87
please let me ask you to aggregate some of your EKBE data for the
referring PO.
In this case you enter you selection data as it is on the start scree
of TA ME87, then you call in the menu program -> execute in backgroun
This says that The aggregated records are saved in table EKBEH.
Also, since this will improve performance but if you need more you should follow the below advice.
Please create an index using the data in this note. Issue still is that
Regards,
Matthew
Before answering
You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more
information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions,
context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
Rules of Engagement
Your answer
Please provide a distinct answer and use the comment option for clarifying purposes.
https://answers.sap.com/questions/7213570/purchase-order-histroy-limitation.html 2/3
6/29/22, 1:05 PM Purchase Order Histroy Limitation | SAP Community
10 characters required.
Find us on
Newsletter Support
https://answers.sap.com/questions/7213570/purchase-order-histroy-limitation.html 3/3