Hierarchy
⤷
⤷
⤷
Basic Data
| Data Element | TERMKNZ |
| Short Description | Scheduling indicator |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TERMKNZ | |
| 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 | SchedInd. |
| Medium | 15 | SchedIndic. |
| Long | 20 | Scheduling indicator |
| Heading | 1 | S |
Documentation
Definition
Within the preventive maintenance strategy, you can use different scheduling indicators, to define the type of scheduling for preventive maintenance plans or define a cycle set.
The following scheduling indicators are possible:
Example
Time-based maintenance plans
You schedule a preventive maintenance plan with a strategy containing a monthly package (for scheduling purposes a month is taken to be 30 days):
- Time
Current date: 04/10/1995
Next planned date: 03/11/1995 -> current date + 30 days
- Key date
Current date: 04/10/1995
Next planned date: 04/11/1995 -> on the 4th day of each month
- Factory calendar
Current date: 04/10/1995
Next planned date: 16/11/1995 -> current date (or next workday)
+ 30 workdays
Performance-based maintenance plans
You can schedule a preventive maintenance plan on the basis of operating hours, kilometers traveled, and so on. The system calculates the planned date in respect of the following counter data:
- annual estimate
- current counter reading
- current date
History
| Last changed by/on | SAP | 20011009 |
| SAP Release Created in |