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 | LRMDT |
| Short Description | Date of last completion in maintenance plan |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Compl.Date |
| Medium | 17 | Last Completion |
| Long | 20 | Completion date |
| Heading | 10 | Compl.Date |
Documentation
Definition
Date on which the maintenance date was completed. The date entered here
is used as the basis for the further scheduling of the maintenance plan.
Supplementary Documentation - LRMDT 0001
Date on which you confirm or have confirmed a maintenance task.
The field has two different meanings:
- When you confirm, you can enter in this field the date on which a maintenance call should be confirmed. In addition to the completion confirmation in scheduling, you can also confirm a maintenance call object, for example, by processing the call object "order" and completing it technically.
- For rescheduling using a Start in cycle, you confirm the last preventive maintenance with this date. This is usually today's date.
Example
Start in cycle
v
|=====|====|====|=====>
1M 2M 3M 4M
The confirmation date states when the last preventive maintenance was performed (here 3M). This date forms the basis for further scheduling.
Note
If the confirmation date is in the past, then the system generates maintenance call objects retrospectively according to the maintenance plan category, if there are still maintenance packages between the confirmation date and the Start in cycle.
Supplementary Documentation - LRMDT 0002
Date on which you have confirmed a maintenance task.
There are two ways in which this field is filled out automatically:
- You have completed the maintenance call object belonging to this maintenance call; this means orders or notifications completed and service entry sheets released. The completion or release date is copied into this field.
If several maintenance call objects belong to a maintenance call, for example, in the case of a maintenance plan with several maintenance items, then the completion or release date of the last completed maintenance call object is valid. - If you have confirmed the maintenance call directly in the maintenance plan using the Confirm function, then this date is copied into the field.
Supplementary Documentation - LRMDT 0003
Use
The finish date displayed in themaintenance item is determined from the call object belonging to the maintenance item.
This date can deviate from the finish data at the maintenance plan header level - provided that multiple maintenance objects for a date each generated a call object. At maintenance plan header level, the last date of all the finished call objects is displayed.
The finish date displayed in the maintenance plan header is relevant for calculating the follow-up date.
Dependencies
Example
Supplementary Documentation - LRMDT 0004
Use
The finish date displayed in themaintenance item is determined from the call object belonging to the maintenance item.
This date can deviate from the finish data at the maintenance plan header level - provided that multiple maintenance objects for a date each generated a call object. At maintenance plan header level, the last date of all the finished call objects is displayed.
The finish date displayed in the maintenance plan header is relevant for calculating the follow-up date.
Dependencies
Example
History
| Last changed by/on | SAP | 20020506 |
| SAP Release Created in |
