| 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)
The data from legacy system excludes:
- Inactive Maintenance Plans ((System Status TJ02T-TXT04 = INAC)
- Maintenance Plans (MPLA.WARPL) to be Excluded (Exclusion List Mapping: EXC-Maintenance Plan Start) from getting started
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, excluding the records which require business decision, 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 requiring 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 Identifier | CHAR | 12 | 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 Calls on Hold (KEEP=X) or Delete Calls on Hold (KEEP=' ') Default Value | CHECKBOX | 1 | Conditional |
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| 9001-001 | C1 | Relevant and Active Maintenance Plan not scheduled until Business Continuity Cutoff Date. Set the Maintenance Plan to Inactive if not required to be started. | 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. | Maintenance Plan, Latest Plan Date | 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, excluding the records which require business decision, 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
Relevant Maintenance Plan for Maintenance Plan Start for plants which have data existing from PF2 and WP2 requiring business decision, 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 > S/4 Strategy Plans (with more than 1 package assigned)
- Legacy Strategy Plans > S/4 Strategy Plans (with enrichment in the items and packages)
Data Privacy and Sensitivity
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 |
|---|---|---|---|---|
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
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 |
|---|---|---|
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
Exclusion List of Maintenance Plans to be Started | |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
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 |
|---|---|---|
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram) | |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
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 Plant Start is in scope based on data design and any exception requested by business.