Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
QA (Package) QM master data
Basic Data
| Data Element | QLZEITKZ |
| Short Description | Long-Term Inspection |
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 | LONG_TERM_INSP_IND | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | LngTrmInsp |
| Medium | 15 | Long-term insp. |
| Long | 20 | Long-term inspection |
| Heading | 3 | LTI |
Documentation
Definition
Use
If you set this indicator, the characteristic is subject to a long-term inspection.
If you set this indicator for at least one required characteristic, you can distinguish between "Short-term inspection completion" and a final completion of the inspection (status: Inspection close completed).
Optional characteristics only work as long-term characteristics, when they are set for processing before inspection completion.
You activate a long-term inspection by confirming the inspection completion for the short-term characteristics. This occurs either in conjunction with the making of the usage decision, or by calling up the special function "Short-term inspection completed."
In a long-term inspection:
- There can already be a usage decision for the inspected material during the long-term inspection
- You can still record inspection results for long-term characteristics, once you have made the usage decision
- The system sets a separate status in the inspection lot to identify the long-term inspection and it provides special worklists and workflow tasks for this purpose
Procedure
Examples
Dependencies
If you want to copy inspection results from a long-term inspection into a batch valuation, note that the data is transferred when the following events occur:
- Results from a short-term inspection are transferred as soon as the statuses "Short-term inspection completion" and "Usage decision made" are set.
- Results from a long-term inspection are transferred as soon as the statuses "Long-term inspection completion" and "Usage decision made" are set
This means that you must confirm or correct a usage decision, if it has been made after a short-term inspection. To do this, use the change transaction, a relevant worklist or an appropriate workflow task.
History
| Last changed by/on | SAP | 19991201 |
| SAP Release Created in |
