Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
QP (Package) QM inspection plan characteristics
Basic Data
| Data Element | QKZRASTER |
| Short Description | Inspection Point |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | QKZ | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | InspPoints |
| Medium | 15 | Insp. Points |
| Long | 20 | Inspection points |
| Heading | 4 | InsP |
Documentation
Use
With this indicator, you specify that all data in the task list pertaining to sampling procedures is based on inspection points.
Procedure
Set the indicator, if you want to use the task list to process the inspection on the basis of inspection points.
Dependencies
If you set this indicator, the following dependencies apply:
- The system also needs an inspection point identifier and a definition of the level of detail for managing the partial quantities.
- At the operation level, you can also define whether the inspections will be carried out on the basis of:
- time
- quantity
- freely defined events (that is, without reference to time or quantity)
Supplementary Documentation - QKZRASTER 1212
Use
You can define a combination of fields in Customizing for the Identification of inspection points. In this field combination both user-defined fields and fixed fields are specified in an individual sequence using key words.
Procedure
Examples
Wire basket/shift
A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.
At the operation level, an inspection interval is predefined for every 50 units.
You can show this by the following inspection point identifier:
Predefined field dependent on inspection point type (' ')
Field active Key word
User fields Field active Key word
Text Length 18
Text Length 10
No. Length 10 1 Wire basket
No. Length 3 X Shift
Date
Time
By marking the "Field active" column, you can make a field an optional field.
In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.
Vessel/Date/Time
In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).
This can be be shown by the following inspection point identifier:
Predefined field dependent on inspection type (' ')
Field active Key word
User fields Field active Key word
Text Length 18
Text Length 10
No. Length 10
No. Length 3 1 Vessel
Date 2 Date
Time 3 Time
Test equipment
Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.
This can be be shown by the following inspection point identifier:
Predefined field dependent on inspection type ('1')
Field active Key word
Equipment 1 Test equipment
User fields Field active Key word
Text Length 18
Text Length 10
No. Length 10
No. Length 3
Date
Time
Note
Even if the test equipment type allows for certain fields, you can define additional user fields.
Dependencies
If you enter a value for the field combination in the task list header, this value is copied into the inspection lot.
Examples
History
| Last changed by/on | SAP | 19980320 |
| SAP Release Created in |
