Show TOC

Example documentationExample: Message Flow for Invoice Processing with Confirmation

 

This example shows the message flow if a customer uses a back-end system for invoice processing. This back-end system sends a confirmation of the invoice created by the supplier to SAP Supply Network Collaboration (SAP SNC).

Caution Caution

Integration with an SAP ERP back-end system does not support invoice processing with confirmations.

End of the caution.

Note Note

Although SAP SNC supports the confirmation function, the ability to use it depends on the customer back-end system being able to create and send such a confirmation.

End of the note.

The process runs as follows:

  1. Create invoice (SAP SNC)

    The supplier can create an invoice manually on the SAP SNC Web UI. If the supplier wants to be able to make changes to the invoice at a later time, he or she can save it with the status Draft. If the invoice has the status Draft, it is not yet sent to the customer back-end ERP system.

  2. Change invoice manually (SAP SNC)

    As long as the invoice has the status Draft, the supplier can still make changes to the invoice manually on the SAP SNC Web UI.

  3. Publish invoice (SAP SNC)

    When the supplier publishes the invoice, SAP SNC assigns the status Publishedto it and sends it to the customer back-end system via SAP NetWeaver system, using an XML message of type InvoiceRequest.

  4. Receive invoice (customer back-end system)

  5. Logistics invoice verification (customer back-end system)

  6. Publish confirmation (customer back-end system)

    The customer back-end system sends a message to SAP SNC using an XML message of type InvoiceConfirmation.

    If you want to use this function, you must ensure that your back-end system is able to send a confirmation that contains a status reflecting the customer’s decision to accept or reject the invoice.

  7. Update invoice status for Purchase Order or Advanced Shipping Notification (SAP SNC)

    SAP SNC updates the acceptance status of the invoice for the ASN or PO. The supplier can view this status on the SAP SNC Web UI.

  8. Process invoice (customer back-end system)

  9. Execute payment run (customer back-end system)

    The customer creates a payment run in the back-end SAP ERP system. The customer back-end system sends a payment advice notification to SAP SNC via SAP NetWeaver, using an XML message of type PaymentAdviceNotification.

  10. Update payment status for invoice (SAP SNC)

    Based on the XML message that was received from SAP NetWeaver, SAP SNC updates the payment status of the invoice. The supplier can then view the updated status on the SAP SNC Web UI.

    Note Note

    It is also possible for a supplier to create an invoice in his or her own back-end ERP and send this to SAP SNC using an XML message of type InvoiceRequest. This is not a standard process, but is possible on a project basis

    The SAP NetWeaver system of the customer receives an XML message of type InvoiceRequest from the supplier system. SAP NetWeaver sends an XML message of type InvoiceRequest to SAP SNC, where the invoice is checked against validation checks. If the invoice passes the validation checks, it is automatically published and sent on from SAP SNC to the customer back-end system via SAP NetWeaver. If the invoice does not pass the validation checks, SAP SNC gives it the status Received. In this case, the supplier must manually change and publish the invoice in SAP SNC for it to be sent on to the customer back-end system.

    We recommend that in the case of receiving invoices by means of an XML message from a supplier system, you use the above method. However, it is also possible for SAP NetWeaver to send a message to the customer back-end system directly at the same time as sending the XML message to SAP SNC. In this case, SAP SNC validates the invoice and changes the invoice status to Published, but it does not actually publish the invoice - that is, it does not send it to the customer back-end system.

    Note that XML messages and mappings depend on the ERP systems and releases being used. If you are using a non-SAP back-end system, you must create mappings as part of a project solution.

    End of the note.