Skip to Content

<<Please select “View as PDF document” option to view the screenshot clearly>>

SAP SNC – Delivery Collaboration Process

Author: Aravind B, Infosys Ltd., Chennai

Introduction

SAP SNC is a common platform for customers and suppliers. Here, we can use Business process collaboration functionalities. The Purchase Order  collaboration is one of the collaboration functionalities of SAP SNC. It is used for collaborative processing of procurement process. In this collaboration, customer and supplier can complete their business processes by using SNC WEB UI. In this process, customer uses SAP ERP & SAP SNC systems and Supplier uses SAP SNC web UI & their B2B (either SAP or Non SAP) systems. SNC Delivery Collaboration process provides functions that are necessary for processing advanced shipping notifications (ASN) and for further follow on processes. The supplier communicates to the customer through ASN’s. It is used to inform the customer regarding the delivery and has details on the products, quantity and expected time of delivery.

Required setting needs to be maintained in

Supply Network Collaboration-> Delivery ->ASN

Other required settings

  • Supply Network Collaboration-Basic Settings-Processing Inbound and Outbound Messages -Maintain Settings for Master Data Completion
  • Supply Network Collaboration-Basic Settings-Processing Inbound and Outbound Messages SAP ICH 5.0 Compatibility
    Mode
  • Supply Network Collaboration-Basic Settings-Processing Inbound and Outbound Messages- Restrict Log
  • Supply Network Collaboration-Basic Settings-Processing Inbound and Outbound Messages -Restrict Alerts
  • Supply Network Collaboration-Basic Settings-Validation

SNC Delivery Collaboration process:

Kindly refer to SNC PO Collaboration before proceeding with this document for better understanding. You can find the document at http://scn.sap.com/docs/DOC-48157

Once the PO is received and confirmed by the Supplier in the SNC portal. The order acknowledgment will get generated as shown in the confirmations tab. This signifies that the order has been confirmed and acknowledged by the supplier.

PO Changes in ECC system.jpg

 

2. The confirmation is an order acknowledgement and can be seen under the confirmations tab of the ECC PO. The supplier can now proceed to
create the ASN in the SNC portal under ASN Creation menu as shown below.

ASN Creation.jpg

3.The supplier enters the ASN name, Delivery date, Shipping date, Customer location, Ship-from location (Supplier location), reference purchase order for which the ASN is created, ASN quantity.

4.Once the details are entered the supplier can choose the “Check” option in the menu to perform the validation of the ASN. The validations happen based on the validations profiles that are configured in the system. There are standard SAP validation profiles as well as customer specific validation profiles which can be used to valid the various parts of an ASN.

5.As per the system setting validations can be performed at the SNC system level or an external system can be used to do the same. As per our selection the validations happen in the SNC system and once an ASN is published no changes will be acceptable.

Path: SPRO->Supplier Network Collaboration->ASN->Validation Scenario for ASN’s

Validation Scenarios for ASNs.jpg

Validation scenarios can be maintained under the path:

SPRO->Supplier Network Collaboration->Validation

IMG path for validations.jpg

6.Once the validations are successful we will be able to see the green messages in SNC portal in the message log section. This indicates that the ASN is successfully validated and can be published. Only after publishing the ASN the changes will be saved.

7.Once we click the “Publish” option from the menu a warning message will be displaying graying out the background screen this indicates that the changes are final and cannot be revoked.

ASN Publish message.jpg

8.Once the warning message is accepted by clicking on Yes option the ASN will be published. The message “Delivery published successfully” will be displayed in the message log as shown in the screenshot below.

ASN Published.jpg

9.Once the ASN is published the XML message “DespatchedDeliveryNotification_Out” will be published from the SNC system and will be received as DESADV IDOC in the ECC system. This IDOC will be responsible for creation of Inbound delivery in case of no hindrances at the time of creation. This IDOC will update the PO as shown below.

XML messages.jpg

10.We can check the Purchase Order History tab of the PO in ECC system. This indicates that the DESADV IDOC has successfully created the inbound delivery.

PO Changes in ECC Post ASN.jpg

This inbound delivery will now be used in MIGO for creating the GR for this PO. Thus the delivery collaboration process in SNC is complete as indicated in the above steps.

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