S&OP Operator IBP Supply Optimizer in technical weeks

[carlos_perez8]

Dear all,

We are running SAP IBP Supply Optimizer, and we have noticed in the results that for example: Production Receipts key figure (output of S&OP Operator) is not consistent in technical weeks with the available capacity (the same for the adjusted capacity). This seems to be because operator is running in weeks instead of technical weeks, and the result is split 50%-50% where one week has two technical weeks. Example:

Production Wn = 100

Production Wna = 50

Production Wnb=50

Even the available capacity is set in this way:

Capacity Supply Wn=100

Capacity Supply Wna=100

Capacity Supply Wnb=0

My question is, may I run S&OP in technical weeks? I have tried but received below error: Time periods of operator and aggr. constr. key figures are not identical.

But we are not using aggregated constraints.

Thanks,

[former_member654033 · Accepted solution]

Hi,

If you want to run S&OP Operator (Optimizer) at TW level and don't want aggregate constraint to be considered then you can remove all the aggregated key figure from supply planning by removing the drop down "Input to Supply Planning"

Aggregate constraint Key figure planning level cannot be changed to TW (Lowest level for them as to be CW) so you have to remove them as input for supply planning (Read below SAP Help link about aggregate KF Planning level considerations)

Configuring Planning Levels for Aggregated Constraint Key Figures

Please try and let me know if this works.

Thanks

Girish

[carlos_perez8 · Accepted solution]

Thanks, I have tried by removing all the 16 key figures for aggregated constraints as input for supply planning, and also removed the flag for aggregated constraints. But before trying to activate the planning area, when I run a consistency check for the PA it fails with error message like the one below for each key figure:

Key figure MAXAGGDEMAND must be specified as input for supply planning and Key figure MAXAGGDEMAND must be an aggregated constraint key figure.

The same message for every KF changed.

[former_member654033 · Accepted solution]

When I tried this in some of this aggregated KF in my system, it only gave warning messages but Check was successful. If this is not working for you then I don't think that you can run optimizer at TW level as aggregated constraints cannot be setup at TW Level.