KEDU: Performance update of summarization levels
[CE1xxxx] [CE2xxxx] [COVJ] [COVP] [DELTA_CE0] [for update of] [high performance] [KEDU] [level] [performance] [summarization] [update]
- INFO: CO-PC-OBJ (Performance)Symptom This is a general note on how to eliminate performance problems in Cost Object Controlling. This note deals with cross-process and general topics. For further valuable information refer to “Workshop: CO-PC...
- CO_ML_BEL: Performance problems during document archivingSymptom Performance problems occur when you archive material ledger documents. Other terms Performance, CO_ML_BEL Reason and Prerequisites You use the archiving of material ledger documents. Solution Use transaction SE11 to create the...
Symptom
You update a summarization level in the costing-based or account-based profitability analysis for an event for which even larger datasets are posted to the Profitability Analysis in parallel. This can impair performance, as the database then reads more line items than is actually necessary.
Other terms
KEDU, summarization level, update, CE1xxxx, CE2xxxx, DELTA_CE0, COVP, COVJ
Reason and Prerequisites
This was caused by a design error: the system unnecessarily selects the line items that were updated with a greater time stamp than the new time stamp of the updated summarization level (that is, line items that were created within 30 minutes before the start of the summarization level update), even though they are not of any benefit to the summarization level.
Solution
a) For the function module RKE_READ_OBJECTS, create the optional import parameter UPDATE_MODE with the type specification TYPE, the associated type FLAG and the default value ‘ ‘. Select the fields for the attributes ‘Optional’ and ‘Pass value’. Save and activate the function module RKE_READ_OBJECTS.
b) Implement the following source code corrections.
c) Now execute the module RKE_GENERATE_SELECT for your operating concern so that the changes to the template RKEVRK2B are copied to the generated program.
CAUTION: test the new logic thoroughly in a test system or development system before you use it in your production system.