Professional Documents
Culture Documents
CRP Basic Settings Part 4 - Running Capacity Leveling in Background
CRP Basic Settings Part 4 - Running Capacity Leveling in Background
w.sap.co (https://community.sap.com)
m/) (https://sharedui.services.sap.com/v2/protected.html?
ref=https://archive.sap.com/)
When you are running Capacity Leveling for a large number of objects, very often you will notice
peformance issues, long runtimes or even a time out when loading, dispatching or saving the results.
The most easy way to avoid this kind of issue is the creation of a background job to dispatch the orders
in background and this document explains how to use transaction CM40 to create such job.
This is a continuation of the following CRP Basic settings documents previously published on SCN:
1 - If you have never created such job before, the first steps is to run transaction CM40, defining a name
for your job and which overall profile will be used.
If you check the flag redefine selection, you will be allowed to define the selection criteria to be used on
your background job.
2 - If you choose the option save parameters, system will simply save the parameters under your job
name and the batch will not be triggered. The parameters will be automatically loaded when you enter the
transaction again with your job.
3 - Choosing the option Schedule batch job, you can define a background job to be executed periodically
(weekly, or monthly, for example). This is quite similar to the scheduling of another background jobs, such
as MRP.
4 - With the remaining options Execute background job at once and Execute job at oce online, the job is
executed immediately, in background or online, depending on the option selected.
5 - You can check if the job is correctly scheduled, if it is being executed or if has already finished using
transaction SM37.
6 - At last, you can check for warnings or errors using on logs of mass processing using transaction
CM41 and see the dispatched orders on CM21/CM25.
(https://people.sap.com/caetano.almeida)
5 replies
(https://people.sap.com/kiran.kumar179)
Caetano,
I would like to add one point can you please correct the transaction code for log
display to CM41..
Br
KK
0
(https://people.sap.com/caetano.almeida)
BR
Caetano
best explanation
(https://people.sap.com/anupam.sharma2)
Hi Caetano,
Regards,
Anupam Sharma
(https://people.sap.com/marianoc)
Mariano Cabalen (https://people.sap.com/marianoc)replied
Good document..
Find us on
(https://www.facebook.com/sapcommunity) (https://twitter.com/SAPCommunity)
(https://www.youtube.com/c/SAPCommunities) (https://www.linkedin.com/company/sap)