Hierarchy

⤷

⤷

Basic Data
Data Element | ADPM_IAOB |
Short Description | CMC: Use Relationships to Link Orders |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | Use Rel. |
Medium | 20 | Use Rel.for Ord.Link |
Long | 22 | Use Rel.for Order Link |
Heading | 47 | Use Rel.for Order Link (Cross-Order Scheduling) |
Documentation
Definition
Links different orders for the same equipment.
Different orders covering the same equipment but with different operations are a frequent occurrence. You can use the relationship functions to link these orders.
At runtime the Component Maintenance Cockpit (CMC) bundles the linked orders internally. Then the CMC groups the operations from these linked orders and schedules and prioritizes them together (depending on the Customizing settings). Visually, these orders are still separate.
Examples
Orders XXX, YYY, and ZZZ are for equipment 1234. They are linked by a relationship.
Order XXX contains operations 10, 30 and 50, order YYY contains operation 20, and order ZZZ contains operations 40 and 60.
At runtime, the CMC bundles these orders into an internal order. Then it schedules the operations sequentially (that is: 10, 20, 30, 40, 50, 60). However, orders XXX, YYY, and ZZZ are still separate in the system.
Dependencies
The operations must be numbered differently in the orders.
History
Last changed by/on | SAP | 20050301 |
SAP Release Created in |