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 | WOFFS2 |
| Short Description | Maintenance package offset (performance) |
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 | Offset |
| Medium | 15 | Offset |
| Long | 20 | Offset (performance) |
| Heading | 22 | Offset (performance) |
Documentation
Definition
The maintenance package offset that is performance-based determines the figure after which the maintenance package first becomes due.
You must enter an offset when the first time a maintenance package is to be performed does not correspond with the cycle length.
You can use the offset to execute a one-time maintenance package (a maintenance cycle for multiple counter plans) by just maintaining the offset.
Example
Cycle length of maintenance package: every 10,000 km
First time due (offset): after 1000 km
Note
If you want to maintain both the offset and the cycle, then the maintenance package (the maintenance cycle for multiple counter plans) is only executed after the offset is overwritten.
You must maintain an offset directly if you want to create a one-time package or a one-time cycle, for example, for a first inspection. In this case, however, you cannot enter a cycle duration.
History
| Last changed by/on | SAP | 19980218 |
| SAP Release Created in |
