Show TOC

Function documentationPublishing ASNs

 

If you want to send an advanced shipping notification (ASN), which you created or changed in SAP Supply Network Collaboration (SAP SNC), to the customer's back-end system, you must publish the ASN in SAP SNC.

Features

The consequences of publishing the ASN are as follows:

  • If you have only entered either a delivery date or only a shipping date, SAP SNC performs scheduling automatically.

  • SAP SNC performs an internal validation.

    If the data for a newly created ASN is complete and correct, the ASN acquires the Published status and SAP SNC sends the ASN to the customer. To do so, SAP SNC generates an XML message of the type DespatchedDeliveryNotification. This goes to the customer's back-end system via SAP NetWeaver.

    In the standard system, SAP SNC sends the XML message in the background directly. However, you can also change the configuration so that SAP SNC uses the Post Processing Framework (PPF) to send the XML message. For more information, see Publication of XML Messages.

  • If the data contains errors, the affected, incorrect ASN subobjects (ASN header or ASN item) acquire the Invalid validation status in the standard system, and the ASN acquires (or retains) the Draft status. To be able to publish the ASN, you must first correct the data. For publishing, all ASN subobjects must have the Valid validation status.

    Note Note

    In Customizing for Validation, the system administrator can specify which validation status a subobject acquires on publishing, depending on the validation result.

    End of the note.

  • SAP SNC automatically updates the In transit and Planned receipts key figures as follows:

    • In Transit key figure

      The In Transit key figure represents the number of published ASNs that the customer has not yet received. SAP SNC transfers the published ASN quantity to the In Transit key figure. In the SMI scenario, a covered planned receipt disappears from the due list for planned receipts (SMI).

    • Planned Receipts key figure

      This key figure is relevant to the SMI scenario. SAP SNC updates this key figure as follows:

      • If the formula for the projected stock contains the In Transit key figure but not the Firm Receipts key figure (published replenishment orders), SAP SNC reduces the Planned Receipts key figure by the published ASN quantity.

        Note Note

        Changing and republishing an already published ASN does not update the Planned Receipts key figure.

        End of the note.

      • If the formula for the projected stock contains both the In Transit key figure and the Firm Receipts key figure, the system reduces the planned receipts published replenishment order quantity rather than by the published ASN quantity.

  • In the standard system, the default setting is that the supplier cannot change a published ASN. For more information about changing the default setting, see Changing ASNs.

  • In the service parts management business scenario, an ASN with the status Published can be changed on the Web UI if this has been set in Customizing for the ASN. For further information, see Processing ASNs in Service Parts Management.

  • In the service parts management business scenario, the ASN goes to the customer back-end system for external validation that either accepts or rejects the ASN. For more information, see Processing ASNs in Service Parts Management and External Validation.

Activities

If you want to publish the ASN, choose Publish in the ASN overview or Publish ASN in the ASN details.