Tell us what you think

We want to create the best possible experience for our learners. Your feedback helps us to improve the experience for everyone.

Configuring Quality Notification Overview

Objectives

After completing this lesson, you will be able to:

Use transaction rules to reflect the Quality Notification needs of your business.
Explain how to ensure consistent data on Ariba Network and in SAP ERP and SAP S/4HANA.

Quality Notification Collaboration Configuration Overview

In Quality Notification Collaboration, most of the configuration required is carried out in SAP ERP and SAP S/4HANA. However, some configuration is also required on SAP Business Network.

Configuration Tasks

The configuration tasks listed in the following table are required to align data in SAP ERP and SAP S/4HANA and SAP Business Network, to enable the systems to communicate successfully.

SAP Business Network	SAP Integration Suite, managed gateway for spend management and SAP Business Network	SAP ERP and SAP S/4HANA
Configure system to comply with quality notification transaction rules Import source data for quality notifications	Not Applicable	Export source data for quality notifications Maintain parameters for quality notification Set up quality notification codes Maintain the event linkages for quality notifications Create the priority type for Ariba Network Perform Configurations for buyer-initiated quality notifications Perform Configurations for supplier-initiated quality notifications Define mandatory fields for quality notifications Resend a quality notification

Quality Notification Transaction Rules

Quality Notification Collaboration Transaction Rules

There are four transaction rules directly related to quality notification.

Transaction Rule 1: Require Suppliers to close a quality notification for an item before they can create a ship notice for the complaint quantity

If this rule is selected, suppliers must resolve a reported defect for an item and close the quality notification before they can create an advance ship notice to replace the complaint quantity for that item.

Transaction Rule 2: Allow Suppliers to create non-PO quality notifications in a multi-ERP environment

If this rule is selected, suppliers can create non-PO quality notifications and, when there are multiple routing end points, select to which system they apply. If this rule is not selected, quality notifications are always sent to the default routing end point.

Transaction Rule 3: Allow Suppliers to send quality notifications for indirect orders without part numbers

If this rule is selected, suppliers can send quality notifications for line items without specifying a customer part number or customer location. This rule makes those two quality notification fields optional.

Transaction Rule 4: Do not allow Suppliers to send non-PO quality notifications

If this rule is selected, suppliers can only create quality notifications that reference an order. If this rule is not selected, suppliers can create non-PO quality notifications on the Quality tab.

Consistent Data on SAP Business Network and in SAP ERP and SAP S/4HANA

For the systems to communicate successfully, there has to be consistency between the quality notification codes used on SAP Business Network and those used in SAP ERP and SAP S/4HANA.

To ensure this consistency, you must export the codes from SAP ERP and SAP S/4HANA and import them into the Buyer account on SAP Business Network. This data can be imported into SAP Business Network without any editing.

Next lesson