Hierarchy

⤷

⤷

Basic Data
Data Element | CCSEQ_NODE_TYPE |
Short Description | Usage Location Type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CCSEQ_NODE_TYPE | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
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 | 9 | Obj. Type |
Medium | 9 | Obj. Type |
Long | 9 | Obj. Type |
Heading | 9 | Obj. Type |
Documentation
Definition
Usage location type of a change number for the change sequence graph.
Use
The system groups together the various application that use change numbers and are considered by the change sequence graph by assigning a type to the usage location of a change number.
The system assigns the usage location types CMP and COL as the default. These types are used for the change statuses in the iPPE product structure.
If customer-specific applications were connected to the change sequence graph, then you must assign customer-specific types to the resulting usage locations.
Dependencies
1. Convert usage location type into a relationship type, and vice versa.
The system generates relationships from the change numbers of the usage locations for the change sequence graph. The usage location type must be converted into the relationship type here, and vice versa.
2. Where-used list
When the system displays the cycles of a change sequence graph (transaction CCSEQ_CYCLE), the where-used list can be triggered for a relationship. The usage location type determines which application is to be searched.
Example
The usage location types CMP and COL describe change statuses in the iPPE product structure.
History
Last changed by/on | SAP | 20050411 |
SAP Release Created in | 600 |