Hierarchy
⤷
⤷
⤷
Basic Data
| Data Element | ANDOR |
| Short Description | Indicator for OR or AND link |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RADIO | |
| 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 | AND/OR |
| Medium | 15 | Operation type |
| Long | 20 | Operation type |
| Heading | 3 | A/O |
Documentation
Definition
Indicator for defining the relationship between the maintenance cycles
In the case of an OR operation, a maintenance call is due as soon as as one maintenance cycle finishes.
In the case of an AND operation, a maintenance call is only due when all the maintenance cycles have finished.
Use
Procedure
Define a link type for the maintenance cycles.
A change in the link type is considered immediately for the next scheduling.
Examples
You define a maintenance plan for aircraft maintenance containing the following cycles:
- Cycle 1: every 350 landings
- Cycle 2: every 1000 operating hours
- Cycle 3: every 170000 air miles
The aircraft flies for 1200 hours and 165000 miles, during which time it makes 340 landings.
In the case of an OR operation, a maintenance date has been reached, as one of the three cycles has finished. Therefore the system creates a maintenance order.
In the case of an AND operation, a maintenance date has not been reached. A maintenance order will not be created until the aircraft has flown another 5000 miles and made another 10 landings.
Dependencies
History
| Last changed by/on | SAP | 20011009 |
| SAP Release Created in |