cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP IBP Key figure DependentDemandQty @ LOCPRODCUSTWEEKLY - fail to activate planning area

ydyulgerov
Participant
720

Hello guys,

I am facing an issue while trying to create BOM explosion in IBP.

The problem is that after implementing the configuration steps: creating the new attributes, master data types (for BOM header and BOM ratio), planning levels, and key figures, I am not able to activate the planning area. While creating the key figure for "DEPENDENETDEMANDQTY", I got a warning message (see attached). Basically, the errors I got by activating the planning area are the same (screenshot also attached).

Based on the errors it seemed that planning level LOCPRODCUSTWEEKLY should be adjusted in terms of the attributes it consists of. But this is actually inconsistent with steps I followed especially regarding to the configuration of the planning levels. This planning level is part of other calculation as you can see in the screenshot for dependent demand calculations, so after I deleted the non-root attributes, the activation showed another error connected to another planning level (which seemed not to be the solution).

The planning level LOCPRODCUSTWEEKLY consists of all attributes for location, product, customer, technical week (screenshot attached), while the LOCPRODCUSTWEEKLYNOAT includes only root attributes for location, product, customer and technical week.

There is also one step for attribute transformation where the value of SALESITEMPRDID is put to PRDID in the transformed planning level TRANSSALESITEMLOCPRODCUSTWEEK.

For the BOM explosion three key figures are in use – dependent demand quantity, independent demand quantity and total demand quantity.

Any help for the activation of the planning area will be highly appreciated. Thank you very much in advance.

Best regards,
Julian

Accepted Solutions (1)

Accepted Solutions (1)

former_member194529
Active Contributor
0 Likes

Hi Julian,

I assume you were you able to find the root cause of your activation issue, otherwise I recommend you to open an incident of SCM-IBP-CNF-ACT support component.

Best,

Ivan

Answers (0)