Quantity Differences for Stock Transfer Orders
Purpose

In Extended Warehouse Management (EWM), you can confirm stock transfer orders with a quantity difference. This enables you to map the following processes:

● You receive a quantity shortage or quantity excess in the inbound delivery, which was caused by a delivering warehouse; for example, the delivering warehouse has not loaded a pallet onto the vehicle.
● You receive a quantity shortage or quantity excess in the inbound delivery, which was caused by a carrier; for example, a carrier damaged the goods.
● In cross-docking, you can confirm quantity excesses or shortages that were caused by the first cross -docking warehouse and not the delivering warehouse. If a source warehouse caused a quantity excess or shortage, the ERP system sends a correction delivery to EWM in the source warehouse. There, if required, you can execute clearing in the Difference Analyzer [Seite 677] between the receivable quantities and the difference quantities to be cleared. If you are unable to execute clearing, you post the difference to the ERP system. You deliver 10 pieces of product A. The customer only receives 9 pieces. You post a correction delivery for one piece as a receivable quantity to be cleared. In the physical inventory, you find that one piece of product A is still in the goods issue area. In the Difference Analyzer, you can offset the receivable quantity to be cleared with a difference quantity to be cleared. If a carrier caused a quantity excess or shortage, you perform an adjustment posting directly in the ERP system. The ERP system uses the process code from the last partial goods receipt message of the target warehouse to determine who caused the quantity excess or shortage. For more information, see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics – General (LO) → Service Parts Management (LO-SPM) → Transfer and Inventory Management → Stock Transfers → Adjustment of Stock Transport Order Quantity Difference.

If quantity differences occur in connection with kits, you always post these differences at the kit header. If the kit itself is not available in the source warehouse, rather the kit components only, you have to clear this difference by posting differences in the inventory quantity.

Prerequisites

● You are working in a system landscape that includes an ERP system, central SAP Advanced Planning & Optimization (SAP APO) for the automatic generation of stock transfer orders, and at least one decentralized EWM.

● You are using interfaces between EWM and the ERP system. For more information, see Communication from EWM to ERP System.

● You have defined tolerance groups for the Difference Analyzer in the Customizing settings for EWM. For more information, see the Implementation Guide (IMG) for EWM under Internal Warehouse Processes → Physical Inventory → Warehouse-Number-Specific Settings → Define Tolerance Groups → Define Tolerance Group for Difference Analyzer.

● You have assigned the user to a tolerance group for the Difference Analyzer in the Customizing settings for EWM. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Physical Inventory → Assign User to Tolerance Group for Difference Analyzer.

EWM in the Source Warehouse

● You have defined document types for the correction deliveries in Customizing for EWM. EWM finds these using the differentiation attribute DIS (discrepancy process) at header level. For more information, see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration → Delivery Processing → Define ERP Document Types for Differentiation Attribute. Make sure that the Customizing settings for EWM for your own document types and for the item types used are correct. If you are defining your own profiles, use the delivered document types and item types and their relevant profiles as a basis.

● You have defined the mapping of the document types from the ERP system in EWM in Customizing for EWM.
For more information, see the IMG for EWM under Interfaces → ERP Integration → Delivery Processing → Map Document Types from ERP System to EWM System. EWM in the Target Warehouse

● In Customizing for EWM, you have defined whether EWM is to execute an automatic or manual goods movement. For more information, see the IMG for EWM, under Cross-Process Settings → Delivery Processing → Actions → Use Assistant to Create Actions.

● In Customizing for EWM, you have defined process codes and assigned these to your own process code profiles. You have also assigned partner roles to the process codes.

● You have defined the mapping of the exception code to the process code of the delivery processing in Customizing for EWM.
For more information, refer to the IMG for EWM under Cross-Process Settings → Exception Handling → Define Exception Codes.

Process

Quantity Differences for Stock Transfer Orders

You work with a central SAP APO and ERP system and two decentralized warehouses managed by EWM. You transport goods from one warehouse to another. In the following, the two EWM systems are referred to as EWM1 for the source warehouse and EWM2 for the
target warehouse.

1. You create a stock transfer order in SAP APO and SAP APO informs the ERP system about it.

2. The ERP system generates a corresponding stock transfer order and an outbound delivery for this. It informs EWM1 of the source warehouse about this.

3. EWM1 generates a relevant outbound delivery.

4. You perform the required goods issue process steps and post the goods issue.

5. EWM1 informs the ERP system about this.Stock Transfer Orders

6. The ERP system generates a corresponding inbound delivery for EWM2 of the target  warehouse. It informs EWM2 about this.

7. EWM2 generates a corresponding inbound delivery.

8. You or a carrier transport the products to EWM2.

9. You execute the goods receipt process steps up to goods receipt posting. When posting goods receipt, you identify a quantity excess or shortage.

10. You post goods receipt with the quantity excess or shortage and specify a process code.
EWM2 uses the process code to differentiate who caused the quantity excess or shortage (see Delivery Quantity Adjustment.

11. EWM2 informs the ERP system about this.

12. The ERP system posts the quantity differences in the proof of delivery.

13. The ERP system generates a correction delivery for EWM1 of the source warehouse. For a quantity shortage, the ERP system generates an inbound delivery for EWM1, and for a quantity excess, an outbound delivery for EWM1. The ERP system informs EWM1
about this.

14. EWM1 generates an inbound or outbound delivery as a correction delivery, based on the notification. It posts the quantity excess or shortage as a receivable quantity to be cleared (external quantity difference). You can reject goods receipt of the inbound delivery or goods issue of the outbound delivery in EWM1. The unassigned stock remains in the ERP system. You have to then process it manually, if necessary. EWM1 posts internal quantity differences from the physical inventory or warehouse task creation as difference quantities to be cleared. For example, if you find a pallet in the physical inventory that has 10 pieces of a product, you post this as a difference
quantity to be cleared.

15. In EWM1, you attempt to offset the receivable quantities to be cleared with the difference quantities to be cleared in the Difference Analyzer.

Quantity Differences in Cross-Docking

Unlike the standard process for stock transfer orders, in the cross-docking process (CD process) you work with at least three decentralized warehouses: the source warehouse, the cross-docking warehouse (CD warehouse) and the target warehouse. These warehouses are managed by EWM. You transport goods from the source warehouse to the target warehouse via the CD warehouse. In the cross-docking process, you record quantity differences in the same way as for stock transfer orders. When you record quantity differences, you can use the process code to decide whether these quantity differences are to be debited from or added to the previous warehouse (if exists) or the source warehouse. The following graphic illustrates these two options. For example, if you want to record a quantity shortage in CD warehouse 2, you can use process code PC2A to debit this quantity difference from CD warehouse 1, or process code PC2B to debit the source warehouse.