Show TOC

Example documentationExample Message Flow: Quality Collaboration

 

This section provides you with an overview of the message flow between the systems when using quality notifications. In the processes depicted here, a supplier can create notifications on the Web UI of the customer SAP Supply Network Collaboration (SAP SNC) system. A customer can also create a quality notification in his or her back-end system.

Recommendation Recommendation

The examples only provides a basic overview. We do not recommend that you use them as a basis for configuration. Instead, use the integration scenarios and mappings that are part of the XI content for SAP SNC. This allows you to generate message flows and routings automatically.

End of the recommendation.
Supplier Creates Quality Notification

The following figure shows the message flow where the supplier creates a quality notification and is followed by an explanation:

In the above figure, QINSNM represents an XML message of the QualityIssueNotificationSUITENotificationMessage type.

The process flow runs as follows:

  1. Create quality notification on Web UI (SAP SNC)

    A supplier creates a quality notification using the Web UI of the customer SAP SNC system.

  2. Publish quality notification on Web UI (SAP SNC)

    The supplier publishes the quality notification on the SAP SNC Web UI. SAP SNC sends this newly created quality notification to the customer back-end system

  3. Create quality notification (SAP ERP)

    The customer back-end system creates a quality notification using the message received from SAP SNC

  4. Change quality notification (SAP ERP)

    A customer may want to edit the quality notification in his or her back-end system to respond to the supplier. If he or she does this, the customer back-end system sends the changed quality notification to SAP SNC.

  5. Update quality notification (SAP SNC)

    SAP SNC updates the changed quality notification based on the message received from the customer back-end system.

  6. Change quality notification on Web UI (SAP SNC)

    The supplier can edit the quality notification using the Web UI of the customer SAP SNC system (for example, to confirm that the issue has been resolved, for example). When the supplier saves the changes, SAP SNC sends the changed quality notification to the customer back-end system

  7. Update quality notification (SAP ERP)

    The customer back-end system updates the quality notification based on the message received from SAP SNC.

Customer Creates Quality Notification

The following figure shows the message flow where the customer creates a quality notification and is followed by an explanation:

In the above figure, QINSNM represents an XML message of the QualityIssueNotificationSUITENotificationMessage type.

  1. Create quality notification (SAP ERP)

    A customer creates a quality notification in his or her back-end system (to report an issue with a product from the supplier, for example). The customer back-end system sends the quality notification to SAP SNC.

  2. Create quality notification (SAP SNC)

    SAP SNC creates a quality notification based on the message received from the customer back-end system.

  3. Change quality notification (SAP SNC)

    The supplier responds to the notification that was sent from the customer. To do this, the supplier changes and publishes the quality notification on the SAP SNC Web UI. SAP SNC sends the changed quality notification to the customer back-end system.

  4. Update quality notification (SAP ERP)

    The customer back-end system updates the quality notification based on the message received from SAP SNC.

  5. Change notification (SAP ERP)

    The customer changes the quality notification in his or her back-end system (to confirm that the issue has been resolved, for example). The customer back-end system sends the changed quality notification to SAP SNC.

  6. Update quality notification (SAP SNC)

    SAP SNC updates the quality notification based on the message received from the customer back-end system.