| Status | |
|---|---|
| Owner | |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Purpose
The purpose of this document is to define the conversion approach to create Maintenance Plan Start in S/4 HANA.
The purpose of the PM Plan is to initiate the creation of Work Orders and/or Notifications based on the criteria specified in the Maintenance Plans.
Currently, Syensqo utilises 10 non-standard Maintenance Plan types as below as below:
| Source | Category | Description |
|---|---|---|
| PF2 | PE | Order for equipments |
| PF2 | ZI | Inspection |
| PF2 | ZQ | Order for QM analysis |
| WP1 | ZI | Notification Basic Inspection |
Based on the conversion approach for Maintenance Plan, the legacy Maintenance plans are mapped to one of the two plan types detailed below reducing variability, complexity and non-standard application of Maintenance plan types.
- NO – for system generated notifications
- PM – for system generated work orders
Conversion Scope
The conversion scope covers the approach for Starting PM Plan (Maintenance Plan) in S/4 HANA system.
The MP data to be started includes:
- Maintenance Plans to be migrated as per CNV-1016 Maintenance Plan and Item
The data from legacy system excludes:
- Exclusion List of Maintenance Plans to be 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 | Maintenance Plan Start will be collected via DCT. An initial extract of the relevant Maintenance Plan Start will be provided in google sheet format to assist business in decision making on including any relevant Maintenance Plan Start from PF2 and WP2. Any additional Maintenance Plan Start data that need to be created to support the new design may be added in the DCT. A review and standardization will be done across all Maintenance Plan Start data in the DCT. |
Additional Information
Multi-language Requirement
Not Applicable
Document Management
Not Applicable
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.
Target Design
With Functional input, document the technical design of the target fields that are in the scope of this document.
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| MPLA | WARPL | WARPL | Maintenance Plan Identifier | CHAR | 12 | Mandatory |
| MPLA | STADT | STADT | Start Date for Scheduling | DATS | 8 | |
| MPLA | STIME | Start Time for Scheduling | TIMS | 6 | ||
| MPLA | SZAEH | SZAEHC | Start counter reading | CHAR | 22 | |
| MPLA | LRMDT | Date of Last Completion in Maintenance Plan | ||||
| MPLA | CONF_TIME | Completion Time of Call | ||||
| MPLA | ZYKLOFFSET | Offset with Start in Cycle | Mandatory | |||
| MPLA | ZYKLUNIT | Unit for the Performance of Maintenance Tasks | ||||
| MPLA | RZAEH | Completion Counter Reading | ||||
| MPLA | CYCLESEQIND | Cycle Set Sequence | ||||
| MPLA | SETREPEATIND | Repeat Factor for Cycle Set Sequence | ||||
| MPLA | KEEP | Keep Calls on Hold (KEEP=X) or Delete Calls on Hold (KEEP=' ') Default Value |
Data Cleansing
No data cleansing is required for Maintenance Plan Start in the legacy system. If any cleansing is deemed necessary, it will be performed outside of the system.
As a result, the cleansed Maintenance Plan Start data will be populated directly in the Data Collection Template (DCT).
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
Summarize Data Privacy and Sensitivity Requirements, if anyExtraction
- Syniti Migrate connects to the sources.
- An initial extract of the relevant Maintenance Plan Start data will be loaded into a google sheet report to assist business with any standardization.
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
If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.| 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 Object data with exception of some fields which require transformation as mentioned in the transformation rule.<Object> DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
Extraction Dependencies
List the steps that need to occur before extraction can commence
| 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 Syniti Migrate 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 Syniti Migrate
- 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
Use the exact name and reference this section in the “Transformation rules” above| 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
The following pre-load validations will be performed by the 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
The following pre-load validations will be performed by the 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
Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence
Configuration
List the Configurations required before loading can commence
| 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
The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management
| Error Type | Error Description | Action Taken |
|---|---|---|
Post-Load Validation
Project Team
The following post-load validations will be performed by the 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
The following post-load validations will be performed by the 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.
Any additional key assumptions.
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.