Introducing Warehouse Inbound Processing

Objective

After completing this lesson, you will be able to execute warehouse inbound processing

Warehouse Inbound Processing

This process enables you to receive and store products in your warehouse. It supports various inbound processing variants, such as from a supplier, other storage locations, or another plant. Products intended for storage are received and moved to a storage bin.

Incoming goods are initially received in storage type S910, the goods receipt area.

Goods requiring packing or inspection are moved to storage type S970, the clarification zone.

At the end of the inbound process, goods are moved to final storage bins in regular storage types. There are three different storage types:

  • Bulk Storage: This storage type is divided into columns of single bins where multiple storage units are placed according to size and dimensions.
  • Fixed Bin Storage: This storage type is used if you want to put away a product in a fixed storage bin because you pick the product usually from this storage type.
  • Standard Storage: This is the most common storage type used to store different types of products, for example a high-rack storage.

The process begins with an inbound delivery relevant for warehouse processing. Upon arrival, the delivery is checked, and products can be packed into handling units as needed. The warehouse clerk creates or finds an appropriate batch for batch-managed material and assigns it to the inbound delivery items.

Afterward, the goods receipt is posted, and warehouse tasks are created to execute the movements. Once products are moved to the final bin or the clarification zone (in exceptional cases), the warehouse tasks are confirmed.

Automatically Pack Unpacked Products – Inbound

Packing proposal in Change Inbound DeliveriesUI Example showing the Pack Automatically button in the SAP Fiori app Change Inbound Deliveries
Button to perform automatic packing in the app
Automatic packing during inbound delivery creation - based on configuration
Activation of automatic packing - configured on document type levelUI Example showing the designated partner roles and check boxes to allow or disallow the activation of automatic packing for Inbound Delivery Process Document Types
Partner role used to determine the packing instruction - configured on document type level

It is also possible to use packing proposals to optimize the packing process in inbound. Alternatively automatic packing can be carried out.

Using the app Change Inbound Deliveries it is possible to add or change batch information for batch-managed products. You can perform a batch split and create new batches.

Note

Watch the video to learn more about this feature.

Choose the correct language for closed captions (CC-label within the embedded media player), in order to choose your preferred language.

Business Benefits

The following is a list of business benefits:

  • Receive products from different sources and store them in your warehouse.
  • Control and record movements of products and handling units in the warehouse.
  • Map your warehouse complex in the system down to storage bin level.
  • Improve visibility and control in warehouse operations.
  • Handle exceptions.

Key Process Flow

  • Improve visibility and control in warehouse operations:

    If the material procured is handled in batches, you can, optionally, create the batch manually, before the inbound process. Batches can, however, also be created automatically by the system during inbound processing.

  • Create handling units and print labels (optional):

    If the product is managed in handling units (for example, pallets with a unique ID), the handling unit has to be created in the system. Normally, this process step also involves the printing of the handling unit labels required for scanning the handling unit in the warehouse processes.

  • Post goods receipt:

    After the goods have been received in the warehouse, the goods receipt is posted in warehouse management.

  • Create putaway warehouse tasks and print putaway lists:
    • The inbound processing in the warehouse is triggered by the creation of an inbound delivery. The original document for the inbound delivery creation could be a purchase order sent to an external supplier/vendor, a customer return order, a stock transfer from another storage location, or an intra-company process (inbound from another plant).
    • The creation of the corresponding inbound delivery order in the warehouse leads to a warehouse request that has to be covered by the creation of putaway warehouse tasks assigned to a warehouse order. The warehouse order is carried out by the warehouse worker, who confirms the warehouse tasks. Putaway lists might have to be printed for this process step as well.
  • Confirm warehouse tasks:

    After the worker has finished the putaway activities, he or she confirms the warehouse tasks carried out.

  • Check material in clarification zone (optional):

    If required data for the process is missing, for example, a product putaway control indicator, the material is sent to the clarification zone for further checking and processing.

  • Create warehouse tasks from clarification zone to final bin and print warehouse task lists (optional):

    After checking and correcting the issue, the material can be moved to the final bin by the creation of warehouse tasks and an optional printout of the warehouse task list (in a paper-driven environment).

  • Confirm warehouse tasks (optional):

    After the worker has completed the warehouse activities from the clarification zone, he or she confirms these warehouse tasks as well.

    For a graphical overview on the business process of the scope item Warehouse Inbound Processing (3BR), refer to the SAP Signavio Process Navigator as described in the lesson Finding Best Practices Documentation via SAP Signavio Process Navigator.

Run a Simulation to Check the System Behavior

Use this simulation to guide you through the main process steps about how to run the warehouse inbound process.

Business Roles and SAP Fiori Apps

The following SAP S/4HANA Cloud business roles are used for this scenario:

  • Warehouse Clerk (EWM)
  • Warehouse Operative (EWM)
Process StepUser RoleSAP Fiori App
  • Assign/create batch
  • Change stock type
  • Create handling unit
  • Post goods receipt
  • Create putaway warehouse tasks
Warehouse Clerk (EWM)Change Inbound Delivery - Deliveries
Check warehouse KPIsWarehouse Clerk (EWM)Warehouse KPI Operations
Confirm warehouse tasksWarehouse Operative (EWM)Confirm Warehouse Tasks

Process Warehouse Tasks - Putaway

Clarification Zone:
  • Check material in clarification zone
  • Create warehouse task from clarification zone to final bin
Warehouse Clerk (EWM)Warehouse Management Monitor
Clarification Zone:
  • Confirm warehouse tasks
Warehouse Operative (EWM)Confirm Warehouse Tasks

The Roles and Apps Used in the Scenario Warehouse Inbound Processing figure shows the roles and SAP Fiori apps involved in the process. Whereas the warehouse clerk is responsible for the main process steps, the warehouse operative carries out and confirms the warehouse activities.

Log in to track your progress & complete quizzes