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

SAP IBP DISAGG Operator using Attribute selection

0 Likes
912

Friends,

We have a situation for our demand planning KFs which are at aggregated Level (Product Class), will get disaggregated to SKU Level using a Disaggregate expression which is working fine.

The requirement we have is out of 100 SKU under product class, user will define a attribute in LOCPROD for which DISAGG should not be done, lets say for some 10 SKU..

Current Scenario: 5000 Qty at Class Level will get Disagg to all 100 SKU by 50 each

Requirement: 5 SKU out of 100 will be marked as Lets say NA in some Attribute in LOCPROD Demand Planning Exclusion = NA, expectation is 5000 should get divided to 95 SKU with 52.63 each, and for those 5 SKU DisAGG should not add any value.

What I have done is in COPY_DISAGG Operator, I have added Attributes values Demand Planning Exclusion <> NA.

When I run Redisagg Operator, its not respecting above criteria... Should I write this in KF Disaggregation Logic Itself, can you please guide?

View Entire Topic
Irmi_Kuntze
Product and Topic Expert
Product and Topic Expert
0 Likes

What you describe is quite complex, and you do not provide HOW you did that in detail. Screenshots of the configuration of the source and target KF and of the copy operator would be helpful to analyze why it failed.

I assume your disaggregation expression does only consist of stored KF's, as described in the model config guide?

Your filter on demand exclusion is not available at the source KF. And as you do not copy between 2 different planning area where you could decide from which attribute you are reading = source or target, the attribute is likely ignored (I have not tested this, just a guess, did you check the log?)

What you could do is to create a calculated KF with means of split factors and copy from there to your target KF, but then not on the aggregated but already on the detailed level (if you need the result as stored key figure in the first place, you may be happy with an on-the-fly calculation as well). Check the model config guide for advice