Background jobs in demand planning

[Former Member]

In the DP implementation we have been making the background jobs but have the following queries:

1.the timing issue for the scheduling, when we go to the start condition for the background jobs we get the timing according to Germany time not the local time.

2.how do u configure the delta making of the CVC and the delta loading of the planning area once the system has gone live? Is the dynamic variants its only solution?

3.Are the process chain much better as compared to the making of the background jobs using sm36, where are the process chains going to be monitored, Is it SM37.

Thanks in advance

APO

[somnath_manna · Accepted solution]

A 1. Please check with your BASIS team about this. The system time zone is maintained in SPRO (Transaction STZAC) and that determines the time (default is CET).

A 2. Creation of delta CVCs (post Golive) is handled in different ways depending on the client requirement and scenarios. However the most common ones are:

a) Manual - since new products are not going to have Sales History you will create new CVCs manually or maybe using Realignment.

b) If you are adding new products for planning (for which you have sales history) then you can generate CVCs based on the Sales History Infocube.

c) Custom program to generate CVCs based on new product master or any such condition.

In the variant for creating new CVCs - it is not advisable to select the option of "Adjust Time Series Objects". First create the CVCs then regenrate the timeseries for the associated planning area and thereafter load data to the planning area.

The loading of data to planning area from infocube (transaction /SAPAPO/TSCUBE) can use a dynamic variant to adjust the time periods for which you want to load data.

A 3. Already replied.

Thanks,

somnath

[Former Member]

Process chains are better than SM36 jobs in many ways. Mainly for jobs that are set up in chains, sequentially and have a dependency on another job

you can create most background jobs using the options in RSPC

Monitoring is a bit of a problem. And so is stopping a job midway. you probably have to use sm50 to kill processes. As far as i know you cant monitor in SM37.

you can check the logs of the jobs that have been completed in RSPC though.

I use SM36 for stand alone jobs and RSPC for dependent or complicated jobs. You just need to remember what is where

[Former Member]

Just to clarify.

Jobs kicked off through a process chain can still be montored through SM37.

The only real difference being that the job name will relate to the process type in the chain, not the defined DP Job Name.

Regards, Mark.

[Former Member]

Hi Mark

thanks for that. I remember not being able to see it in SM37 but will check again.

[Former Member]

Hi,

In SCM 5, you can monitor the jobs of Process chain. Job name start with <b>BI_Process_</b>, With this you can atleast understand wheter the process chain's process start / finished.

For logs you will require to monitors through RSPC/RSPC1 transactions.