Way to find CTM taking more time to plan a demand

[Former Member]

Hi,

Normally a demand in CTM gets planned in less than 1 second. But sometimes there are abnormailities may be because of Data or system and CTM takes more time to plan a demand. Is there a way or method to find why a demand has been planned in more time?

Need your help

Thanks

Deepak

[Former Member]

Hi Deepak,

1) Once the CTM run is started, it will record & execute all the events of the program mentioned in the function module and each event will be stored in the OPTIMISER TRACE FILE.

The trace files will be recorded in back end and you can check with basis team to help you in extracting & convert into your requirement form with suitable fields and you can develop a custom report on this so that you can execute on daily/weekly basis and analyse. The trace file will be available only in optimiser server.

2) The other areas that you can look at is /SAPAPO/OPT12 - Process Overview wherein u will get process related informations but not at very detailed level

3) Check with basis team whether any database alerts can be developed if at all your CTM run gets strucks or extends for want of data or performance.

4) Check the application logs/inbound/outbound queues/sysfails which will figure out any specific item containing errors.

Regards

R. Senthil Mareeswaran.

[Former Member]

Hi Deepak,

Normally, CTM run takes time for the following reasons.

1) Demand is very high

2) Master data inconsistencies

3) Transactional data errors

4) Performance problem of livecache

The reasons for abnormality will be stored only in the following areas.

1) Optimiser trace file (you need to take basis help to read the files)

2) Application log files

3) Optimiser log files

4) CTM consistency check will reveals the inconsistencies if any.

Regards

R. Senthil Mareeswaran.

[Former Member]

Thanks Senthil. I know via Master data/transaction data I have to check why demand planning took more time. But is there a tool or transaction handy that gives me the information and reason for this?

Your reply is appreciated.

Thanks

Deepak

[Former Member]

Hi Deepak,

There is no such kind of tool to find out the reason of higher runtime. But yoy can check the job logs to find out the total run time for every steps.

Like there is information that "job started' ..step started..then 77 location product processed.

You will find a time difference between these steps.For any job to be started its checks for its relevent masterdata then its processed and find out the result, then writes the result.

So, if you find difference between job strted and 1st step started is taking more time, then its taking for the consistency checkof the selected master data. And if there is a high time difference between loc-prodct processed and its previous step's end time, then you can assume that there are many masterdata in your selected scenario or the planning horizon is large or too much demand.

There are very good information regarding the run time for every steps for 'Optimizer' in the optimizer application log, for CTM you can check the joblog through sm37 (step by step) (or via reporting/application log)

Thanks,

Satyajit