Processing ASNs in Service Parts Management In the service parts management business scenario, the customer uses SAP ERP with activated service parts management as the backend system. This customer backend system is the leading system for ASNs. It validates and distributes the ASNs to SAP Supply Network Collaboration (SAP SNC) and to
SAP Extended Warehouse Management
(
SAP EWM
). If the supplier creates or corrects an ASN manually in SAP SNC, the customer backend system must – together with SAP EWM – first
validate
and approve the ASN. A supplier working with EDI does not send a new or modified ASN directly to SAP SNC but to the customer backend system, which validates the ASN and forwards it to SAP SNC.
SAP EWM carries out the goods receipts in the service parts management business scenario. An ASN with goods receipt (GR) information goes first from SAP EWM to the customer backend system, which then forwards the ASN to SAP SNC. In service parts management, SAP SNC thus only communicates with the customer backend system (and possibly the supplier backend system) in ASN processing.
You use the following messages for ASNs:
XML message
DespatchedDeliveryNotification
and IDoc DESADV.DELVRY05
You use these messages to transfer an ASN that the supplier has created, changed, or canceled manually in SAP SNC from SAP SNC to the customer backend system.
IDoc DELINF.DELVRY05 and XML message
DeliveryInformation
You use these messages to transfer an ASN with validation results, GR data, or other changes from the customer backend system to SAP SNC. The transferred ASN version completely replaces any predecessor version that may already exist in SAP SNC. You can display obsolete ASN versions in the ASN history.
For more information, see External Validation .
In the standard system, the supplier can change ASNs that have the
Published
status and that were accepted by external validation. In Customizing for the
ASN
under
Define and Assign Display Profiles
, you can define whether a supplier can display ASNs with the
Published
status in the Web UI of SAP SNC, but cannot change them. You use this setting in a service parts management scenario if a supplier sends ASNs via EDI from his or her backend system, but is not to create or change them manually in SAP SNC.
If you, as supplier, want to revoke a draft ASN or a published changeable ASN in SAP SNC, you must cancel it.
The consequences of canceling the ASN are as follows:
The canceled ASN acquires the
Canceled
status.
The ASN still exists in SAP SNC. However, SAP SNC no longer takes account of the ASN in planning or for other functions.
You cannot change a canceled ASN.
If you cancel an ASN manually in SAP SNC, SAP SNC sends a cancellation ASN to the customer backend system. To do so, SAP SNC uses an XML message of the type
DespatchedDeliveryNotification
.