Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
LO-ECH (Application Component) Engineering Change Management⤷
CCSEQ (Package) Sequence Graph for Change Numbers
Basic Data
| Data Element | CCSEQ_OBJEC_KEY |
| Short Description | Object Key |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CCSEQ_OBJEC_KEY | |
| Data Type | CHAR | Character String |
| Length | 50 | |
| Decimal Places | 0 | |
| Output Length | 50 | |
| 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 | 6 | Object |
| Medium | 6 | Object |
| Long | 15 | Object Key |
| Heading | 6 | Object |
Documentation
Definition
Usage location key for a change number
Use
When adding a change status to the usage location table in the change sequence graph, the system stores the object key for identification. For example, the key is used to map relationships of the change sequence graph, or to display the usage locations for a relationship.
Generally, only the keys from component variants in the iPPE product structure are used.
Dependencies
The system uses the object keys to map the relationships of a change sequence graph. The system can only map a relationship when at least two usage location exist with an identical object key. The sequence within an object is determined using the rank.
Example
Various change statuses of a component variant in the iPPE product structure are stored under the same object key in the usage location table of the change sequence graph, namely the CHAR32 GUID for iPPE Variant with Conversion.
History
| Last changed by/on | SAP | 20050411 |
| SAP Release Created in | 600 |
