Inbound Integration 

Purpose

You can use this process to integrate Contract Packager (CP) in the purchase inbound process.

Process Flow

The following figure illustrates the process flow

       1.      Create purchasing document (Supplier)

The purchasing of service parts from the supplier is established by a scheduling agreement between the supplier and the company. The types of items defined by these agreements include the:

¡            Material purchased

¡            Total quantity for a time period

¡            Price conditions and the receiving location

If CP is involved, the receiving location at the item level is defined using the combination of plant and storage location. This combination identifies the primary/planned CP to receive the goods. The storage location should be a CP-AFS storage location, which is the master storage location of the CP MRP area. If only a plant is specified as the receiving location, then it is assumed that no CP is involved in the process.

       2.      Send purchase order/release to supplier

The released scheduling agreement is sent to the supplier. The purchase documents contain the material, quantity, expected date of arrival and reference of the item in the scheduling agreement. For a CP, the address data is the address of the storage location.

       3.      ASN from the supplier

The supplier sends an advanced shipping notification (ASN) to announce the physical goods arrival date, quantity, and the ship-to-location. The reference of the item in the scheduling agreement is also contained in the ASN. If the goods are delivered on the basis of a scheduling agreement with a CP, then both the plant and the storage locations are required in the supplier ASN IDoc.

       4.      Create the inbound the delivery (SAP ECC)

The consistency of the data in an ASN is checked in the validation framework. The validation of the ship-to-location is adjusted for CP scenarios. For more information, see the validation integration. Depending on the checking criteria and the Customizing settings, an inbound delivery is created in the ERP system. Based on the result of the validation, the inbound delivery is set to Real or On Hold. The creation of an inbound delivery updates the scheduling agreement in background processing.

       5.      Dispatch the inbound deliveries (SAP ECC)

The dispatch of inbound deliveries to SAP EWM is based on a warehouse assignment made at the plant/storage location. This makes the CP itself work as an extended warehouse management system.

       6.      Goods in yard at CP (SAP EWM)

When the goods arrive in the yard at the CP, SAP EWM sets then the status of the corresponding inbound delivery to In Yard, and communicates this status to the ERP system. This status update is then dispatched to SAP ICH and SAP SCM.

       7.      Goods receipt at the CP (SAP ECC)

After the goods are received, unloaded and posted in CP, the status changes from In Yard to Received on dock (ROD). SAP EWM at the CP then sends the posting data to the ERP system, which triggers the goods receipt posting in the ERP system. Then the stock is then visible at storage location CP_ROD. SAP SCM-APO is informed by core interface (CIF), and the ERP system sends the update of the inbound delivery to SAP ICH.

For more information about the Inbound Processes, see Extended Inbound Delivery Processing.