Show TOC

  External Validation

Purpose

This process is only relevant for the Service Parts Management scenario. If you, as supplier, publish a new or changed ASN in SAP Supply Network Collaboration (SAP SNC), SAP SNC firstly validates the ASN internally in SAP SNC . SAP SNC then sends the successfully validated ASN for a further external validation to the customer back-end system (ERP with activated Service Parts Management). The customer back-end system performs the validation along with the leading system for goods receipt processing, SAP Extended Warehouse Management (SAP EWM). Depending on the validation results, the customer back-end system either accepts or rejects the ASN. After the validation, the customer back-end system sends the ASN with the acceptance status and the validation log back to SAP SNC. SAP SNC generates alerts for the exceptions contained in the validation log. To publish an incorrect ASN, you must postprocess the ASN in SAP SNC.

Note Note

External validation is not relevant to returns ASNs .

End of the note.

Prerequisites

Settings in SAP SNC

  • You have configured external validation in Supply Network Collaboration Customizing under Start of the navigation path Delivery Next navigation step ASN Next navigation step Define Validation Scenarios End of the navigation path .In doing so you also activate the fields on the ASN processing Web UI that are relevant for the external validation, such as the acceptance status (see below).

  • You have defined how SAP SNC maps the results of the external validation to alerts. You do this in Supply Network Collaboration Customizing under Start of the navigation path Basic Settings Next navigation step Processing Inbound and Outbound Messages Next navigation step Display of External Exceptions and Logs Next navigation step Map External Logs to Alerts End of the navigation path .

  • You have made the following settings in Supply Network Collaboration Customizing under Start of the navigation path Tools Next navigation step Actions (Post Processing Framework) Next navigation step Define Action Profiles and Definitions End of the navigation path .

    • You have activated the action /SCA/BOL_DLV_XML for the application /SCA/ICH in the action profile /SCA/BOL_DELIVERY.

    • You have set Processing When Saving Document as the time of processing.

Settings in the Customer Back-End System

You have made the settings for the validation in the customer back-end system.For more information, see the component SAP ERP Central Component under Start of the navigation path General Logistics (LO) Next navigation step Service Parts Management (LO-SPM) Next navigation step Extended Inbound Processing End of the navigation path .

Process

  1. You publish the ASN in SAP SNC. SAP SNC first validates the ASN internally within SAP SNC. If this internal validation detects errors, you cannot publish the ASN in the standard system, in other words, you cannot send it to the customer. You must first remove the errors.

  2. After the internal validation has been performed successfully within SAP SNC, the ASN acquires the status Published and SAP SNC sends the ASN to the customer back-end system. Until the customer back-end system responds, the ASN has the acceptance status Pending in SAP SNC and you cannot process the ASN.

    The transfer to the customer back-end system is as follows: SAP SNC sends the ASN as a DespatchedDeliveryNotification to SAP NetWeaver. SAP NetWeaver maps the DespatchedDeliveryNotification to the IDoc DESADV.DELVRY04 and sends the IDoc to the customer back-end system.

  3. The customer back-end system creates a temporary inbound delivery and performs the validation. The customer back-end system can accept or reject the ASN. The ASN acquires the acceptance status Accepted or Rejected accordingly. The customer back-end system can reject an ASN for technical or business reasons. These include the following reasons:

    • In SAP SNC, you have created an ASN with a number that already exists in the customer back-end system.

    • In SAP SNC, you have changed the quantity of an ASN item, even though a goods receipt exists.

      Even if the customer back-end system has accepted an ASN, the ASN might still contain errors according to validation. The customer back-end system stores the exceptions in a validation log.

  4. The customer back-end system sends the ASN together with the acceptance status and the validation log to SAP SNC.

    The transfer to SAP SNC works as follows: The customer back-end system sends the IDoc DELINF.DELVRY05 to SAP NetWeaver. SAP NetWeaver maps the IDoc to an XML message of the type DeliveryInformation and sends this XML message to SAP SNC .

  5. SAP SNC performs the following actions:

    1. SAP SNC replaces the pending ASN with an ASN that customer back-end system has sent back and deletes the pending ASN. The acceptance status shows whether the customer back-end system has rejected or accepted the ASN.

    2. SAP SNC updates the ASN history.

    3. SAP SNC generates alerts for the exceptions contained in the validation log and sets the validation status of the affected incorrect subobjects (ASN header or ASN items) to Invalid .

  6. You check the validation status, the alerts, and the message history for the ASN.

  7. To remove the errors (that is, the cause of the alerts and possibly the rejection) in the ASN, you correct the ASN and publish it again.

    Note Note

    Note that you cannot change an ASN with the acceptance status Rejected . If you have created the ASN new, you must create a new ASN. If you have changed a published and accepted ASN, you must make the changes in the last accepted ASN version. You call the last accepted version by entering the ASN number and the status Accepted .

    End of the note.

  8. SAP SNC sends the changed ASN back to the customer back-end system for the external validation. Until the customer back-end system responds, the ASN has the status Pending again in SAP SNC and you cannot process the ASN in SAP SNC.

    The transfer to SAP SNC works as follows: SAP SNC sends an XML message of the type DespatchedDeliveryNotification to SAP NetWeaver. SAP NetWeaver maps the XML message to the IDoc DESADV.DELVRY04 and sends the IDoc to the customer back-end system.

  9. The customer back-end system validates the ASN and changes the inbound delivery accordingly.

  10. The customer back-end system sends the validated ASN and the validation results to SAP SNC.

    The transfer to SAP SNC works as in step 3: The customer back-end system sends the IDoc DELINF.DELVRY05 to SAP NetWeaver. SAP NetWeaver maps the IDoc to an XML message of the type DeliveryInformation and sends this XML message to SAP SNC .

  11. SAP SNC replaces the pending ASN with the transferred ASN and updates the ASN history.

Results

If the customer back-end system has not found more errors during the validation, the process is finished. You have successfully published a new or modified ASN.