WhatsApp Button




top of page

Warehouse Document Types

Warehouse Document Types

In this blog, we are going to discuss about types of documents in SAP EWM.

 

In SAP Extended Warehouse Management, document types play an important role in managing and categorizing different warehouse activities. The document type helps in structuring, processing, and tracking various warehouse transactions. 

 

Inbound Process Flow in EWM

How Inbound Delivery Document (IBD) is created in EWM?

The Inbound Process starts from the S/4HANA ERP System. On successful creation of inbound delivery in the ERP system, the system checks if the storage location EWM is managed and then distributes the delivery in WMS.

 

First Inbound delivery notification is created in EWM and we can either reject it by changing the quantity to zero or we can create an inbound delivery in EWM as IDN only acts as an interim document number.

Inbound delivery notification is obsolete in Embedded EWM as of now. An inbound Delivery Document is created in EWM.

 

Outbound Process Flow in EWM

Which all documents related to outbound delivery are present in EWM?

The outbound delivery documents are also triggered from ERP. On successful creation of outbound delivery in ERP, an outbound delivery request (ODR) is created in the EWM system. ODR only acts as interim documents and is further converted into outbound delivery orders (ODO) for which we need to process the follow-on functions like warehouse task creation, packing, and picking.

 

Outbound Delivery Notification (ODN) can either be rejected or activated.

 

Once the Outbound Delivery Order is processed and the goods issue completed. EWM system creates outbound delivery which known as Final Delivery (FD).

 

What is Warehouse Task?

A warehouse task document represents both physical movements and posting change there are two types of warehouse tasks.

 

1)     Product Warehouse Task

2)     Handling Unit (HU) Warehouse Task

 

Which categories are available for warehouse tasks?

1)     Put-away

2)     Stock removal

3)     Internal warehouse movement

4)     Posting Change

 

Which statuses are available for warehouse tasks in EWM?

1)     Open: It is the initial status of any warehouse task.

2)     C- Confirmed: Once the warehouse task is confirmed.

3)     A- Cancelled: If the warehouse task is cancelled

4)     B-Waiting: If any dependent warehouse task is pending for processing. B status will appear.

What are products warehouse tasks and handling unit(HU) warehouse tasks?


A product warehouse task is created for a product, it contains data related to materials, quantity, and destination bin.

 

It can be created for put-away, picking, or internal movement. It can also be created manually without any reference document.

1)     Product Warehouse task creation

2)     Handling Unit Warehouse task creation

What are yard warehouse tasks?

Yard warehouse tasks are used to move transportation units and vehicles in the yard.

What are Warehouse Orders?

Warehouse order documents are used to bundle one or more warehouse documents into work packages.

Based on the warehouse order creation rule (WOCR), when warehouse tasks (WT) are created or activated, they are assigned to warehouse orders. A Waiting/Inactive warehouse task (WT) is never assigned to a warehouse order (WO).

How we can print warehouse orders (WO)?

We can print warehouse orders from the warehouse monitor

What is the Sequence used in the Warehouse Creation Rule (WOCR)?

The below sequence is followed during WO creation as per WOCR.

1.     All WTs are grouped by activity area (AA) and queue. Every group of WTs with the same AA and queue is passed independently to the next step.Note: You can set up the Warehouse Process Type (WPT) if the AA should be based on the source bin or on the destination bin of the WT.

2.     EWM customizing is read to determine which WOCRs exist for the AA. You can set up multiple WOCRs per AA and bring them into a sequence. EWM starts with the first WOCR and passes all WTs to it.Note: If no WOCR is set up, EWM uses a default WOCR called DEF.

3.     EWM applies an item filter and a subtotal filter to WTs. You can use these filters to filter out tasks that do not meet certain conditions, for example, all tasks with more than a specific weight. The subtotal filter is used to filter WTs that do not fulfill certain criteria by consolidation group (the criteria for “subtotal” is always the consolidation group). For example, you can filter out all WTs for a specific consolidation group if there are not at least WTs processed.

4.     All WTs that did not pass the filters of the WOCR are passed on to the next WOCR in the sequence, according to the customizing settings.Note: If there are no WOCRs left in the sequence for the AA, EWM assigns a default WOCR called UNDE (meaning Undetermined).

5.     The WTs that passed the filters are now sorted. The sorting at this step is called inbound sorting. You can configure the criteria for which the sorting will take place. For example, the sequence number of the bin can be used if you want to pick according to the pick path defined by the bin sequence.

6.     The sorted WTs are next checked according to the limits. You can configure limits per WOCR, for example, a maximum of 10 tasks per WO. The limits do not change the WOCR, they only impact on the size of the individual WOs.

7.     Another sorting function, called pack sorting, occurs next. Pack sorting allows you to sort the WTs, for example, by descending volume.

8.     Next, the packing profile is applied to each WO. Packing materials can be assigned to the WO based on weight, volume, or dimensional data. Pick HUs can be created and assigned to the WO based on the determined packing materials. If the WTs do not fit completely in one Pick HU according to the capacity of the packaging material, they can be split into multiple HUs.

9.     Finally, a last sort is executed, called WT sorting. Using WT sorting, you can sort the WTs once again, for example, by pick path. This lets you sort the tasks for picking within the WO (as opposed to the previous sorts that occur before the splitting of the WOs and therefore are used primarily for determining which items are included within each WO).

 

What is Wave Document in EWM?

Waves are used to group delivery items and to create warehouse tasks and warehouse orders for the group of delivery items.

It can be created manually or automatically.

1. Create a Wave Template



What are Physical Inventory Documents in EWM?

PI documents are the basis for the PI process. They are used to plan the PI, perform the counting, record the count data, and post the differences that can occur during the count.


1)     Create a Physical Inventory Document

2)     Process Physical Inventory Document

Which functions can be performed on the Physical Inventory Documents?

1.     Activate or Deactivate: A deactivated PI is not assigned to any warehouse order.

2.     Count

3.     Re-count

4.     Delete: cannot delete a PI document if a difference is posted

5.     Post

6.     Print

 

What are stock transfer and posting change documents in EWM?

In EWM stock posting and transfer posting are two different documents where a stock transfer can be done from one bin to another bin, and location changes.

Posting Change refers to a change in stock type.

We can directly create warehouse tasks for transfer posting using

1.     T-code: /N/SCWM/ADPROD- To move Product

2.     T-code: /N/SCWM/ADHU

We can use the same transaction to create WR which creates an internal delivery document, which can be used to create multiple warehouse tasks or assign warehouse tasks to a wave.

3.     T-code: /N/SCWM/POST used to create a posting change.

How do post-stock transfers and posting change directly from EWM?

1)     We can create warehouse requests using T-code: /N/SCWM/IM_ST

2)     We can create warehouse requests using T-code: /N/SCWM/IM_PC


Rajesh Sharma

SAP WM/EWM Functional Consultant




190 views0 comments

Comments


bottom of page