System Interaction

Use

This process describes how a consumer system interacts with the Quality Inspection Engine (QIE).

Prerequisites

The consumer system provides the user interface.

Process

  1. You call up the application that you require in the consumer system.

  2. The consumer system checks if you have authorization to use this application.

  3. In the consumer system, you select the function you require within the application and enter data.

  4. The consumer system transfers the data to the QIE and calls up the associated service in the QIE.

  5. The QIE checks if you have authorization to use this service.

  6. Depending on the service, the QIE executes one or more of the following steps:

    • It reads or loads data.

    • It checks data.

    • It changes data.

    • It deletes data.

    • It saves data.

  7. The QIE makes the processed data available to the consumer system.

  8. The consumer system picks up, interprets, and processes the data and makes it available to you if required.



This process flow can be repeated as often as required during a process. See the following example.

Example

The following process flow is an example of how the systems interact when you display the findings for an inspection document:

  1. In the consumer system, you choose the transaction for the administration of findings.

  2. The consumer system checks if you have authorization to use this transaction.

  3. In the consumer system, you select the function for displaying findings and enter the inspection document for which you want the findings to be displayed.

  4. The consumer system transfers the number of the inspection document to the QIE and calls the service for displaying findings there.

  5. The QIE checks if you have authorization to use this service.

  6. Based on the transferred inspection document number, the QIE reads data for the inspection document and the associated findings.

  7. The QIE makes a list of findings available to the consumer system.

  8. The consumer system picks up the list of findings and displays it on the user interface.

If you then decide than a finding needs to be processed, the process flow will restart at step 3 when you select the function for changing findings.

The following process flow is an example of how the system creates an inspection document in the background when you create a goods receipt:

  1. In the consumer system, you choose the transaction for the creating goods receipts.

  2. The consumer system checks if you have authorization to create goods receipts.

  3. In the consumer system, you enter the data required for the goods receipt, for example, the material and the plant.

  4. The consumer system transfers the material and the plant to the QIE and calls the service for creating inspection documents there.

  5. The QIE checks if you have authorization to use the service for creating inspection documents.

  6. Based on the transferred material and plant data, the QIE evaluates the corresponding inspection rules, determines the inspection parameters, creates the inspection document based on these parameters, and if necessary created the associated samples. If necessary, the system can execute other follow-up actions. For example, it can print sample-drawing instructions.

  7. The QIE informs the consumer system that an inspection must take be carried out, that an inspection document has been created, and it tells it the number of this inspection document.

  8. The consumer system picks up the information that an inspection must be carried out. If you have made the corresponding settings, the consumer system will flag the goods receipt document accordingly.