Updating ASNs with an SAP Back-End System

Use

When you, as customer, use an SAP back-end system, you have various possibilities to update advanced shipping notifications (ASNs) with goods receipt data in SAP Supply Network Collaboration ( SAP SNC), depending on the type of delivery processing in the back-end system.

This section is not relevant for the business scenarios for Service Parts Management (see Processing ASNs in Service Parts Management ).

Features

Goods Receipt in theSAPBack-End System for Inbound Delivery

In this scenario you transfer ASNs from SAP SNC to the SAP back-end system. There you create an inbound delivery for an ASN (transaction VL31N ) and create the goods receipt (GR) reference to the inbound delivery. To update ASNs in SAP SNC, you have the following options:

Transfer proof of delivery in a ReceivedDeliveryNotification message

Here you configure the SAP back-end system so that it automatically creates a proof of delivery upon goods receipt and sends it via SAP NetWeaver to SAP SNC with an XML message of type ReceivedDeliveryNotification . The ReceivedDeliveryNotification message is able to transfer detailed GR data at item level. Depending on the GR data, SAP SNC updates the status of the ASN item, the in-transit quantity, and the stock on hand. You can use XML messages of type ReceivedDeliveryNotification to process partial goods receipts in SAP SNC (see Confirming Partial Goods Receipts ).
Transfer GR data using the report RSMIPROACT or RSMIPROACT2 and a ReceivedDeliveryNotification message

Here you configure the SAP back-end system so that it does not generate a proof of delivery upon goods receipt. To transfer GR data to SAP SNC, you use the report RSMIPROACT or the report RSMIPROACT2 (see also Transfer of Demands and Stocks to SAP SNC (SMI, RP, DR) ). The system transfers the GR data to SAP SNC via SAP NetWeaver with an XML message of type ReceivedDeliveryNotification (see previous paragraph).
Transfer GR data using the report RSMIPROACT or RSMIPROACT2 and a ProductActivityNotification message

Here you do not generate proofs of delivery in the SAP back-end system. To transfer GR data to SAP SNC, you likewise use the report RSMIPROACT or the report RSMIPROACT2 . However, you do not transfer the data to SAP SNC with an XML message of type ReceivedDeliveryNotification , but with an XML message of type ProductActivityNotification. Since a ProductActivityNotification message does not transfer any quantities at item level, you can only map complete goods receipts in SAP SNC. SAP SNC therefore sets the Goods Receipt Complete status for an ASN item even if the supplier has only delivered a partial quantity.

Release Processing Without Inbound Delivery

In release processing, you procure your products using scheduling agreement releases, which you send toSAPSNC with XML messages of type DeliveryScheduleNotification. The supplier creates ASNs for scheduling agreement releases inSAPSNC that you transfer to yourSAPback-end system. We recommend that you also process goods receipts in theSAPback-end system on the basis of inbound deliveries in release processing (see above). Alternatively, you can also work without inbound deliveries; in other words, you do not send back any ReceivedDeliveryNotificationmessages toSAPSNC . If, in this scenario, you also want to updateASNitems inSAPSNC automatically, you have to specify thatSAPSNC updatesASNitems based on the cumulative received quantities that you transfer toSAPSNC using scheduling agreement releases. For more information, see Customizing for Start of the navigation path Supply Network Collaboration under Delivery Next navigation step ASN Goods Receipt Define Settings for Release Processing End of the navigation path .

Goods Receipt in theSAPBack-End System Without Reference to ASNs

In this scenario you do not transfer ASNs from SAP SNC to your SAP back-end system. You create goods receipts in the SAP back-end system without reference to an ASN (transaction MIGO ). The GR employee enters the delivery note number manually. The delivery note number is identical to the ASN number. In this scenario, you can only map complete goods receipts in SAP SNC.

To update ASNs in SAP SNC, you have the following options:

Transfer GR data in a ReceivedDeliveryNotification message

In an XML message of type ReceivedDeliveryNotification , you transfer the ASN number, the product number, and the goods receipt quantity for the product from the SAP back-end system to SAP SNC. Since it is easy to make mistakes when entering and transferring item numbers, you do not transfer any item numbers. ( SAP SNC is only able to correctly update ASN items if the item numbers in the ReceivedDeliveryNotification message match the item numbers in the ASN exactly.) For this variant, SAP SNC updates the status of all ASN items that contain the product. You should only use this variant if a product only occurs in one item of an ASN .
Transfer GR data using the report RSMIPROACT or RSMIPROACT2 and a ReceivedDeliveryNotification message

In this case, an ASN item is updated in SAP SNC as described in the last section. The only difference is that you use the report RSMIPROACT or the report RSMIPROACT2 to perform the transfer.
Transfer ASN numbers with the report RSMIPROACT or RSMIPROACT2 and a ProductActivityNotification message

In this case, you use the report RSMIPROACT or the report RSMIPROACT2 and an XML message of type ProductActivityNotification . In the ProductActivityNotification message, you only transfer the ASN number and the product numbers. You do not transfer any product quantities. SAP SNC updates the status of all ASN items that contain the product.