Product Interchangeability functionality in APO SNP provides the system ability to plan discontinuation of products. The products are substituted or replaced with another product due to various business purposes, which can be addressed through product interchangeability functionality.
Possible business scenarios:
Product interchangeability function helps the organizations to achieve the following:
Product interchangeability in supply network planning is used to transfer demand of a product to be discontinued on to a successor product or to use existing stock of a current product to meet demand for the successor product. APO SNP supports the following product interchangeability methods:
1. Supersession: A ---> B <---> C
- Product A is forward interchangeable with product B. The product B and C have forward and backward relationship and are fully interchangeable. The substitution valid from <date>, use-up strategies as no/yes/restricted until <date> are used.
2. Discontinuation A ---> B
- Product A is replaced by product B
The supersession and discontinuation use the parameters like valid from date. The substitution valid from <date>, use-up strategies as no/yes/restricted until <date> are used.
3. Form-fit-function (FFF) class: It is a grouping of interchangeable parts which are identical in technically properties (form, fit, function). The FFF class has fully interchangeable products with no validity dates. The FFF class contains at least one FFF subset, which has a leading product defined. The leading product is only ordered/procured.
Pre-requisites and Master Data for Product interchangeability:
Interchangeability group- creation
Model assignment:
FFF Class and FFF subset:
Interchangeability in SNP:
To address product interchangeability functionality in SNP, the below points should be ensured:
FFF Class in SNP:
Interchangeability functionality in CTM:
Interchangeability in SNP- Integration with R/3:
The following restrictions exist with respect to transfer of SNP planning results from APO to R/3:
Uploading discontinuation information from R/3:
XML upload functionality can be sued to upload the interchangeability or discontinuation information from R/3 to APO. XML upload can be done in the following two ways:
Restrictions in Supersession chain:
The following restrictions exist for the maintenance of supersession chain:
Demo:
Scenario 1: Forward interchangeability with restricted use-up strategy
Consider the below interchangeability group with forward interchangeability and use-up strategy- restricted. As per the group, the product 1000-01 needs to be substituted with product 1000-02 from 14th July and the stock of product 1000-01 can be used up to 28th July to meet it's demand, after this date even if the stock of 1000-01 exists, that should not be used to fulfill its demand instead distribution orders should be created.
Before planning situation:
In the below screenshot the stock of 70 is not used to fulfill the demand from 28th July onwards as the use-up date is 28th July in the interchangeability group.
SNP planning is executed: Planning creates substitution receipt for product 1000-01.
Corresponding substitution demand is created for successor product 1000-02.
Scenario 2: FFF classes with CTM planning
Below is the FFF subset consisting 3 products 1000-03, 1000-04 & 1000-05 with the leading product as 1000-03.
Demand exist for member products: 1000-04 & 1000-05
CTM planning is executed using FFF class, product interchangeability option:
The substitution demands are created for the leading product 1000-03.
References:
http://help.sap.com/saphelp_ewm70/helpdata/en/b4/92ea509775e85ee10000000a44538d/content.htm
SAP Note: 1405601- Implementation recommendations for APO 7.0 SNP, CTM and VMI
SAP Note: 1405636- Implementation recommendations for APO 7.0 MD, INT, INC
SAP Note: 617281- Migration of discontinuation data: SAP_BASIS 610 as above
SAP Note: 617283- Migration of discontinuation data: SAP_BASIS 46C and below
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 | |
1 |