Show TOC

  Goods Receipt Posting Triggered by EWM

Purpose

You receive finished products, in the goods receiving area for example, for which you want to post goods receipt . For this, you are working with expected goods receiptsin Extended Warehouse Management (EWM). In exceptional circumstances, you generate an EWM inbound delivery manually without a template, meaning without an expected goods receipt. In this case you must make sure that the data in the inbound delivery is validated. You can use the standard implementation of Business Add-In (BAdI) /SCWM/EX_ERP_PROD.

EWM uses document type IDPD Inbound Delivery from Production to differentiate that an EWM inbound delivery from production takes place.

For more information about document type determination, see the Implementation Guide (IMG) for Start of the navigation path EWMunderGoods Receipt Process Next navigation step Inbound Delivery Next navigation step Define Document Type Determination for Inbound Delivery Process. End of the navigation path

Prerequisites

  • You are working with SAP SCM and SAP ERP.For more information, see the Implementation Guide (IMG) for EWMunder Start of the navigation path Interfaces Next navigation step ERP Integration Next navigation step General Settings Next navigation step Set Control Parameters for ERP Version Control End of the navigation path .

  • You are using simple transport routes, for example without stock transport orders, so that your goods receipt posting in SAP ERP directly triggers generation of the EWM inbound delivery.

Process

The following figure provides an overview of the process flow:

  1. You generate a production order and release it.

    The production order contains a plant / storage location combination that refers to a warehouse in which you are using EWM. In other words, EWM manages the plant and storage location combination.

    If EWM does not manage the plant and storage location combination, SAP ERP generates a material document immediately at goods receipt posting. You put away the product, and SAP ERP updates the stock. SAP ERP does not trigger generation of expected goods receipts.

  2. If you execute report /SCWM/ERP_DLV_DELETE , EWM deletes any existing expected goods receipts in EWM, and calls SAP ERP function module /SPE/INB_EGR_CREATE_PROD. SAP ERP checks whether relevant production orders atill exist for which you still have to post goods receipt. SAP ERP identifies the relevance from your selection criteria and from the open quantities. If open quantities still exist, then the goods receipt indicator is set in SAP ERP but the final delivery indicator is not set.

    For more information, see Generate Inbound Delivery from Expected Goods Receipt .

  3. For each relevant production order, EWM receives a notification for the expected goods receipt from SAP ERP, and generates a corresponding expected goods receipt in EWM.

    The expected goods receipt contains a link to the production order in SAP ERP. You can use the expected goods receipt in EWM for planning purposes. It contains the planned times and quantities, for example.

  4. You confirm the end of the designated production steps in the production order. In doing this, SAP ERP updates the finished quantity and marks the completed production steps.

  5. You transport the finished products into the warehouse, for example to the goods receiving area.

  6. You can use the number of the production order to find the expected goods receipt, and generate a corresponding EWM inbound delivery. Here you use the expected goods receipt as a template for the EWM inbound delivery, and can adjust the quantities if required.

  7. You post the goods receipt and put away the products.

  8. EWM transmits the goods receipt posting to SAP ERP. SAP ERP also posts goods receipt for the related SAP ERP inbound delivery. SAP ERP also updates the stock in the production order and in the SAP ERP inbound delivery, due to the goods movement.

Result

You have posted goods receipt for your products from production, and updated the stock in SAP ERP.