Show TOC

 Creation of a Posting Change Delivery

Purpose

Surplus planning checks warehouse stock for excess inventory and determines whether the excess should be stored or scrapped. The system can do this periodically, or for specific tasks, for example, to make warehouse space available or reduce the total inventory value.

SAP APO evaluates the inventory and determines whether a part is surplus or obsolete and, as a result, can be scrapped. When excess or obsolete stock occupies space at a warehouse, SAP APO generates a scrap order, based on predefined settings, and posts the scrap information to the ERP system. The ERP system coordinates the data flow between SAP APO and SAP EWM by:

  1. Receiving the SAP APO information

  2. Creating a Posting Change Delivery

  3. Initiating the Posting Change Request (PCR) in SAP EWM to execute scrapping

Prerequisites

  • If more than one storage location exists, then all the storage locations must determine a single warehouse number, which is allotted for the combination of each plant and its storage location(s)

  • The scrap order contains material(s) from one plant

  • The value of scrap indicator is one of the following:

    • A - Scrap Entire Inventory

    • B - Scrap Inventory with Retention Quantity Constraint

    • C - Scrap Predetermined Quantity

Process Flow

The system creates the Posting Change Delivery in the following steps:

  1. ERP receives the scrap information from SAP APO.

  2. The ERP CIF Inbound interface contains the scrap information that SAP APO has sent.

    Note Note

    This information is mapped to the corresponding ERP structures, and the scrap information is sent to the ERP system via CIF structures.

    End of the note.

  3. The system prepares the data with a Goods Movement Business Add-In (BAdI) (/SPE/SSE_DETERMINE_P) by:

    1. Determining the scrap’s storage location, stock type and quantity, such as scrap or keep quantity

    2. Assigning a code to create the Posting Change Delivery

    3. Assigning a posting date

  4. The system validates the data.

    Note Note

    If the validation fails, the ERP system captures the error messages and writes to the CIF application log. A resulting error log appears in the return table.

    End of the note.

  5. The system creates the Posting Change Delivery and sends the validated data to SAP EWM, which creates a Posting Change Request.

  6. The ERP system inserts the scrap indicator in the outbound queue.

  7. The ERP system sends the delivery number to SAP APO along with the Globally Unique Identifier (GUID) information. The item table shows the resulting information, including the:

    • ERP generated delivery number

    • Line item number indicating the number of lines in the item detail of the delivery

    • Scrap order ID

    • GUID for schedule lines