SAPPractical.com

1/29/2016 8:59:09 PM

This blog will be covering about Inbound Process with Repacking for Putaway in SAP EWM-A truck arrives at the checkpoint and drives to the door, Check the delivery note and assign the inbound deliveries to the TU, Unload the truck and check the goods, Check goods on the staging area Post the goods receipt and create WOs-SAP EWM,Check goods on the staging area and other steps.

Introduction

When the truck arrives, the check-in office creates a transport unit (TU) in SAP EWM and directs the truck to a door. The truck driver hands over the delivery notes to a warehouse clerk, who brings them to the goods receipt office. The GR clerk finds the corresponding inbound deliveries in the system and assigns them to the TU. After the truck is unloaded, the warehouse clerk checks the number of unloaded pallets at the staging area and the truck can leave. The warehouse clerk checks the quantities on the pallets and builds a single handling unit (HU) for each inbound delivery. For this purpose he prints multiple labels with the same HU number on an external printer and attaches them to all pallets of one delivery and to the delivery note. He then takes the delivery note to the GR office. The GR clerk corrects the GR quantities, creates the HU for each delivery and posts the goods receipt. Upon goods receipt, the system automatically creates and confirms a HU warehouse task to move all pallets of one delivery to a bin located in the inbound section of the packing station. At the packing station, a packer repacks the goods onto pallets used for storage. Once a HU is closed, EWM automatically creates the HU warehouse task for the putaway of the pallet to the final bin. A forklift driver executes the putaway with the help of a mobile device.

Step 1) A truck arrives at the checkpoint and drives to the door (SAP EWM)

The checkpoint clerk creates a TU. He writes the TU number on one of the delivery notes. As the goods delivered regularly by the vendor are always unloaded at the same doors, the checkpoint clerk checks if one of those doors is free. If yes, he assigns a door to the TU and directs the truck to the assigned door. Assuming a small to medium size yard the checkpoint clerk confirms the arrival of the truck at the door. This step is necessary for the checkpoint clerk to see that the door is occupied. If no door is free yet, the truck driver must wait. The checkpoint clerk informs the truck driver as soon as a door is free and assigns then the TU to the door.

For large yards it would be possible to have the arrival at the door confirmed by the GR office in a separate step. In this case the checkpoint clerk only confirms the arrival of the truck at the checkpoint.

Physical Activity: A truck reached, The checkpoint clerk notes the transport unit (TU) on the delivery paper and communicates the door. The truck drives to the door.

System Activity  : A checkpoint clerk creates a transport unit (TU) and assigns the TU to a door and confirms the arrival of the truck at the door.

Step 2) Check the delivery note and assign the inbound deliveries to the TU (SAP EWM)

The truck driver brings the delivery notes to the goods receipt office. The GR office clerk finds the corresponding inbound deliveries in the system and assigns them to the TU.

Note: If an inbound delivery does not exist yet due to a communication failure of the ASN, the GR office clerk creates the inbound delivery manually with the external delivery note number. If the ASN communication failure is solved after manual creation of the inbound delivery, the system will issue an error upon ASN reception and no duplicate will be created.

Physical Activity: Here no Physical Activity so only system activity

System Activity  : A GR office clerk assigns the inbound delivery items to the TU. GR office cleark creates HU's with unknown content. The createa a collective HU and prints labels for the HU's with unknown content.

Step 3) Unload the truck and check the goods (SAP EWM)

The unloading can carried out at the same time as the previous step. 

A forklift driver unloads the truck. When the warehouse clerk comes back from the GR office, he counts the number of unloaded pallets per delivery. He or she writes it on the delivery note then hands over the delivery notes to the truck driver, who takes the revised delivery note to the GR office.

Note: The activities above are not carried out in the system.

Physical Activity: A warehouse clerk checks the goods against the delivery note. 

System activity  : No system activity

The GR office clerk confirms the unloading.

Step 4) Check goods on the staging area

In this process, this step is not realized in the system.

For each inbound delivery, the warehouse clerk working at the staging area prints on an external printer as many HU barcode labels as the number of pallets plus one label to be used by the GR clerk for the creation of the HU in the system. All HU barcode labels of one delivery have the same HU number (needed for moving the physical HUs of one delivery to the packing station).

The warehouse clerk checks the goods against the delivery note, attaches the HU barcode label on each pallet and takes the delivery notes with annotations and the additional HU label to the GR office.

In case of quantity differences, you write annotations on the delivery note.

Physical activity : No Physical activity

System Activity   : The GR office clerk checks the quantities and posts the goods receipt and the system creates WOs


Step 5) Post the goods receipt and create WOs (SAP EWM)

The GR office clerk adapts the inbound deliveries according to the annotations on the delivery notes. In case of a quantity deviation or a missing product, the GR office clerk adjusts the quantity in the system with an appropriate process code. In case an additional product has been delivered, the GR office clerk creates a new inbound delivery item for the additional product.

The GR office clerk creates the HUs with unknown content (“dummy” HU) for each inbound delivery using the external HU number according to the label printed on the external barcode printed in the staging area.

Finally the GR office clerk posts the goods receipt for the TU. The system communicates the goods receipt to SAP ERP. When the GR is posted, the system automatically creates the HU-WTs and warehouse orders (WOs) to move the goods to the next empty bin of the inbound section of the packing station. All pallets of one TU will be moved to the same bin. If the WOs cannot be created because all inbound bins of the packing station are occupied, the system regularly re-tries to create the WOs automatically.

Step 6) The truck leaves (SAP EWM)

The truck leaves the door and the premises. The GR office clerk confirms the departure of the truck from the checkpoint and from the door. This step is necessary for the checkpoint clerk to see in the system that the door is free.

In large yards, the checkpoint clerk can confirm the departure from the checkpoint separately. In this case, the GR office clerk only confirms the departure of the truck from the door.

Step 7) Move the HUs to the packing station (SAP EWM)

In this step a warehouse worker moves the HUs to the packing station. This step is executed using a mobile device.

When the warehouse clerk comes back from the GR office, he signals a forklift driver to start removing the pallets from the staging area.

The forklift driver picks the first pallet from the staging area and scans the HU label of the pallet with his mobile device. The destination bin in the inbound section of the packing station appears on the display. He drops the pallet on that bin. He proceeds the same way with all pallets from the staging area.

A peculiarity of this process is that the system creates one HU WT for all pallets of the delivery and confirms it before the pallets are physically moved to the packing station. As a consequence the HU is already located at the packing station in the system. The forklift driver executing the physical move queries the current location of the HU in the system in order to know where he has to bring each pallet to.


Step 8) Repack the goods and create putaway warehouse orders(SAP EWM)

The inbound section of the packing station is divided into several bins. Each bin is equipped with a card holder. One packer inserts his card into the card holder of one bin to signal that he is working on that bin. He picks up the first pallet from that bin and scans its HU label. The HU is displayed automatically by the system. He navigates to the HU content, picks a product from the HU and selects the corresponding HU item in the system. The system displays the total quantity of the delivery item and proposes a packaging material and a target quantity for the product. The packer adjusts the item quantity if necessary and repacks the product onto the new HU. The HU is created in the system upon confirmation of this step. Upon HU creation a HU label is printed automatically. The packer attaches the HU label to the HU. If he has packed exactly the target quantity onto the HU, he closes the HU immediately in the system.The system prints automatically a HU content list. The packer attaches the HU content list to the HU and moves it physically to the outbound section of the packing station. EWM automatically creates a HU warehouse task for the putaway to the final storage type. He proceeds the same way with all pallets from the source bin. 

Once all products have been repacked, he or she closes all remaining HUs in the system, attaches the HU content list to the corresponding HU and moves the HUs physically to the outbound section of the packing station. EWM automatically creates the HU warehouse tasks for the putaway to the final storage type.

At regular time intervals empty pallets used for storage are brought to the packing station and the empty pallets from the vendors are removed. These steps are not realized in the system.

If the system cannot propose packaging information for a product due to missing packaging specification, the packer informs a warehouse clerk, who will identify the product and create the packaging specification. In the meantime the packer can re-pack the other products. Once all other products have been repacked, only the product with missing packaging specification remains on the source HU. The packer puts the pallet aside. In the system the HU Is moved from the inbound section to the main section, so that the inbound section is free for the next delivery. Once the warehouse has created the packaging specification, the packer can re-pack the product and trigger the final putaway.

Step 9) Putaway the goods (SAP EWM)

In this step the warehouse worker moves the putaway HUs to the final bins. This step is executed using a mobile device .

A warehouse worker (for example, a forklift driver) takes the equipment necessary (for example, vehicle, mobile device) and logs on as a resource. The warehouse worker picks one HU from the outbound section of the packing station and scans its ID. The system finds the open HU-WT. The worker is prompted to bring the HU to the final destination bin in the pallet storage. There he drops the HU and scans the bin, thus confirming the WT. He drives back to the packing station to proceed with the next HU.

If the warehouse worker finds an empty pallet on the destination bin, he removes it from the bin and brings it to the area reserved for empty pallets. This step is not realized in the system.


Question 1) I need to control the batch creation by my centralized ERP system. What options do I have?

Answer: There are several possibilities. The batch can either be created directly in the EWM system or the data can be entered in the delivery and the batch can then be created in EWM.

Use transaction MSC1N or a batch management BAPI to create the batch.

Create the batch when creating the delivery in transaction VL31N or VL60. In this case, the delivery is usually replicated and created in EWM before the batch has been replicated. For restrictions see answer TODO -> reference to respective question

Enter all data that are relevant for the batch creation in ERP and save the document without creating the batch. In EWM set up the system to create the batch in background for the inbound delivery request (TODO: IMG path)

Note: This option will only work if all data that are required to maintain the batch are available in the delivery data model. In the SAP standard, the batch number, production date, BBD/ SLED, country of origin and the vendor batch are available.

Question 2) I have created the batch and an inbound delivery in the ERP system. The batch has been distributed to EWM. My inbound delivery is in status inconsistent (red). The handling units that I have expected have not been created. When I press the button 'Validate' in transaction /SCWM/PRDI, the inbound delivery is getting consistent (green) and I am able to create HUs. What is wrong here?

Answer: The delivery was probably processed in EWM before the batch replication was done. In this case, the inbound delivery is created in status inconsistent. The system is not able to create handling units from either the ERP HUs or the packaging specification as long as the batch has not been created in EWM.

Question 3) What can I do to get the HUs created when the delivery was created before the batch was available in EWM?

Answer: Delete the inbound delivery. The system will create a new inbound delivery from the inbound delivery request.

Question 4) I want to get the batch number from the ERP number range but I do not know the attributes before I am actually checking the incoming products. How can I do this in EWM?

Answer: Enter the batch number and all attributes that are already known when creating the delivery in ERP. The user who is working in EWM can then enter the remaining attributes in the corresponding fields of the delivery and create the batch by pressing the button 'Create Batch' in transaction /SCWM/PRDI or /SCWM/GR.

Example:When the delivery is created in the ERP system from the information provided by the vendor, the user knows the country of origin. This field is then entered in ERP. The delivery is sent to EWM. In EWM, the user enters the best-before-date and creates the batch.

If you like this blog, please share (Facebook/LinkedIn/Google+) to click below links so it will reach to others.


COMMENTS

LEAVE A COMMENT