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:

1. All relevant Maintenance Plans (MPLA-WARPL)

The data from legacy system excludes:

1. Inactive Maintenance Plans ((System Status TJ02T-TXT04 = INAC)
2. 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

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.

Data Cleansing

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.

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 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:

1. The data exists. ADMM connects to the source and loads the data into ADMM . There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if ADMM cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. 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

Selection Screen

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Measurement Document data with exception of some fields which require transformation as mentioned in the transformation rule.

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

2. Maintenance Plan Start Exclusion Data Construction Rules

Extraction Dependencies

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:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in ADMM 
2. 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

Transformation Rules

1. Maintenance Plan Start (DCT)

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):

1. Select the latest record(s) where Completion Date (MHIS-LRMDT) is not null, order by Call Number (MHIS-ABNUM)
2. 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 (' ')

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Notes:

1. Unless specified, all validations are performed at the target (and not in SAP)

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Load Phase and Dependencies

Cutover: 9001 - Maintenance Plan Start

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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.

See also

Change log