Skip to Content

Planning Object in IBP

Hello,

I have a general question in IBP. What is the definition of a planning object. We have often the situation, that we create new master data and upload this with the dataintegration job but first we have create a new planning object it is visible in the planning view.

What is a planning object ?

What is the different between planning object and planning level?

How this process work in a production system ? Is this not inconvenient?

Give a way to create a planning object automatically ?

Will be a planning object automatically create with the CDI Process ?

Thanks in advance

Regards

Oliver

Add a comment
10|10000 characters needed characters exceeded

Related questions

6 Answers

  • Best Answer
    Posted on Jan 11, 2019 at 07:01 PM

    Hi Oliver,

    Planning Object is the unique ID for each combination created based on the Base Planning Level.

    It can be created directly one by one in Excel Add-In or during Forecast run which will require to maintain Global Parameter - "CREATE_MISSING_PLANNING_OBJECT".

    You can also use DISAGG Operator to create Missing Planning Object if the following pre-requisites are met -

    • The aggregation level of the DISAGG operator (ATTRIBUTE1, ATTRIBUTE2, and so on) must be the same as the base planning level of the target key figures.
    • Planning objects can only be created if the required master data values are available. The DISAGG operator does not create missing master data type values.

    Regards

    Ankur

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 11, 2019 at 06:25 PM

    Hey Oliver

    do you know APO-DP and the initialization requirements there with report /SAPAPO/TS_PAREA_INITIALIZE?

    Here you had to initialize the planning horizon for a planning area before you could work with it. And when you had a new cvc, you needed to run the /SAPAPO/TS_LCM_CONS_CHECK for each planning area attached to a planning object structure.

    In IBP, one planning area usually has lots of planning levels that need initialization individually as well. A planning combination is the combination of key attributes of that planning level. This can be done by e.g.:

    - load key figure values for at least one key figure of that planning level, in order to initialize the whole horizon --> automatically done by CPI-DS load, and in orderbased planning the TS-key figures are usually generated by the SDI load

    - have a key figure attribute attached to the planning level and maintain any value, as it is the concept of the SAP7 / SAP74 planning areas since the beginning --> this is my preferred way for most planning levels: create a decibel attribute, attach it to a master data type and have it as key figure attribute. Challenge is to find the right MD type: for PERPRODLOC it would be to IBPLOCATIONPRODUCT, for PERPRODCUST it would be IBPCUSTOMERPRODUCT, for PERPRODLOCCUST you could create a dummy MD type location-customer-product -- or use the IBPCUSTOMERSOURCE, etc.

    - by COPY operator with setting specific parameter to "X" (DISAGG) is the other way around, set a parameter if you do NOT want the objects to be created). If you e.g. have the WKPRODLOC initialized, make a sum-calculation (or whatever would fit) and copy KF to MTHPRODLOC level

    - by running FC model and having a global parameter set that this creates missing planning combination

    It is sufficient to have one key figure per planning level initialized, in order for all to be available without error

    Sounds more complicated as it actually is...

    Irmi

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Irmi,

      just to get it right refering to the second option you sketched out, i.e. "have a key figure attribute attached to the planning level and maintain any value".

      Would I need to create a dummy MD consisting of location-customer-product to which I am attaching a custom attribute as KF which I am filling with a dummy content in case I am using a copy of the standard planning area SAP6 (demand) where I make use of planning level "LOCPRODCUSTWEEKLY"?

      Example:

      MDT (LOCPRODCUST)

      Customer | Location | Product | Init
      4711 | 0001 | 0815-10 | 1

      Init would be an attribute based KF within my planning area being loaded with dummy value '1' in order to initialize this level?

      Or did I get it wrongly?

      regards Peter

  • Posted on Jan 16, 2019 at 09:31 AM

    Hi Irmhild, hi Ankur,

    thanks for the response.

    In our demo system, we have often the situation, that we want upload velues for the keyfigures but it is not working. The values are often not visibility in excel.

    After, we create a "new planning object", we can see and manage the values.

    If I set the global parameter for create Missing Planning Obejct, will the system automatically create than the object if I start the forecast algorthm? also for attributes , which are not used in the forecast process?

    Regards

    Oliver

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 16, 2019 at 03:57 PM

    Hi Oliver,

    Using that operator, it will create all possible valid planning object for the planning level at which you will be running Forecast.

    Regards

    Ankur

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 21, 2019 at 07:34 AM

    Hi Ankur,

    thanks for the response.

    Regards

    Oliver

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 28, 2019 at 08:48 AM

    Hey Peter

    You got it right, that is the general idea.

    I dont like the SAP6 planning area too much due to the naming convention of the planning level, therefore I usually copy from SAPIBP1 and only copy the Demand side instead and model what may be missing manually. In those cases, we do already have the customer source on the level of product-location-customer which I than mis-use for the initialization.

    Make sure the attribute is really of type decimal.

    You can see the concept very much in use e.g. for the orderbased planning where the timeseries data are automatically generated with this, using the key figure attributes that all start with H and end with COUNTER, check SAP7 for reference in order to understand the idea better

    Irmi

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.