Populating the AGGCONSTRAINT master data makes the optimizer ignore the Agg constraints KFs?

[eddyizaguirre3]

Hello Experts,

I am trying to use the aggregated constraints Key figures "MAXAGGPRODUCTION" and "MINAGGPRODUCTION" at planning level CAL week | Product | Location | Source AGG ... to constraint my key figure "PRODUCTION" at Planning Level week | Product | Location | Source on calendar weeks W09 2019, W10 2019, W11 2019.

Example below

These are my results after running the optimizer:

As you might notice, what is happening is that the AGG constraints are not being taken into account in W11 2019, I am expecting to have a value of 40 in this week. I have tried this several times, and the only conclusion i have is that it's not working because i am populating the "aggregate" attribute in my Agg Planning level with a value that is not "__NS" which is how in the SAP HELP portal they tell you is the notation to ignore this attribute. Every time I do that the agg constraint gets ignored.

I have a couple of questions:

• Is that a normal behavior of the agg constraints? Am I supposed to always populate the "Aggregate" attribute with "__NS" only?

Have any of you had this case before?

Thanks for the support

[ankpatel · Accepted solution]

Check out if you can use CPI task to update Min Agg numbers from your Production.

[eddyizaguirre3 · Accepted solution]

Hi Ankur,

I tried this using a CPI task, one of my coworkers who is a CPI user helped me and it worked. I am still unsure why it doesn't work very well with the planning operators, I will wait for the incident to be answered and let you know.

Thanks!

[ankpatel]

Eddy, it makes sense of what you are looking for. Did you check in the DISAGG logs on any error or information messages?

[eddyizaguirre3]

Hi Ankur,

There aren't any evident errors, at the end it just tell me that the number of planning objects disaggregated was zero. I actually opened an incident and it's being processed.

Another approach I am working on to tackle this is to use a dummy BOM and use each aggregated attribute as a "component" of each SKU.

I'll see how it works and tell you about it. If you have any other idea on how to tackle this, I am more than open to suggestions.

Thanks!

[ankpatel]

That is correct if you don't maintain aggregate constraint it will not work. Also, what exactly you want to use copy/diagg to this KF for?

[eddyizaguirre3]

The reason is the customer wants to "Freeze" the production plan at an aggregated level.

This is an Example of my vision for the solution:

Let's say I run my optimizer and I get the following results (This is an aggregated view)

Since they want to Freeze it at an aggregated level, I cannot use the freeze horizon solution that comes as a standard in IBP, because that will only freeze it at the Product ID location ID level. I need it higher.

So my idea was to use a DISAGG operator to aggregate the Production receipts quantities and Copy them in the Agg Production receipts Constraint KF, like this

But... since the aggregate constraint need that "__NS" value, the DISAGG is not working... it's like the operator doesn't see the planning level.

This was the whole reason for my question. If I populate the aggregate attribute with a value other than "__NS" then the DISAGG operator would work, but according to your answer that will make the optimizer ignore the constraint.

So now i'm in at lost with this request.

Sorry I wrote a lot. Does this makes sense??

[ankpatel]

Hi Eddy,

Yes, you have to populate Aggregate constraints with "_NS" for the attribute you don't want to upload data. Can you check if you can see the data in the Master Data Planning Object?

Regards

Ankur

[eddyizaguirre3]

Thanks for your reply!

Yes I can see the data. But If the Aggregated Attribute it's not meant to be populated, than this creates a problem for me.

How is a COPY operator or a DISAGG operator going to work, if for example, a customer wants to " Freeze" the production plan at an aggregated level? . Whenever I try these operators they don't work in the planning object with "__NS" so I could not perform this operation. Have you ever tried?

Is the only option we have right now to copy manually the values to the aggregated constraints?