Filters in Multi-Stage inventory optimization run

[former_member696146]

Hello Experts,

I have a question on the filter usage in multi-stage inventory optimization run.Am i correct in saying that filters are not possible to be used for multi-stage inventory optimization run ? If yes,then do there exists any kind of change pointers which detects only the changed input parameters (like changed demand or changed forecast error numbers etc) based on which optimization run is carried out on only few affected materials instead of entire set of materials in the complete supply chain ? My client is worried on the system performance with every time the complete set of materials being taken with IO run.Can you please throw some light on the same ?

Thanks,

Praveen

[chris_topf]

Hello Praveen,

There are a couple of ways that the IO operator can be filtered:

1. by Subnetwork (Planning Unit)

2. by an attribute (i.e. Product = 'PRODUCT1')

Attribute-based filtering specifically works in conjunction with the Subnetwork (Planning Unit) attribute. To use it, the pre-requisites are defined on the following Help portal page:

https://help.sap.com/viewer/62772a60ce5543e3b46fbd787866b6dc/2008/en-US/66e1caacaecc412dbd5606a64cb6...

When you run the IO operators for a given Subnetwork, the NETWORKID attribute is populated with the specific "network" that each product/location belongs to. For example, if you have a Subnetwork named 'NET1' and you run multi-stage for that subnetwork, the NETWORKID field would be populated with values like NET1-1, NET1-2, NET1-3, etc. Every product/location that has the same value for NETWORKID belongs in the same network. When you use an attribute-based filter (i.e. Product = 'PRODUCT1'), the IO operators select all the product/locations that have the same value of NETWORKID as the attribute you filtered on and the inputs for those product/locations would be used.

There is no change pointer or anything like that with the IO operators.

Hope that helps!
Chris

[former_member696146]

Hello Chris,

Sorry for responding to you quite late.Thanks for your inputs on this topic.

With regards to sub-network,the filter works the way as suggested by you.

Kindly confirm my understanding on the attribute based filter(points given below) :

1) Filter with only product ID (without IO network ID) -->Filter is not respected by IO run.

2)Attribute filter is inputted with IO network ID -->Filter respected by the IO run .

3)Attribute filter is inputted with IO network ID(first filter step) and also product ID(second filter step)-->Filter respected by the IO run

.Please give your feedback on my understanding.

Thanks,

Praveen

[revanchatraban]

Hi Chris,

I have 2 more questions with respect to the above mentioned example:

For example, if you have a Subnetwork named 'NET1' and you run multi-stage for that subnetwork, the NETWORKID field would be populated with values like NET1-1, NET1-2, NET1-3, etc.

1. How is the ID determined like NET1-1, NET1-2 etc..? I mean FG's with ID 1, SFG's with ID 2 etc.. based on the BOM structure.

2. As the attributes are editable, what will be the impact on the IO run when the user changes the NETWORKID ? Whether the attribute is allowed for maintainance or should be updated only by the Operator run?

Thanks,

Revan C