SAP ABAP Data Element CC_AEEIN (Leading change master record)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷
CA-GTF-ECM (Application Component) Engineering Change Management
⤷
CC (Package) Engineering Change Management
⤷
⤷
Basic Data
| Data Element | CC_AEEIN |
| Short Description | Leading change master record |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AENNR | |
| Data Type | CHAR | Character String |
| Length | 12 | |
| Decimal Places | 0 | |
| Output Length | 12 | |
| Value Table | AENR |
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 | Lcmr |
| Medium | 15 | Lead. chg. mas. |
| Long | 20 | Lead. chg. master |
| Heading | 4 | Lcmr |
Documentation
Definition
Superior (higher-level) change master record in a change hierarchy. It groups together several change packages for the change process.
Use
Important control functions that are relevant to all the allocated change packages are maintained in a leading change master record. For example:
- Definition of when the change should become effective (for example, the valid-from date)
- Release key
Procedure
Examples
A complex change is controlled by a change hierarchy tha has the following change master records allocated to it:
- Leading change master record with the change number NR-1
Entry for effectivity (valid from 10.01.1999)
Reöease key (for example, release for production)
- Allocated change packages with the following change numbers:
- P-1
- P-2
You process the objects with reference to the change packages.
History
| Last changed by/on | SAP | 20020827 |
| SAP Release Created in |