| Status | Approved |
|---|---|
| Owner | |
| Stakeholders | ERGUIZA-ext, Pinky Love TEE-ext, Paul JOSHI-ext, Aditya VILARES, ines LEIGHTON-ext, Dean LAKKAD-ext, Anirudh STEFANESCU-ext, Aurelia MOUSSA-ext, Eva |
Purpose
The purpose of this document is to define the conversion approach to load Maintenance Plan Start object in order to Start the Maintenance Plans in S/4 HANA.
The purpose of the Maintenance Plan Start is to initiate the creation of Work Orders based on the criteria specified in the Maintenance Plans.
Maintenance Plans for Syensqo are defined with the purpose of:
- Preventive Plans - Used for Time Based and Condition based Preventive Maintenance with a defined Strategy
- Shutdown Plans - Shutdown Plans with a Defined Strategy
Conversion Scope
The conversion scope covers the approach for loading Maintenance Plan Start object in S/4 HANA system.
The data from legacy system includes:
- All relevant Maintenance Plans (MPLA-WARPL) in MHIS table, with the next planned call record after the call that has been completed
The data from legacy system excludes:
- Inactive Maintenance Plans </Start CR0438> (
System Status TJ02T-TXT04 = INACJEST-STAT = 'INAC' and (JEST-INAC <> 'X') </End CR0438>) - Maintenance Plans (MPLA-WARPL) to be Excluded (Exclusion List Mapping: EXC-Maintenance Plan Start) from getting started
List of Tables to extract for this object is maintained here: Extract Table Register.
List of source systems and approximate number of records
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2, WP2 | Relevant Maintenance Plan for Maintenance Plan Start will be extracted from PF2 and WP2, which include the following scenarios (not exhaustive):
| 70,000 | S/4 HANA | 70,000 |
| DCT | Maintenance Plan for Maintenance Plan Start for plants which do not have data existing from PF2 and WP2 | TBD | S/4HANA | TBD |
| DCT | Relevant Maintenance Plan for Maintenance Plan Start for plants which have data existing from PF2 and WP2 which fail pre-load validation during transformation. These data require business decision and may fall under the following example scenarios (not exhaustive):
| TBD | S/4HANA | TBD |
Additional Information
Multi-language Requirement
Not Applicable
Document Management
Not Applicable
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| MHIS | WARPL | WARPL | Maintenance Plan | CHAR | 12 | Mandatory |
| - | ZWERKS | WERKS | Plant | CHAR | 4 | Mandatory |
| MHIS | LRMDT | LRMDT | Date of Last Completion in Maintenance Plan | DATS | 8 | Conditional |
| MHIS | OFFZE | OFFZE | Offset with Start in Cycle | FLTP | 16 | Conditional |
| MHIS | ADUNIT | DZEIEH | Unit for the Performance of Maintenance Tasks | CHAR | 3 | Conditional |
| MHIS | RZAEH | RZAEH | Completion Counter Reading | FLTP | 16 | Conditional |
| - | KEEP | - | Keep or Delete Calls on Hold | CHECKBOX | 1 | Conditional |
| MHIS | NPLDA | NPLDA | Next Planned Date | DATS | 8 | Display only for validation. |
MHIS | ZZAEHL | PAKETZAEHL | Maintenance Package Number (combined) | CHAR | 40 | Display only for reference. This custom field will contain list of all packages for the next call, separated by a single space (' ') |
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| 9001-001 | C1 | Relevant and Active Maintenance Plan is not scheduled until Business Continuity Cutoff Date. | Active Maintenance Plan is defined by System Status TJ02T-TXT04 <> INAC Business Continuity Cutoff Date is defined by parameter (MHIS-NPLDA). Based on all the relevant and active Maintenance Plans in MHIS table, identify what is the latest Plan Date (MHIS-NPLDA). If the date is before the Business Continuity Date parameter, this is an error. In this example scenario, the latest Plan Date for consideration of this report is 13 September 2026.
Note: Business to either set the Maintenance Plan to Inactive if not required to be started, or schedule the Maintenance Plan until after the Business Continuity Cutoff Date | Maintenance Plan, Plant, Latest Call No, Latest Plan Date Note: Plant is derived from the planning plant of one of the Maintenance Item (MPOS-IWERK) | PF2, WP2 |
Note: List of Cleansing is maintained here: Conversion Specs Register (DCT & Cleansing Report)
Conversion Process
The high-level process is represented by the diagrams below.
The following represents the high-level process for Source System Extraction:
Relevant Maintenance Plan for Maintenance Plan Start will be extracted from PF2 and WP2, which include the following scenarios (not exhaustive):
- Legacy Strategy Plans > S/4 Strategy Plans (with no further enrichment in the items and packages)
- Legacy Single Cycle Plans > S/4 Strategy Plans (with only 1 package assigned)
The following represents the high-level process for DCT:
Collection will be done manually in the Data Collection Template for the following scenarios:
- For sites not on SAP-PF2 or WP2 systems
Collection will be done manually in the Data Collection Template for the following scenarios:
Relevant Maintenance Plan for Maintenance Plan Start for plants which have data existing from PF2 and WP2 which fail pre-load validation during transformation. These data require business decision and may fall under the following example scenarios (not exhaustive):
- Maintenance Plans in legacy without scheduled calls all the way to the Business Continuity Cutoff Date
- Legacy Single Cycle Plans migrated as S/4 Strategy Plans (with more than 1 package assigned)
- Legacy Strategy Plans migrated as S/4 Strategy Plans (with enrichment in the items and packages)
Data Privacy and Sensitivity
Not Applicable.
Extraction
Extract data from a source into Advanced Data Migration and Management (ADMM). There are 2 possibilities:
- The data exists. ADMM connects to the source and loads the data into ADMM . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ADMM cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in ADMM . This is to be conducted using DCT (Data Collection Template) in ADMM
The agreed Relevancy criteria is applied to the extracted records as reference point to identify the records that are applicable for the data construction in the DCT.
Extraction Run Sheet
| Req # | Requirement Description | Team Responsible |
|---|---|---|
| 1 | Extract data from source system based on relevancy rule | SyWay Data Team |
| 2 | Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. | SyWay Data Team |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| Not Applicable |
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for Maintenance Plan Start data with exception of some fields which require transformation as mentioned in the transformation rule.
- The extracted report will be loaded into the required structure using the DCT.
- Standardization activities (including deduplication, standardization and additions) will be carried out within the DCT.
Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.
Note: All rules specified below should be documented as a tooltip in the DC Page.
Format:
- Line 1: Mandatory / Conditional
- Line 2: Remaining text
1. Maintenance Plan Start Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyWARPL | Maintenance Plan Identifier | Mandatory Must either exist in legacy (for PF2/WP2 data), or exist in Maintenance Plan DCT. |
| ZWERKS | Plant | Mandatory Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes Must be valid Planning Plant associated with the Maintenance Plan. |
| LRMDT | Date of Last Completion in Maintenance Plan | Conditional Mandatory if the Maintenance Plan is Time Based. Leave blank if the Maintenance Plan is Performance Based. Must be in DDMMYYYY format |
| OFFZE | Offset with Start in Cycle | Conditional Populate if offset is required. Allowed values: Numeric values more than 0. Leave blank if offset is not required. |
| ADUNIT | Unit for the Performance of Maintenance Tasks | Mandatory Allowed values: Valid UOM from T006. Must align with the Cycle Unit of the Maintenance Plan. |
| RZAEH | Completion Counter Reading | Conditional Mandatory if the Maintenance Plan is Performance Based. Leave blank if the Maintenance Plan is Time Based. |
| KEEP | Keep or Calls on Hold | Leave blank This field is only required if the Maintenance Plan needs to be rescheduled and there are existing calls on hold. X = Keep Calls on Hold. Blank = Delete Calls on Hold. |
2. Maintenance Plan Start Exclusion Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyWARPL | Legacy Maintenance Plan | Mandatory Must exist in legacy (PF2/WP2) Note to developer: This is the key field |
| zLegacyWERKS | Legacy Plant | Mandatory Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes Legacy Planning Plant associated with the Legacy Maintenance Plant Note to developer: This is the key field |
| COMMENT | Comment | Mandatory Populate requirement for Exclusion Note to developer: This is NOT the key field, but make this mandatory in the DCT |
Note: List of DCTs is maintained here: Conversion Specs Register (DCT & Cleansing Report)
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Relevancy Criteria for Maintenance Plan and Item | SyWay Data Team |
Transformation
The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow ADMM to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in ADMM
- Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation
Transformation Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Obtain DCT Sign-off from Business. | SyWay Data Team |
2 | In dspMigrate, select the wave – S4/HANA – Plant Maintenance | Syniti |
3 | Go to Process Area Launch and Process the Object – Maintenance Plan Start | Syniti |
4 | Review and Validate Error and Preload Reports | Syniti |
5 | Execute the transformation to prepare the target tables | Syniti |
6 | Validate data from pre-load and error reports | Business/Data owner |
7 | Populate DCT for records which need business decisions (if required) | Business/Data owner |
8 | Repeat steps 1-7 as required to allow business the opportunity to add additional records into the DCT based on validations performed during transformation | Syniti |
9 | Generate load files | Syniti |
Transformation Rules
1. Maintenance Plan Start (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | MHIS | zLegacyWARPL | Maintenance Plan Identifier | S/4 HANA | MHIS | WARPL | Maintenance Plan | Value Mapping: Maintenance Plan |
| 2 | DCT | - | ZWERKS | Plant | - | - | ZWERKS | Plant | Value is not for loading, only for validation. |
| 3 | DCT | MHIS | LRMDT | Date of Last Completion in Maintenance Plan | S/4 HANA | MHIS | LRMDT | Date of Last Completion in Maintenance Plan | Direct Mapping |
| 4 | DCT | MHIS | OFFZE | Offset with Start in Cycle | S/4 HANA | MHIS | OFFZE | Offset with Start in Cycle | Direct Mapping |
| 5 | DCT | MHIS | ADUNIT | Unit for the Performance of Maintenance Tasks | S/4 HANA | MHIS | ADUNIT | Unit for the Performance of Maintenance Tasks | Direct Mapping |
| 6 | DCT | MHIS | RZAEH | Completion Counter Reading | S/4 HANA | MHIS | RZAEH | Completion Counter Reading | Direct Mapping |
| 7 | DCT | - | KEEP | Keep or Calls on Hold | S/4 HANA | - | KEEP | Keep or Delete Calls on Hold | Direct Mapping |
| 8 | - | - | - | - | - | - | NPLDA | Next Planned Date | Blank |
| 9 | - | - | - | - | - | - | ZZAEHL | Maintenance Package Number (combined) | Blank |
2. Maintenance Plan Start (ECC)
Note: MHIS table contains all the maintenance plan calls (multiple records per Maintenance Plan). To load Maintenance Plan Start, only the latest completion must be considered.
Selection criteria for transformation of records from MHIS table. Based on relevant Maintenance Plan Start (WARPL):
- Select the earliest record(s) where Completion Date (MHIS-LRMDT) is null, order by Call Number (MHIS-ABNUM)
- If there are more than one record with the same Call Number, then select the first record, and combine the multiple package numbers (MHIS-ZAEHL) into one field (ZZAEHL) separated by single space (' ')
Scenario for extraction from MHIS Table is illustrated in this example:
- Based on the earliest record(s) where Completion Date is null, call number 9 should be extracted for this Maintenance Plan.
- In this instance, the next planned date should be 18 June 2026, and the Maintenance Package Number should be "01 02 03"
- For the Last Completion Date (MHIS-LRMDT) - select the Completion Date of the previous call (which is call number 8) - which is 15 December 2025
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | MHIS | WARPL | Maintenance Plan | S/4 HANA | MHIS | WARPL | Maintenance Plan | Value Mapping: Maintenance Plan |
| 2 | - | - | - | - | - | - | ZWERKS | Plant | Derive the Planning Plant (MPOS-IWERK) from one Maintenance Item of the Maintenance Plan |
| 3 | PF2, WP2 | MHIS | LRMDT | Date of Last Completion in Maintenance Plan | S/4 HANA | MHIS | LRMDT | Date of Last Completion in Maintenance Plan | For Time Based Plan: Direct Mapping - select the Completion Date of the Previous Call For Performance Based Plan: Default to Blank |
| 4 | PF2, WP2 | MHIS | OFFZE | Offset with Start in Cycle | S/4 HANA | MHIS | OFFZE | Offset with Start in Cycle | Floating point conversion conversion from SI unit. Consider the unit from (ADUNIT) and compare against table T006 for conversion. Explanation for conversion from SI Unit: a) Based on the UOM of the ADUNIT, retrieve record from T006-MSEHI b) With the value: > Dividy by ZAEHL, and > Multiply by NENNR |
| 5 | PF2, WP2 | MHIS | ADUNIT | Unit for the Performance of Maintenance Tasks | S/4 HANA | MHIS | ADUNIT | Unit for the Performance of Maintenance Tasks | Direct Mapping |
| 6 | PF2, WP2 | MHIS | RZAEH | Completion Counter Reading | S/4 HANA | MHIS | RZAEH | Completion Counter Reading | For Performance Based Plan: Select the Completion Counter Reading of the Previous Call Floating point conversion conversion from SI unit. Consider the unit from (ADUNIT) and compare against table T006 for conversion. Explanation for conversion from SI Unit: a) Based on the UOM of the ADUNIT, retrieve record from T006-MSEHI b) With the value: > Dividy by ZAEHL, and > Multiply by NENNR For Time Based Plan: Default to Blank |
| 7 | PF2, WP2 | - | KEEP | Keep or Delete Calls on Hold | S/4 HANA | - | KEEP | Keep or Delete Calls on Hold | Default to blank |
| 8 | PF2, WP2 | MHIS | NPLDA | Next Planned Date | - | - | NPLDA | Next Planned Date | For Time Based Plan: Direct Mapping Value is not for loading, only for validation. For Performance Based Plan: Default to Blank |
| 9 | PF2, WP2 | MHIS | ZZAEHL | Maintenance Package Number (combined) | - | - | ZZAEHL | Maintenance Package Number (combined) | For Time Based Plan: Combine the multiple package numbers separated by single space (' ') Value is not for loading, only for reference. For Performance Based Plan: Default to Blank |
Note:
- Time Based Plan is defined by (S/4 SAP) MPLA-STICH = Blank, 1 or 2
- Performance Based Plan is defined by (S/4 SAP) MPLA-STICH = 3
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
| EXC-Maintenance Plan Start | Exclusion List of Maintenance Plans to be Started |
| Maintenance Plan | Old to new Maintenance Plan |
| Plant | Mapping of legacy Plant to new Plant |
List of Transformation Mappings with additional details is maintained here: Transformation Mappings
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure DCT tables completeness | SyWay Data Team |
2 | Ensure all Transformation mappings are up to date. | SyWay Data Team |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Verify Record Count | SyWay A2D Data Team to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | SyWay A2D Data Team to verify that all fields below meet pass the checks:
|
| Review Error Reports | Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data. |
Business
Completeness
| Task | Action |
|---|---|
| Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data). |
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure Pre-load sign-offs are obtained. | SyWay Data team |
2 | Go to the load tool and select the correct load Program. | SyWay Data team |
3 | Proceed with Data load. | SyWay Data team |
4 | Validate few records loaded by accessing standard transactions | SyWay Data team |
5 | Generate the post load reports in the tool. | SyWay Data team |
6 | Log errors as defects, if any and address resolutions. Close defects. | SyWay Data team |
7 | Resolve defects by reupload and re-generate post load reports if necessary. | SyWay Data team |
8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
9 | Repeat steps 5 to 7 if necessary. | SyWay Data team |
Load Phase and Dependencies
Cutover
Configuration
| Item # | Configuration Item |
|---|---|
| Not Applicable |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1016 | Maintenance Plan and Item |
| 9002 | Measurement Document |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Invalid Data | Invalid Maintenance Plans and Items | Expedite whether the master data is available in the system |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Count | SyWay A2D Data Team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA. |
Verify Logs | Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.). |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Verify that the EAM Maintenance Plant Start data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA. |
Business
Completeness
| Task | Action |
|---|---|
Verify Count | Download Post Load Reports from dspMigrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Verify that the EAM Maintenance Plant Start data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA. |
Key Assumptions
- Maintenance Plan Start is in scope based on data design and any exception requested by business.
- Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.
- Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
- All Maintenance Plans to be started in S/4 are Strategy Based Plans.
- Multiple Counter Maintenance Plans are not in scope.
- Manual starting of Maintenance Plans are not in scope.
- For Starting of the Performance Based Maintenance Plans in S/4, no validations are performed at this point to verify if the next call date is after Business Continuity Cutoff Date. More data needs to be analysed to define the validation and will be performed after the Mock cycles are completed.
- Proposed target design follows the structure of Function Module: MPLAN_START_CYCLE