When you change/confirm production orders, extensive delete operations are executed on the info structures S021 and S022 which slow down the entry for the update point of view considerably.
Cause and prerequisitesDelete operations are necessary because the period fields are part of the key and are supplied via the completion confirmation date. If it is changed, you have to delete the old records and insert the new ones.
Solution1. Change the update to asynchronous update.
Use Transaction OMOD
For each info structure, there are update parameters. They should be set to asynchronous update (V2 update program).
2. Update restriction:
The info structure update is controlled via table TMC2F. The update routines are called via the event. You can reduce the system load, for example, that the update is first made as of event PB (production orders and operations with the status 'confirmed'). To do this, you have to delete the records marked with <-DEL from table TMC2F (with an appropriate ABAP).
Table TMC2F
Short description Relevant Update Routines for Info Structures
Number of entries 10
Clien Busin Hiera Update Updat Program Subroutine (2.2)
MANDT ZEITP SUHIE STAFO KBTCH FPROG FROUT (Rel. 3.0)
->003 PA B 000010 2 RMCSS021 F0001_UPDATE<-DEL
->003 PA C 000010 2 RMCSS022 F0001_UPDATE<-DEL
003 PB B 000010 2 RMCSS021 F0001_UPDATE
003 PB B 000010 2 RMCSS023 F0001_UPDATE
003 PB C 000010 1 RMCSS024 F0001_UPDATE
003 PB C 000010 2 RMCSS022 F0001_UPDATE
003 PC B 000010 2 RMCSS021 F0001_UPDATE
003 PD B 000010 2 RMCSS021 F0001_UPDATE
003 PD B 000010 2 RMCSS023 F0001_UPDATE
003 PE B 000010 2 RMCSS025 F0001_UPDATE
For testing: Create a production order. This order should not be in the info-structures S021 and S022 and should not be included in the update log.
Additional key words
Performance
No comments:
Post a Comment