In this EDI scenario, you send inspection results that are issued on a certificate as formatted data to your customer. You can also send the certificate as a PDF file.
In general, a quality certificate is referenced to a delivery, inspection lot, or batch. Therefore, the transfer of the quality data on the certificate is not necessarily linked to a purchase order or delivery. Results of inspections that, from the recipient's point of view, were made externally, can also be sent to the recipient system for further processing. For more information, see Receiving a Quality Certificate via EDI with Access to Data (QM-CA).
The certificate as a PDF file automatically receives a digital signature to protect the data from being modified during transfer. This means that the data cannot be manipulated during transmission.
The following requirements must be met when sending quality data on a certificate:
· On the sender side (vendor)
¡ Certificate profiles and class characteristics or master inspection characteristics are used
¡ A clear assignment of the characteristics is ensured using the characteristic mapping table, if the characteristic descriptions differ in the vendor and customer system
¡ The address data of the customer is defined in the EDI partner profile
To ensure a correct assignment of the delivery to the purchase order on the customer site when transferring quality data on a certificate with reference to a delivery, the purchase order item or the customer material number must be entered on the delivery item detail screen in the sales order.
The following condition components must have been created:
Condition Component |
Value |
Output type |
LQCA, LQCB |
Application |
U2 |
Procedure |
V20001 |
Transmission medium |
6 (EDI) |
Access sequence |
0003, 0008 |
Partner function |
AG (sold-to party) and WE (ship-to party) |
For more information, see Quality certificates in Customizing for Quality Management (QM).
· Message Determination
· Message Processing
You must maintain the following values for both the outbound partner profiles and the additional partner profiles for outbound processing using output control:
Screen Field |
Value |
Message category |
QCERT |
Partner type |
KU (customer) |
Partner function |
WE, AG, Q1 or Q2 |
Receiving port |
e.g. SUBSYSTEM |
Output mode |
z.B. Transmit IDocs immmediately |
Basic type |
QALITY02 |
Application |
U2 |
Output type |
LQCA/LQCB |
Process code |
QCERT_OUT |
Communication in SAP is established using the IDoc interface. Outbound and inbound IDocs are saved on the database and later transferred to the storage system. Technical transmission can be determined for each partner. In general, communication is possible:
· Between two SAP Systems
· Between an external system on the vendor side and an SAP system on the customer side
· Between an SAP system on the vendor side and an external system on the customer side