Skip to Content

Overview:

In SNC SMI, supplier sends advanced shipping notification (ASN) from SNC (WebUI or Supplier System) to customer SAP system once the products are ready to ship. These ASNs are considered as transit quantities. Customer SAP system send goods receipt confirmation back to SNC, when the actual goods receipt is getting posted. This is the mandatory confirmation and in absence of this confirmation, the projected stock calculation in the replenishment planning would end inconsistency.


As long as ASN quantity is equal to Goods receipt quantity the output for Proof of delivery (OPOD) would be triggered automatically from Inbound delivery/Shipping notification.


In this document explains, how to manually intervene the confirmation process in case there is a mismatch in ASN and Goods receipt quantities due to shortfall or item lost during transit.


What is SMI?


Pls refer to the following document for the basic understanding of SMI process.


SNC Supplier Managed Inventory Integration – Key Settings in ECC

Process:

1.) ASN creation in SNC based on replenishment order

2.) Verify Inbound delivery in ECC

3.) Goods receipt in ECC against Inbound delivery (receipt quantity less than ASN quantity)

4.) Modify Inbound delivery quantity inline with actual Goods receipt quantity

5.) Check Proof of Delivery output

6.) Check ASN updated with correct Goods receipt quantity in SNC


1.) ASN creation in SNC based on replenishment order:

ASN Quantity = 100 EA

Capture1.PNG

2.) Verify Inbound delivery in ECC:

Inbound delivery is created with quantity 100 EA

Capture2.PNG












3.) Goods receipt in ECC against Inbound delivery (receipt quantity less than ASN quantity):

Goods receipt is completed and the quantity is less than the ASN quantity, say 95 EA.

Capture4.PNG

Proof of delivery output is not triggered from Inbound delivery,

Capture5.PNG

Goods movement status in Inbound delivery is shows partially completed.

Capture7.PNG

Hence, the ASN is not updated with the Goods receipt status and still shows as “Published”. If the status of ASN remain as Published, even though the goods receipt is completed in customer ECC, it will impact the projected stock calculation during replenishment planning.

Capture6.PNG

4.) Modify Inbound delivery quantity inline with actual Goods receipt quantity:

To update the ASN status with Goods receipt complete, it is required to manually amend the quantity in Inbound delivery equivalent to Goods receipt quantity. It is not advisable to add POD output manually in Inbound delivery.

By using VL32N, the quantity is modified equivalent to Goods receipt.

Capture8.PNG

Automatically the POD difference is recorded in Inbound delivery for the difference quantity.

Capture9.PNG

Once the quantity is adjusted the overall goods movement status is set to completed.

Capture10.PNG

5.) Check Proof of Delivery output:

The Goods movement status is changed to completed, hence the output is triggered from Inbound delivery for proof of delivery.

Capture11.PNG

6.) Check ASN updated with correct Goods receipt quantity in SNC:

Capture12.PNG

Further, drill down to the details, it is displayed GR quantity as 95 EA and ASN quantity as 100 EA

Capture13.PNG

Conclusion:

The goods receipt quantity discrepancy occurs occasionally, still require the above intervention for proof of delivery update so that the planning would happen smoothly.

Rifaie.jpg

Mohamed Hasan Rifaie M,  a Lead SAP consultant, an employee of Larsen & Toubro Infotech Ltd. He has overall 15 years of experience, out of which around 9 years in SAP Consulting (P2P, SRM, SCM & WM). He has business experience in various industries like Manufacturing, Electro mechanical Construction and Process industries as a Procurement Executive.








To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply