Show TOC

Process documentationSupersession

 

In this process, you can plan the substitution of one or more products with one or more different products. You specify when the discontinuation of the products is to begin. Based on this date, the system plans the substitution of the respective products by calculating the necessary date values for the substitution, and continually checking their ability to be realized.

The system calculates the date values for the supersession at entry location level only. However, here it takes into account all of the child location products of the entry location product. If you plan one or more of these child location products in the reorder-point-based planning mode, the supersession service does not take into account these child location products when it calculates the date values for the entry location product.

If you plan an entry location product and all its child location products in the reorder-point-based planning mode, you must select the Check ROP dropdown box in Customizing for Advanced Planning and Optimization, under Start of the navigation path Supply Chain Planning Next navigation step Service Parts Planning (SPP) Next navigation step Supersession Next navigation step Define Service Profile for Supersession End of the navigation path.

  • If you choose Skip Planning for ROP Products from this dropdown box, the system checks if the sub-BOD of the predecessor product contains only ROP-based location products. Planning is skipped for ROP products. No dates are calculated and a warning is output in the log. This is the default setting.

  • If you choose Set SED to Planning Date from this dropdown box, the system checks if the sub-BOD of the predecessor product contains only ROP-based location products. If this is the case, the system sets the current date (the date of running the service) as the date for the following:

    • At each entry location of the predecessor product's sub-BOD that contains only location products with ROP-based planning:

      • the stock exhaustion date

      • the stock exhaustion warning date

    • At the successor product entry locations:

      • the successor product planning date

      • the successor product receipt date

    This also means that the system creates these entry points in the chain in the interchangeability master data. An information message is also output in the log.

  • If you choose Push SED While Stock Exists on Predecessor from this dropdown box, the system checks if the sub-BOD of the predecessor product contains only ROP-based location products. If this is the case, the system sets the next working day as the date for the following:

    • At each entry location of the predecessor product's sub-BOD that contains only location products with ROP-based planning:

      • the stock exhaustion date

      • the stock exhaustion warning date

    • At the successor product entry locations:

      • the successor product planning date

      • the successor product receipt date

    This also means that the system creates these entry points in the chain in the interchangeability master data. An information message is also output in the log.

To use the Check ROP dropdown box, you must activate the SCM-APO-SPP, Service Parts Planning 1 (SCM_APO_SPP_GEN_1) business function. For more information, see SCM-APO-SPP, Service Parts Planning 1.

Prerequisites

You have made the necessary settings in Service Parts Planning (SPP) as well as in the master data for product and location interchangeability. For more information, see Supersession Settings in SPP.

Process

  1. You want to substitute a product and specify the start of the discontinuation period. For more information, see Definition of the Discontinuation Period Start Date.

  2. Before planning supersession, the system checks the following master data for product and location interchangeability:

    • Group type

    • Application relevance

    • Status

    • Start date of the discontinuation period

    If you have not specified the group type or application relevance correctly, the system creates a message in the application log. If you have not completely entered the start date or status of the discontinuation period or if you entered it incorrectly, the system generates an alert for the analyst so that he or she can manually postprocess the corresponding master data and then release it.

  3. The system checks the start date of the discontinuation period and only calculates more date values if this date has already been reached. If the date still lies in the future, the system does not calculate the stock exhaustion date and the planning date. If the date has been reached, the system continues with step 4.

  4. The system calculates the stock exhaustion date. This date depends on the entry location and specifies when the available stock of the predecessor product is likely to be used-up. For more information, see Determination of the Stock Exhaustion Date.

  5. The system calculates from the stock exhaustion date backward to determine the successor product planning date. For more information, see Determination of the Successor Product Planning Date.

  6. The system carries out steps 4 and 5 until it reaches the product planning date for the successor product.

  7. On reaching the planning date for the successor product, the system realigns the predecessor product demand history for the successor product, and begins forecasting, inventory planning, and distribution requirements planning (DRP) for the successor product. On the planning date for the successor product, the system also calculates the stock exhaustion warning date. For more information, see Determination of the Stock Exhaustion Warning Date.

  8. The system checks daily if the stock exhaustion date comes before the stock exhaustion warning date and, accordingly, whether the stock of the predecessor product runs out earlier than planned. If this is the case, the system creates an alert. For more information, see Monitoring of Destocking.