on 03-16-2021 4:00 AM
Hi experts,
I am trying to run the forecast automation job at Product- Sales Org level. I created a new masterdata Product Sales org where Product and Sales Org are the root attributes.
The Planning level WKPRODLOCCUST doesn't have Sales Org as Root attribute.
So, when I run the Forecast Automation job, some of the records which have different Time Series analysis output fail with the Ambiguous value for non-root ZTSANALYSIS2 using root PRDID at plan level PA1.WKPRODLOCCUSTCURR in MD PA1PRODUCTSALESORG.
Failed Record:
How can this error be avoided, since I cannot run the time series analysis at Product-Customer level, since it's too detailed and can't be used.
Regards,
Sid
Hello Sid,
This is a configuration design issue and it's documented in KBA 2367185 - IBP: Master Data Load Error-Ambiguous value found for non-root....
Although your MDT Product Sales Org has PRDID - SALESORGID as key attributes, in the PL WKPRODLOCCUST, that has PRDID - CUSTID as roots, and SALESORGID as non-root, the forecast automation operator may find several PRDID - CUSTID combinations with different time series properties to the same SALESORGID. However, when the operator will store the data in the MDT Product Sales Org, it doesn't know which time series property to save as there might be several different ones at the PRDID - SALESORGID level.
You need to define if the time series properties are either saved at a PRDID - CUSTID level, or calculated at another PL e.g. PRDID - SALESORGID (as roots).
Best regards,
Matheus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
4 | |
3 | |
2 | |
2 | |
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.