Show TOC

  Example: Message Flow for Invoice Processing

This example shows the message flow if a customer uses an SAP back-end system for invoice processing with SAP Supply Network Collaboration (SAP SNC).

* To use invoice collaboration with SAP R/3 4.7, SAP ERP 2004, and SAP ERP 2005, you must implement the following SAP Notes:

  • SAP Note 1040648.

  • SAP Note 1053121

    Note Note

    As of SAP ERP 2005 SP 10, you do not need to implement these SAP Notes.

    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 it manually on the SAP SNC Web UI.

  3. Publish invoice (SAP SNC)

    When the supplier publishes the invoice, SAP SNC assigns the status Published and sends the invoice to the SAP NetWeaver system of the customer using an XML message of type InvoiceRequest . SAP NetWeaver converts this XML message into an IDoc of type INVOIC.INVOIC01 and sends it to the customer back-end system.

  4. Receive invoice (customer back-end system)

    The customer back-end system receives the IDoc.

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

  6. Process invoice (customer back-end system)

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

    The customer creates a payment run in the back-end ERP system. The system generates an IDoc of type REMADV.PEXR2002 and sends this to SAP NetWeaver. SAP NetWeaver converts the IDoc into an XML message of type PaymentAdviceNotification and sends this to SAP SNC.

  8. Update payment status for invoice (SAP SNC)

    Based on the XML message received from the customer back-end system, 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 system and send this to SAP SNC. SAP SNC can receive such an invoice from 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 which checks the invoice against validation checks. If the invoice passes the validation checks, it is automatically published and sent on from SAP SNC to the customer SAP ERP 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 an IDoc of type INVOIC.INVOIC01 to SAP ERP 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 the invoice to the customer back-end system.

    Note that IDocs, XML messages and mappings depend on the ERP system and releases being used. We deliver standard mappings for use with an SAP backend system. If you are using a non-SAP back-end system, you must create mappings as part of a project solution.

    End of the note.