SAP WM module is integrated with other SAP modules. After the salesperson completes the creation of the sales document, the business personnel of the warehouse department need to pick for the delivery document. If WM management is enabled for the picking storage location, the warehouse personnel need to create a TO (Transfer Order) based on the delivery note to complete picking.
The usual practice is that after the TO document is created and confirmed, the warehouse business personnel manually execute the transaction code VL02N to do the goods issue posting (PGI). In fact, the SAP system can automatically update the delivery quantity of delivery note according to the confirmed TO quantity after the TO is confirmed, and even automatically complete the goods issue posting. These are reflected in the integration of SAP WM and shipping in SD, the so-called copy WM quantity.
Related configuration can be done by below path.
There are 4 options for the Copy WM quantity field:
Do not copy WM quantity as delivery quantity into delivery
1 Copy WM quantity as delivery quantity into delivery
2 Copy WM quantity as delivery quantity and post GR/GI
4 Do not take WM qty as delivery qty, but post GR/GI
The first option is empty, it is often used in SAP project practice. This blog will not demo the effect of first option. And this blog focus on the control function of the option 1,2 and 4.
Part I：Copy WM Quantity = 1 (Copy WM quantity as delivery quantity into delivery)
1, we maintain the value of the field “Copy WM quantity” into 1 for the warehouse number NM1 movement type 601.
2, we created below sales order and delivery document for the material 800.
Delivery,
3, Execute the transaction code LT03 to do picking for this outbound delivery.
Click enter, we got below screen,
We just picked 75 EA for this delivery, then save it,
TO#100 was created,
Confirm TO 100,
Execute transaction code VL03N to display this outbound delivery document, to see the update of the delivery quantity.
The delivery quantity was changed into 75 EA automatically, of course the picked quantity was 75 EA too.
We can find the change history of delivery note to see the detailed information, see below screenshot.
This is the control function when Copy WM quantity = 1.
However, in the projects I participated in, few projects set the value of copy WM quantity field in this configuration to 1. This function is a good function, which is more convenient and flexible, but it is not applicable in business practice. Because of the delivery of goods to customers, many enterprises do not allow partial delivery. Once the delivery is created, it must be delivered to customers according to the quantity of delivery.
Part II：Copy WM Quantity = 2 (Copy WM quantity as delivery quantity and post GR/GI)
1, we maintain the value of the field “Copy WM quantity” into 2 for the warehouse number NM1 movement type 601.
2, we created below sales order and delivery document for the material 800.
Delivery QTY = 100 EA.
3, Execute the transaction code LT03 to do picking for this outbound delivery.
Suppose we just picked 88 EA for this delivery. Click Save, then TO#101 was created, and then we confirmed this TO.
Execute the transaction code VL03N to display the document flow of this outbound delivery.
We can see that the goods issue has been posted.
To see the delivery quantity of delivery note,
The delivery quantity of this outbound delivery was changed into 88 EA, of course the picked quantity was 88 EA too.
This is the effect when Copy WM quantity = 2.
However, in the projects I participated in, almost no project set the value of copy WM quantity field as 2. This function is very good and automatic, but it is not applicable in business practice. After picking, the warehouse operators may often need to re-pick for various reasons. If the picking has been completed, the goods issue will be posted automatically. When handling picking errors, they also need to cancel the PGI in advance, which brings trouble to the business personnel.
Part III: Copy WM Quantity = 4 (Do not take WM qty as delivery qty, but post GR/GI)
1, we maintain the value of the field “Copy WM quantity” into 4 for the warehouse number NM1 movement type 601.
2, we created below sales order and delivery document for the material 800.
Delivery QTY = 50 EA.
3, Execute the transaction code LT03 to do picking for this outbound delivery.
We just picked 45 EA for this delivery. Save it, the TO#102 was created, we confirmed this TO document by transaction code LT12.
Check the document flow for this outbound delivery,
No PGI was done. Execute VL03N to display this delivery,
When the picked qty is smaller than the delivery qty, after TO confirmation, the delivery quantity will Not be updated, no PGI.
Continue to do picking,
The picked qty is 5 EA, save it and created the TO#103，confirm this TO.
Now to check the document flow of this delivery,
The PGI was done automatically. It means that when the value of Copy WM quantity =4, SAP will automatically done PGI only when the picked quantity equals to the delivery quantity.
This is the control function when Copy WM quantity =4.
However, in the projects I participated in, almost no project set the value of copy WM quantity field as 4. This function is very good and automatic, but it is not applicable in business practice.
Note: This blog is based on SAP S4/HANA 1909 system.
Okumaya devam et...
The usual practice is that after the TO document is created and confirmed, the warehouse business personnel manually execute the transaction code VL02N to do the goods issue posting (PGI). In fact, the SAP system can automatically update the delivery quantity of delivery note according to the confirmed TO quantity after the TO is confirmed, and even automatically complete the goods issue posting. These are reflected in the integration of SAP WM and shipping in SD, the so-called copy WM quantity.
Related configuration can be done by below path.
There are 4 options for the Copy WM quantity field:
Do not copy WM quantity as delivery quantity into delivery
1 Copy WM quantity as delivery quantity into delivery
2 Copy WM quantity as delivery quantity and post GR/GI
4 Do not take WM qty as delivery qty, but post GR/GI
The first option is empty, it is often used in SAP project practice. This blog will not demo the effect of first option. And this blog focus on the control function of the option 1,2 and 4.
Part I：Copy WM Quantity = 1 (Copy WM quantity as delivery quantity into delivery)
1, we maintain the value of the field “Copy WM quantity” into 1 for the warehouse number NM1 movement type 601.
2, we created below sales order and delivery document for the material 800.
Delivery,
3, Execute the transaction code LT03 to do picking for this outbound delivery.
Click enter, we got below screen,
We just picked 75 EA for this delivery, then save it,
TO#100 was created,
Confirm TO 100,
Execute transaction code VL03N to display this outbound delivery document, to see the update of the delivery quantity.
The delivery quantity was changed into 75 EA automatically, of course the picked quantity was 75 EA too.
We can find the change history of delivery note to see the detailed information, see below screenshot.
This is the control function when Copy WM quantity = 1.
However, in the projects I participated in, few projects set the value of copy WM quantity field in this configuration to 1. This function is a good function, which is more convenient and flexible, but it is not applicable in business practice. Because of the delivery of goods to customers, many enterprises do not allow partial delivery. Once the delivery is created, it must be delivered to customers according to the quantity of delivery.
Part II：Copy WM Quantity = 2 (Copy WM quantity as delivery quantity and post GR/GI)
1, we maintain the value of the field “Copy WM quantity” into 2 for the warehouse number NM1 movement type 601.
2, we created below sales order and delivery document for the material 800.
Delivery QTY = 100 EA.
3, Execute the transaction code LT03 to do picking for this outbound delivery.
Suppose we just picked 88 EA for this delivery. Click Save, then TO#101 was created, and then we confirmed this TO.
Execute the transaction code VL03N to display the document flow of this outbound delivery.
We can see that the goods issue has been posted.
To see the delivery quantity of delivery note,
The delivery quantity of this outbound delivery was changed into 88 EA, of course the picked quantity was 88 EA too.
This is the effect when Copy WM quantity = 2.
However, in the projects I participated in, almost no project set the value of copy WM quantity field as 2. This function is very good and automatic, but it is not applicable in business practice. After picking, the warehouse operators may often need to re-pick for various reasons. If the picking has been completed, the goods issue will be posted automatically. When handling picking errors, they also need to cancel the PGI in advance, which brings trouble to the business personnel.
Part III: Copy WM Quantity = 4 (Do not take WM qty as delivery qty, but post GR/GI)
1, we maintain the value of the field “Copy WM quantity” into 4 for the warehouse number NM1 movement type 601.
2, we created below sales order and delivery document for the material 800.
Delivery QTY = 50 EA.
3, Execute the transaction code LT03 to do picking for this outbound delivery.
We just picked 45 EA for this delivery. Save it, the TO#102 was created, we confirmed this TO document by transaction code LT12.
Check the document flow for this outbound delivery,
No PGI was done. Execute VL03N to display this delivery,
When the picked qty is smaller than the delivery qty, after TO confirmation, the delivery quantity will Not be updated, no PGI.
Continue to do picking,
The picked qty is 5 EA, save it and created the TO#103，confirm this TO.
Now to check the document flow of this delivery,
The PGI was done automatically. It means that when the value of Copy WM quantity =4, SAP will automatically done PGI only when the picked quantity equals to the delivery quantity.
This is the control function when Copy WM quantity =4.
However, in the projects I participated in, almost no project set the value of copy WM quantity field as 4. This function is very good and automatic, but it is not applicable in business practice.
Note: This blog is based on SAP S4/HANA 1909 system.
Okumaya devam et...