Product Interchangeability - not working for FULL and USE-UP (YES) strategy

[former_member215376]

Hi Experts,

We have an issue on some of our interchangeability groups (supersession) wherein current stocks of the predecessors were not used for the demands on the successors. The current strategy that we used is Direction (FULL) and Use-up (YES). This is a strange behavior because it was only
last month (May 18th) where this issue was observed and prior dates were still working fine. Logs in the SNP heuristics showed this less Product substitution orders on the mentioned date compared to the previous logs.

I'm not sure but when I checked the INC group master data, nothing has been changed on it for the affected groups. One thing that I noticed was that the Valid-from date was May 12th which means that when Heuristics ran on May 18th, the valid-from date of May 12th was not respected? Not sure on this because some groups still working fine even though the valid-from date was also May 12th.

Please advice on the possible cause of this issue. Also, as we just recently upgraded our APO to 702, are there any notes available that might correct this issue?

Thanks for your usual support.

Regards,

AA

[former_member190993 · Accepted solution]

Hi AA,

Understand that you are using full interchangeability with use up strategy 'yes'. Best practice is to have your valid from date from current date to any date in the future. If you have SNP horizon maintained then this date should be beyond your horizon.

Please change your valid from date from past horizon to appropriate date in future and check if it works.

Regards,

Umesh

[former_member215376 · Accepted solution]

Thanks Umesh,

Are there any SAP notes pertaining to your answers above? Also, the SNP horizon you mean the SNP checking horizon or SNP stock transfer horizon?

Regards,

AA

[former_member190993 · Accepted solution]

Hi AA,

The SNP horizon here refers to SNP production horizon/SNP transfer horizon. I do not find any note exactly mentioning this issue. However, you may refer to SAP consulting notes 1405601 & 1405636 for more information on interchangeability functionality as of SCM 7.0.

Hope this helps!

Regards,

Umesh

[former_member215376 · Accepted solution]

Thanks Umesh,

I'm still checking this possible cause in our Quality system but it seems that we have current setup in Live system that the validity-from-date is also in past and there are SNP horizons maintained from the product-master. The interchangeability is also full and use-up (yes). However, they are having substitution orders also. Are there any causes of this?

I've checked the notes but seems that I can't find any related inputs for the issue that we are encountering. Thanks for the usual help and assistance.

Regards,

AA

[former_member215376 · Accepted solution]

Moreover, while checking the validation logs for the Prod. Inc. goups that has an issue. I found that there's a warning message for validation S_V8 (Prod.& ProdComb.in Multiple ATP Groups) - means not successful. What could be the impact of this warning message in the setup? And how can this be avoided?

Thanks for the help.

Regards,

AA

[former_member190993 · Accepted solution]

Hi AA,

The warning message S_V8 is applicable for ATP relevant interchangeability groups. It means that the product or product combination of this group are already there in other ATP relevant interchangeability groups.

To avoid this, make sure product does not exist in multiple groups or if you do not want system to carry out this check you can make this as active or inactive in customizing under Master data>Product and Location interchangeability>Consistency checks>Maintain validation.

Regards,

Umesh

[former_member215376 · Accepted solution]

Thanks Umesh,

I've seen this configuration in the latest BB for Master Data for Product and Location Interchangeability.

To give you more details on the issue that we are facing in our live system.

For example, Supersession A (pred)<->B (succ), Full Direction, Use-Up (YES). For A, the t-lane assigned is Y->X, while for B it is Y->X and Z->X. The interchangeability is only active at X location only. A has stocks and B don't have but with demands. Validity From Date is in the past.

Can you comment if the setup is correct? Also, as per my understanding, since validity from date is in the past, i would assume that B should have stocks already at X location. If this is the case, then the interchangeability would work as the same for other inc groups scenario.

Regards,

AA

[former_member190993 · Accepted solution]

Hi AA,

Yes, the master data setup is correct. X being the destination location where you can run the SNP heuristic and interchangeability data is only needed at location X, which will create required substitution orders at X.

I tried creating a similar scenario where the valid from date lies in the past. Details below:

Consider below interchangeability group:

Valid from date is in past 25th May.

Demand for 1000-01 lies from July onwards.

Planning run date: 19th June

Result: Substitution receipt are created accordingly from July onwards and the existing stock of 1000-01 is not utilized as per the use-up strategy 'no'.

Hope this helps!

Regards,

Umesh

[former_member215376 · Accepted solution]

Thanks Umesh, appreciate all of this.

I would expect that the use-up strategy YES will use the stocks of 1000-01 after the heuristics run from.

We have raised an OSS message for this issue as there are working groups in our live system but most of the groups wer not with an assumption that all the master data and INC setups are the same.

I'll let you know for any outcome of this.

Thanks again.

Regards,

AA

[former_member215376 · Accepted solution]

Hi Umesh,

Finally, I found the root cause of our issue. In my example above, X has another target location which we can call as location T. This location T are assigned to my predecessors and successors and that only by assigning the preds. and succs. into the T-Lane X-->T, the issue was resolved i.e. substitution orders are now available and cen be created.

In summary, the INC setup is only available at location X, while there's another location T assigned to the products, the INC will not happen unless otherwise the master data has been setup for T-Lane X-->T. Is this note 1918220 discussed the same? Thanks for the help.

Regards,

AA

[former_member190993 · Accepted solution]

That's great AA.

Thanks for the update!

Regards,

Umesh