Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
IPRM (Package) Application Development R/3 Preventive Maintenance
Basic Data
| Data Element | WZYKL1 |
| Short Description | Maintenance cycle |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WZYKL | |
| Data Type | CHAR | Character String |
| Length | 22 | |
| Decimal Places | 0 | |
| Output Length | 22 | |
| 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 | Cycle |
| Medium | 15 | Cycle |
| Long | 20 | Cycle |
| Heading | 22 | Cycle |
Documentation
Definition
The maintenance cycle defines the interval after which a task becomes due.
For a time-based or performance-based strategy plan, the maintenance intervals are derived from the maintenance packages entered in the maintenance strategy.
For a single cycle plan, you can enter the maintenance interval directly.
For a multiple counter plan, the maintenance cycles are also defined in the maintenance plan.
Example
- Time-based:
A task is to be performed every 3 months. The cycle is therefore 3 months.
- Performance-based:
A task is to be performed every 1000 miles. The cycle is therefore 1000 miles.
Note
In the case of a multiple counter plan, there are no individual packages as there are for performance-based and time-based maintenance plans. When a cycle is due, all the operations from the assigned task list are automatically due.
In order that the package representation is clear and the due dates of the packages are sensible for common deadlines, it is advantageous to define the cycles in the maintenance strategy so that the packages have the smallest common factor. Advantageously defined cycles have a positive effect if you use hierarchies for the individual packages in the case of performance-based and time-based maintenance plans.
Ideally, the smallest common factor corresponds to the smallest cycle.
For example, a good cycle:
3 months 6 months 9 months
20 days 40 days 60 days
A poor one:
3 months 5 months 9 months
20 days 41 days 63 days
History
| Last changed by/on | SAP | 19980218 |
| SAP Release Created in |
