Purchase Order Histroy Limitation

Question

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.

Answer 1

Hi there,
Please kindly consider the notes I attached to your message.              
In general, aggregating part of the purchase order history documents      
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         
support the processing of such huge data volume.                                                                               
As far as I can tell from here, using the aggregation transaction ME87    
is the only possibility to consolidate this issue, i.e., reduce the       
amount of data retrieved by the system to an acceptable amount. So        
please let me ask you to aggregate some of your EKBE data for the         
referring PO.                                                                               
311089 Performance problems because of long PO history                    
694091 Further processing of aggregated documents                         
1.Regarding mass execution of PO's.                                        
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      
Then the aggregation will be carried out as a background job and           
everything possible will be aggregated as you expected.                                                                               
2.Details of aggregation can be checked in below notes                     
417933   Consulting note on purchase order history records ME87            
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
EKBE is very large.                                                    
1386608 MRN0: Performance problems for selection with receipt prices   
For a detailed description on how to create an index,                  
please refer to the online documentation, 'Basis Components ->         
ABAP Workbench ->  BC - ABAP Dictionary -> Tables -> Indexes'. 
Hope this helps.
Regards,
Matthew