Recording Device Inspection Data in Quality Management 
The SAP Quality Management (QM) component is used to record and manage device inspection data in IS-U. This section describes the necessary system settings.
Required Presettings
Table T156M
Before you can post a material transfer in the inspection stock, you must enter MA07 2 1 and MA07 2 2 in table T156M. If these entries are missing, maintain them as described in note 119613.
Table TQ30
Enter inspection type 08ISU_01. Double click on the inspection type and maintain the following values:
Physical-sample type
08
Notification type
F3
One notification per inspection lot
X
Task list usage
9
Control key
QM01
Transaction
9000
Table TQ34
Double-click on the inspection type to maintain the values for 08ISU_01. These values are then given when you allocate the inspection type to the material (see Create Material).
Table TQ32
Enter inspection type 08ISU_01 for inspection lot origin 08.
Table TE131
If inspection type 08ISU_01 is defined for a material, this table must contain the movement types for which PM inspection lots have to be generated for certification during stock transfer (standard U11).
Create material
If QM inspection lots can be generated for certification of equipment, you must specify the following in the material:
In the basic data 1, Unit must be specified as the base unit of measurement.
Under Quality Management you have to create inspection type 08ISU_01 for the inspection data and set the following detailed information fields:
Post to inspection stock
X
Inspection with task list
X
Automatic allocation of default values
X
Inspect characteristics
X
100% - inspection
X
Skips permitted
X
Automatic usage decision
X
Single units possible
X
When you enter check type 08ISU_01, ensure to set the Preferred indicator.
Serial number profile
In the serial number profile for IS-U equipment, you must enter serial number usage 02 (optional) for serialization procedure QMSL.
Inspection Plan
Description of the quality inspection process for the materials in a plant.
An inspection plan can consist of several operations. An operation determines which activity to execute at a work center. Operations can consist of several inspection characteristics. An inspection characteristic describes what needs to be inspected.
In addition, the required production resources and tools can be determined for each operation.
Inspection Plan Header
In order to prevent getting multiple results per characteristic and device, ensure that the value 3 (unique external numbering) is entered in the External Numbering field in the inspection plan header. If you do not do this, it is possible that multiple results are generated by the import of data from an external system.
The Usage field must contain the value 9 (the same as in inspection type 08ISU_01).
Procedure
When processing inspection data, if you want to go directly to the units to be inspected view once you have selected the corresponding operation, you must enter the value 11 (confirmation of results for units to be inspected) in the Recording View field.
If you want to be able to export lot data to a subsystem, you must specify a work center for every operation. The work center must in turn be allocated to a subsystem. You maintain subsystems in transaction QSUB.
Communication with External Systems
RFC function modules are available in QM for communication with external systems. The names of all the function modules begin with QIRF_, which makes them easy to find within the development environment.
QIRF_SEND... These function modules allow you to download data from an ERP system to a subsystem.
QIRF_GET... These function modules allow you to upload data from a subsystem to an ERP system.
For further details on the function modules, see the documentation for QM.
QIRF_SEND_REQUIRMENTS_GET_DATA
You use this function module to download operation and characteristics data to the subsystem. Ensure that the Record Type field in the I_QUAILS input structure is empty and that the SUBSYS (Subsystem) field is filled.
QIRF_GET_ORIGINAL_VALUES
You use this function module to upload inspection data recorded in the subsystem to an ERP system.
For quantitative characteristics, use record type Q51. For qualitative characteristics, use record type Q52.
In order to be able to allocate the inspection data to the corresponding device, you must set the KZSERNR indicator in table T_QAISETAB and you must enter the serial number in the SERIALNR field.
Process Flow
The cycle of the devices is generally the same:
Delivery of the devices
It is irrelevant whether or not the devices are serialized on delivery.
Install devices
The devices are serialized at this point at the latest.
Replace devices periodically.
At this stage, some of the removed devices must undergo certification. For this purpose, you must allocate the devices to be inspected to a QM lot according to their category. Include as many devices in a QM lot as you want to process in one operation.
The individual inspections are specified in the inspection plan, which is automatically allocated to the QM lot when it is created.
A QM lot can be generated in a number of ways:
Generate QM lot manually
Transaction QM01.
Enter material, plant, and inspection lot origin.
On the next screen, enter the number of devices that you want to inspect using the QM lot (inspection lot amount).
The serial numbers of the devices are only allocated to the QM lot when you record the inspection results (transaction QE01).
Manual transfer of devices to inspection stock.
Generate QM Lot by Stock Transfer
Transaction MB1B.
Enter movement type U11, plant and, if necessary, storage location.
In the next screen, enter target stock location, material, the number of devices you want to inspect using the QM lot and, if necessary, a source stock location.
Confirm the next screen without making any changes and on the following screen enter the serial numbers of the devices for inspection (use F6 for selection help).
If you end the posting by saving, a QM lot with the specified devices is generated in the background and transferred to the inspection stock of the target stock location.
Once the QM lots are generated and the serial numbers are assigned, you can enter the inspection data (transaction QE01).
Recording Inspection Data in External Systems
In this case, the subsystem must first download the inspection characteristics of the ERP system by means of the QIRF_SEND_REQUIRMENTS_GET_DATA function module. Once all of the information exists in the subsystem, the inspection data can be fully recorded there.
Since the serial numbers can not yet be downloaded at this point, you must enter them manually when recording the inspection data.
In order to ensure that the inspection data is allocated to the correct device when it is uploaded to the ERP system, you must specify the serial number in every data string.
Inspection Lot Completion
Once the inspection data has been recorded, you must close the characteristics before you can complete the inspection lot. Inspection lot completion (transaction QA11) includes making a decision about the usage of the inspected material and transferring the devices from the inspection stock.
You can use UD code A from selected set 03 for the usage decision.
If you want the usage decision to trigger a follow-up action it makes sense to define your own usage decision. Proceed as follows:
Table TQ07:
Define a follow-up action
Define the function module to be executed for the follow-up action
Transaction QS00:
Define a code group
Define the codes that can be used in the code group
Define a selected set with status 2 (released)
Define the codes of the selected set referring to a follow-up action (TQ07)
In order to disburden the inspection stock, you must transfer the devices to one or more storage locations within the transaction.