Sending a Quality Certificate via EDI with Access to Data (QM-CA)
Use
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.
Prerequisites
Application
The following requirements must be met when sending quality data on a certificate:
characteristic mapping table, if the characteristic descriptions differ in the vendor and customer system
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.
Output Control
The following condition components must be defined:
Condition component |
Value |
Output type |
LQCA , LQCB |
Application |
V2 |
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).
IDoc Interface
You must maintain the following values for both the outbound partner profiles and the additional partner profiles for outbound processing using the output control:
Field |
Value |
Message type |
QCERT |
Partner type |
KU (customer) |
Partner function |
WE , AG , Q1 or Q2 |
Recipient port |
e.g. SUBSYSTEM |
Output mode |
e.g. Transmit IDocs immediately |
Basic type |
QALITY02 |
Application |
V2 |
Output type |
LQCA/LQCB |
Process code |
QCERT_OUT |
Features
Communication in R/3 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:
