Executing Expected Goods Receipts Processes

Objective

After completing this lesson, you will be able to execute expected goods receipts processes.

Overview of Goods Receipts Documents

The main feature of expected goods receipt (EGR) processing is the ability to plan goods receipts (GRs) within SAP EWM, without an inbound delivery in ERP. Using expected goods receipt offers advantages. For example, it serves as a template to create inbound deliveries (either automatically or manually) and calculations of expected workload can be based on expected goods receipt (and then displayed in the Warehouse Management Monitor).

If an expected goods receipt is used to generate an inbound delivery manually for a purchase order or production order, the process has the following advantages:

  • Execution of the good receipt process starts in SAP EWM.

  • If ERP is temporarily unavailable, you can still execute the physical goods receipt process.

  • The inbound delivery data has been checked by both ERP and SAP EWM. This also ensures a posted goods receipt in ERP.

  • Since the expected goods receipt is based on an open purchase order or open production order data, you can use the expected goods receipt as a preview of the goods receipt.

The following figure shows how the SAP EWM GR process uses EGR data as part of the product check-in process.

The graphic outlines the process flow for expected deliveries, from check-in and goods receipt preparation to unloading and release, with key checks and comparisons at each step.

In this process, any product that is received, but does not appear in an existing inbound delivery, can still be received. The inbound delivery can be updated from the expected goods receipt data.

Expected Goods Receipts Documents

There are two methods to transfer data from the purchase order or production order. As a result, an expected goods receipt notification document is created:

  • Push Scenario: The process is triggered in ERP by executing the report /SPE/INB_EGR_CREATE. (This is transaction /SPE/EGR).

  • Pull Scenario: The process is triggered in SAP EWM by executing the report /SCWM/ERP_DLV_DELETE. (This is transaction /SCWM/ERP_EGR_DELETE).

In both the push scenario and the pull scenario, the consistency check of data is automatic. With the transaction code /SCWM/EGR, it is also possible to execute the consistency check manually in SAP EWM.

The Notification of Expected Goods Receipt (GRN) is created based on either a purchase order or production order in ERP. This interim document contains a copy of all of the relevant logistical data from the source document.

Based on the GRN, the EGR document is created either manually using a transaction (/SCWM/GRN) or automatically, using PPF. This document contains all of the relevant data from the GRN. It is a temporary document that exists in SAP EWM (and not in ERP). It is used as a template to manually create SAP EWM inbound deliveries.

The graphic illustrates the process flow of inbound delivery creation in SAP, showing integration between ERP and EWM using expected goods receipt notifications and deliveries.

Note

In SAP S/4HANA embedded EWM, the whole scenario is simpler. The report to create the expected goods receipt documents (GRN and EGR) is not required, these two documents no longer exist. With the transactions for GR Preparation (description following), the inbound deliveries can be created directly with reference to a purchase order or a manufacturing order.

In a decentral EWM system, the expected goods receipt notification (GRN) can be skipped, similar to the other notification documents.

Note

For manufacturing orders it is meanwhile not necessary anymore to schedule the job for the creation of the expected goods receipt (notification). The EGR document can be created, updated, and deleted automatically when a manufacturing order is released or updated. For more details, see the SAP Note "2811153 - Manufacturing Integration: Automatic creation / update of expected goods receipt in SAP EWM".

Based on the EGR document, an inbound delivery is created in the SAP EWM system. For this, there are two transactions:

  • GR Preparation – External Procurement (/SCWM/GRPE)

  • GR Preparation – Production (/SCWM/GRPI)

For an EGR for a production order, the inbound delivery can also be created through RF, but for this, it is expected that the material is packed in an HU (Receive HU by Manufacturing Order).

In a production integration scenario, it is also possible that no inbound delivery is created in ERP, but only a material document for the goods receipt posting.

GR Workload List

Goods receipt processing enables the display of data to assist planning for products that are to be received into the warehouse (over a chosen time frame). This information is provided through the Goods Receipt Workload List.

The GR Workload List is executed with transaction /SCWM/GRWORK. It provides for time-dependent data aggregation, based on inbound deliveries and expected goods receipts. Data on the report is aggregated at these levels:

  • Number of items

  • Number of HUs (using a BAdI)

  • Weight and volume

  • Customer fields (using a BAdI)

Learning

SAP FacebookSAP YoutubeSAP LinkedIn