DP background job is failing with message " Plannning version XXX is not initialized to planning area "XXXX". How to correct it .

[Former Member]

Hi ,

Few of the DP jobs are getting cancelled with error "Plannning version XXX is not initialized to planning area "XXXX". If the same job is copied then also geting the same error. But If I create new job with exactly same parameter then its running successfully. The Planning version is pretty much initialised and there is no inconsistency in system. When I try to do mass processing for this job theu MC8I , it gives status  as" processed with error".

Anybody in this forum faced the similar issue .

Thanks -

M

[jagannadhb]

Dear Mitali,

To identify the root cause, you can debug the job in SM37. Just type in 'JDBG' in the

command line (  '/n/JDBG' ), put the cursor on the job and press enter - will take you to the job in debug mode.

Regards,

JB

[Former Member]

Hi,

   The error is coming because of key figure(wrongly created/invalid parematers). Please Change the key figures. First Try with standard key figure.

Other thing you can check:

1. Check the Periodicities, Create New(don't take currency field while doing) - you should specify the correct date interval without gap

2. Check MPOS and create atleast 1 CVC (Without CVC it will not work)

Please go through the following:

Re-Initialize Your Planning Area with report /SAPAPO/TS_PAREA_INITIALIZE. The creation

of time series objects for the planning area is known as initializing the planning area. The

system creates a network of characteristics and key figures in liveCache, time series objects

are created for a version and a period of time. You can extend the time series into the future

and delete the oldest periods from liveCache by re-initializing the time series periodically. In

this way, you can maintain a "rolling horizon". The system recognizes where new

characteristic value combinations or new time series exist, and creates time series objects

only for the new master data. From release SAP SCM 4.0, you can define key-figure specific

initialization horizons and save a lot of memory in your liveCache. For example, for historical

key figures, you can initialize only time buckets in the past and for forecast figures only

buckets in the future. This can be defined in a Pop-Up window during the start of the report or

in the transaction for key figure administration.

The report /SAPAPO/TS_PAREA_INITIALIZE locks the complete version of the planning

area. If the lock cannot be set, the report terminates. From release SAP SCM 4.0, you have

the additional possibility to perform the initialization with parallel processes by defining a

parallelization profile in transaction /SAPAPO/SDP_PAR. For this, you have to define a block

size and a maximum number of parallel processes for the planning area. After starting the

Best Practice: Manage Demand Planning in SAP APO (3.x) / SAP SCM (4.x, 5.x)

initialization job, it automatically creates the desired number of parallel processes. If the report

terminates abnormally for any reason other than lock problems (you can see this in the job

log), run report /SAPAPO/TS_LCM_CONS_CHECK with option Repair (see Maintenance of

DP Data Storage Structures) before restarting/SAPAPO/TS_PAREA_INITIALIZE.

For example, if you no longer need a certain planning version, you can remove its data from

liveCache by deleting the time series objects with report

/SAPAPO/TS_PAREA_DE_INITIALIZE.

Suggestion taken from :

[alok_jaiswal]

Hi Mitali,

Please check in /SAPAPO/MSDP_ADMIN if your planning area is active (Green status).

Also choose your planning area and create time series objects (right click on planning area and Choose Create time series objects) or you can do via SE38 report  - /SAPAPO/TS_PAREA_INITIALIZE

After that run the consistency check program in repair mode to correct any inconsistencies - /SAPAPO/TS_LCM_CONS_CHECK.

Hope it helps.

Regards,

Alok

[Former Member]

Planning area is active thats why if I create new job with same parameters it run successfully. And we are done with all consistency check.