2018 May 31 12:00 PM - edited 2024 Feb 04 3:16 AM
Hello Experts,
In our current Solution for IBP we have S&OP and Demand licenses. We are doing Time series based planning. IBP 1805 is integrated with S/4 Hana 1709 for master and transaction data.
My query is regarding planning at different attribute levels. I am providing a brief explanation below:
CUSTID LOCID KEYFIGUREDATE PRDID ACTUALSQTY
Lastly. can we achieve the above requirement with Time series planning of do we need Order series license to serve our purpose?
Regards,
A.Basu.
Request clarification before answering.
Hi,
I would suggest to once again review the S/4HANA and IBP master data types.
1. S/4HANA customer master has CUSID DISCHN and the same attributes to be mapped in IBP. If one customer belongs to 3 distribution channels, in IBP 3 planning objects to be created with customer and distribution channel combinations.
2. You need to adjust the master data type CUSTOMER.
3. While mapping from S/4HANA you need to change the logic disaggregate the data at customer/distribution channel wise and load data into IBP tables.
4. Load data at customer distribution channel level and aggregate data to the customer level, so you have data at both combinations.
5. You need to upload data at CUSTID/DISTCHN/LOCID/PRDID level.
Best Regards,
Lingaiah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lingaiah,
Based on the inputs-
1. Added MDT CUSTDISTRIBUTIONCHANNEL, with Cust id and Dist Channel. Checked Attribute Cust ID against Cust id for MDT Customer to have consistency.
2. Created a new planning level WKPRODLOCCUSTDISTCHN, added Dist Channel as root.
Now, the standard configuration for Actual Sales/Demand and other KFs are at level WKPRODLOCCUST.
I require to have the KF values at both levels so that i do not have to adjust other KF calculations for level WKPRODLOCCUST. How can i approach this need of having values at both level without touching other calculations?
Regards,
A.Basu.
Hi Basu,
Planning level WKPRODLOCCUSTDISTCHN - dist channel as root and create new key figure called ACTUALQTYS4 with planning level WKPRODLOCCUSTDISTCHN and finally write calculation planning level at WKPRODLOCCUST (So this key figure is input for ACTUALSQTY). Later create new key figure or used standard key figure to copy the ACTUALQTYS4 (WKPRODLOCCUSTDISTCHN) to ACTUALSQTY (WKPRODLOCCUST).
Sorry for the above message.
Best Regards,
Lingaiah
Hi Basu,
Rather than making changes in master data in IBP, I would suggest to do following.
Since Customer ID is a key field in IBP and in S4 Customer ID + Distribution channel makes it unique entry, you should combine CustomerID_DistChannel in HCI DS. This will make your customer ID as key in IBP. If you do this also make sure that every interface you have from S4 to IBP that has customer in it, same transformation should be applied.
Hope this helps.
Thanks
Vilas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
at high level this seems like yiu will need separate master data retype distribution channels as you have inS4 you. Add new master data and attribute to planning are then to create new planning level wkprodcustdc. Something like that and adjust key figure r view this appr
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anil,
Thanks for the inputs.
Here is what i did - 1. Added MDT CUSTDISTRIBUTIONCHANNEL, with Cust id and Dist Channel. Checked Attribute Cust ID against Cust id for MDT Customer to have consistency.
2. Created a new planning level WKPRODLOCCUSTDISTCHN, added Dist Channel as root.
Now, the standard configuration for Actual Sales/Demand and other KFs are at level WKPRODLOCCUST.
I require to have the KF values at both levels so that i do not have to adjust other KF calculations for level WKPRODLOCCUST. How can i approach this need of having values at both level without touching other calculations?
Regards,
A.Basu.
Hi Basu
if you store data at
WKPRODLOCCUSTDISTCHN then aggregation will happen automatically if you remove DC in planning view
WKPRODLOCCUST as system functionality
you may include sum calculation
WKPRODLOCCUST
= sum (WKPRODLOCCUSTDISTCHN)
If there is another business need then you cam also use copy operator but I don't think you need it
Regards
Anil
| User | Count |
|---|---|
| 9 | |
| 6 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.