Product Information
SAP IBP Tight Coupling for Planning Objects
This video showcases the new functionality in SAP Integrated Business Planning called Tight Coupling for Planning Objects that has been introduced in SAP IBP 2208 release, which helps in automatic creation of planning objects and automatic deletion of obsolate planning object based on selected master data for a particular planning level.
Hi Ayan Bishnu thank you very much for this instructive video. Tight-coupling will sure come in handy.
At 2:05 you mentioned that this new 2208 feature can prevent some earlier workarounds such as copy operators, deletion of non-conforming planning objects; and what is the last workaround you mentioned please? Could you elaborate a bit?
He talks about Attributes as Key Figure I think. Meaning an Attribute in a Master Data Type, which you fill via CPI with a "1" and which is linked to a Planning Level. This will automatically create a Planning Object when you load Data in the Master Data Type.
Yes you are right. Thier are different ways like AAK, using CPI with value 1 and even using the advanced copy operator with option as generate planning objects.
Hi Ayan Bishnu thanks for the video. Do you know if this function is only creating the Planning Object or also initializing the time periods? And for which horizon? Thank you!
This is exclusively for creation of new planning object and deletion of obsolate planning object. It has nothing to time period initialization. The planning objects are generated for the entire planning horizon
Thank you Ayan Bishnu a very helpful video!
Ayan Bishnu Why is it that in the TEST environment I'm able to make a selection, in the section "Tight Coupling for Planning Objects" of the Master Data Type and the Create/Delete button but in the PRODUCTION environment it is not enable. I've been looking in Roles/Catalog in both environments and I cant see why
Any comments will be appreciated
Thanks
After posting this the first time I kept checking and without having made any changes the option is enable in the PRODUCTION environment. I dont know why, if it is because it was locked as probably a process was running ??