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 | QMETHERS |
| Short Description | Trigger Central Replacement of Inspection Method |
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 | ReplMeth. |
| Medium | 15 | Replace method |
| Long | 20 | Replace method |
| Heading | 1 | R |
Documentation
Definition
If you set this indicator, you can replace old versions that are in task lists with the new version when you create a new inspection method version.
When you save the inspection method, the system creates a list, which shows where the inspection method is used. You can then replace specific old versions for the inspection method with the new version.
Central replacement is not supported, if the inspection method is linked to the task list using a referenced master inspection characteristic.
Use
The system can manage different versions of master data records for inspection characteristics and inspection methods. The individual versions are clearly identified by a current version number that is assigned internally by the system. For each version, there is a date from which the data record is valid (valid-from date). Several versions can be valid for the same key date.
If you first create a master record (function "Create inspection characteristic" or "Create inspection method"), you can either give it an alphanumeric or numerical key, or let the system assign a numerical key (Number range definition). The system assigns this new master record version number 1. You must specify a valid-from date for this first version.
You can create additional versions of the master record in the following ways.
- You use the function "Create version". You must specify a date from which the version is valid. This date must not be used in another version of the data record.
- You use the function "Change". You can choose and change a valid version for a key date.
However, if this version is released and if history management is defined for inspection characteristics or inspection methods in the settings at plant level, the system then creates a new version with the same valid-from date. The original version is saved with no changes and can still be used.
History
| Last changed by/on | SAP | 19990310 |
| SAP Release Created in |
