Show TOC

 Connection of the Quality Inspection Engine to QM

Purpose

With SAP’s Quality Inspection Engine (QIE) , you can perform quality inspections using a combination of various SAP solutions in the mySAP Business Suite , as well as in non-sap applications. Other systems, which are known as consumer systemssupply the QIE with data. From the QIE, you can forward inspection requests to Quality Management (QM) in the ERP system so that you can use the additional functions available in QM.

This example process describes how you can use the QIE as the leading system to create and execute quality inspections, and then use results recording in the ERP system.

Prerequisites

If the following conditions are met, the system creates an inspection lot automatically:

  • Quality Management is active for the material. This means the following settings must be made in the material master:

    • An inspection type for the inspection lot origin 17 (externally triggered inspection) is active.

    • The indicators for the inspection type are set so that they meet the requirements of inspection lot processing.For more information, see Editing the Inspection Setup .

  • You have made the relevant settings in Customizing of Quality Management in the IMG activity Communication with Quality Inspection Engines .

  • You have defined the ERP system as an external system in the Customizing of the QIE.

  • In the inspection rule in the QIE you have defined that the inspection is to be executed in an external system and you have specified the inspection type as the attribute.

Process Flow

  1. The system creates an inspection documentin the QIE based on the data from the consumer system. This inspection document can be created with or without samples.

  2. In the QIE, you release the inspection document and thereby also automatically release the associated samples.

    The system sends a corresponding XI message to the ERP system.

  3. Based on the data from the QIE, the system creates an inspection lot with or without physical samples in the ERP system. The inspection lot is created for the origin 17 (externally triggered inspection) ; the samples are created with the inspection type 10 (sample from external inspection).

    Note Note

    When the system creates or changes an inspection lot with or without samples based on data from the external system, you can transfer additional data using the following Business Add-Ins (BAdIs):

    End of the note.

    • QPLEXT_LOT_CREATE: Creation of inspection lots for externally triggered inspection

    • QPLEXT_LOT_CREATE: Changing of inspection lots for externally triggered inspection

  4. The system assigns an inspection plan. If an inspection plan was specified in the QIE, the system will use this inspection plan. If not inspection plan was specified in the QIE, the system uses the functions of Quality Managemen t to determine an inspection plan. If the system cannot assign an inspection plan, you must do this manually.

  5. Samples are determined .

    The inspection lot is now available in the ERP system.

    If you want to change this inspection lot or the physical samples, if you want to cancel the inspection lot, or if you want to delete or create physical samples, you must do this in the QIE. The system then sends a corresponding XI message to the ERP system, where the changes are then also implemented.

  6. You perform results recording and the valuation in the ERP system.

  7. As soon as you have started recording results in the ERP system, the system sets a status to this effect in the corresponding inspection document in the QIE, so that it is no longer possible to perform a new sample calculation for this inspection document.

  8. You make the usage decision in the ERP system.

    The codes used in the QIE and in the ERP system must be identical, so that the usage decision can be replicated to the QIE. This means that the decision codes of the decision code group for the inspection document in the QIE must correspond to the codes in the selected set for the usage decision for the inspection lot in the ERP system. For an inspection with samples, the decision codes of the decision code group for the samples in the QIE must correspond to the codes in the selected set for valuation of the inspection point in the ERP system.

  9. The system transfers the information about the inspection decision to the inspection document and to the samples in the QIE. The system transfers the usage decision for the inspection lot, and for an inspection with samples it transfers a valuation of the physical samples. The system determines this valuation based on the inspection points and uses the valuation with the lowest quality score.

    Note Note

    You can use the BAdI QPLEXT_LOT_DECISION (copying of inspection decisions for externally triggered inspection) to define the other data that is to be transferred from the ERP system to the QIE.

    End of the note.