Status

Page Status

Owner

TEEMAHAJAN-ext, Pauliesha

Stakeholders

LEIGHTON-ext, Dean ERGUIZA-ext, Pinky Love PUN-ext, Eddy JOSHI-ext, Aditya VILARES, ines LAKKAD-ext, Anirudh STEFANESCU-ext, Aurelia MOUSSA-ext, Eva BAGGA-ext, Abhishek

Purpose

The purpose of this document is to define the conversion approach to create Maintenance Plan and Item in S/4 HANA.

Legacy Maintenance Plan and Item is using a diverse range of formats across the different systems. There are instances where the same Maintenance Plan and Item is duplicated within and across sources, with informal words. This results in data inconsistency. As per SyWay design, EAM Maintenance Plan and Item will be standardized.

Conversion Scope

The scope of this document covers the approach for converting active Maintenance Plan and Item from Legacy Source Systems into S/4HANA following the Maintenance Plan and Item Master Data Design Standard.

Maintenance Plan from legacy system is relevant if:

have at least 1 valid maintenance Item

Maintenance Plan from legacy system is not relevant if:

Maintenance plan marked for deletion

Maintenance Item within each maintenance plan is considered relevant if:

It has at least 1 relevant material, FL or Equipment in ref object or item in object list based on material, FL and Equipment relevancy
At least 1 valid task list based on task list relevancy

Object list within each relevant maintenance item will only include FL and Equipment that is relevant based on FL and Equipment Relevancy.

List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2

Maintenance Plan:

An initial extract will be provided to business to evaluate.

Additional data/records may be required and these will be constructed via DCT.

Enrichment of in-scope data may be required and will be added via transformation rules (business/technical).

70,000

S/4HANA

70,000

PF2, WP2

Maintenance Items:

An initial extract will be provided to business to evaluate.

Additional data/records may be required and these will be constructed via DCT.

Enrichment of in-scope data may be required and will be added via transformation rules (business/technical).

74,000

S/4HANA

74,000

Additional Information

Multi-language Requirement

Multi language is supported for Maintenance plan and item. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Maintenance plan and item.

Document Management

Long text and DIR are not covered in this document as they are defined as another data object.

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

A Maintenance Strategy for an asset is established based on the Asset Management Plan, which outlines how the asset will be maintained throughout its lifecycle.
Syensqo defines both Preventive and Reactive Work Maintenance Strategies using a Maintenance Plans.

A Maintenance Item is an Integrated master data object created with the Maintenance plan, These Maintenance Items are used to update technical object that requires maintenance, along with its associated Task List.
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

Maintenance Plans and Items are TIER 3 Governed objects

Conversion Scope

The scope of this document covers the approach for converting Maintenance Plan and Item from Legacy Source Systems into S/4HANA following the Maintenance Plan and Item Master Data Design Standard.

A Maintenance Plan is a scheduling framework that determines timing and frequency of proactive maintenance tasks.
Key features:
- Can include one or more maintenance items
- Drives the proactive schedule maintenance calls (notifications/orders)

A Maintenance Item specifies the responsibilities, technical object and a task list to be performed. It defines:
- The equipment, functional location, or object list to be maintained
- The planner group and activity types
- The task list describing detailed operations

Key features:
- Multiple items can be assigned to one plan
- Each item can have its own task list
- Enables tracking of proactive maintenance history per object

The data from legacy system includes:

Maintenance Plan (MPLA-WARPL) that has at least 1 relevant Maintenance Item (MPOS-WAPOS)
Maintenance Items (MPOS-WAPOS) that has at least 1 valid task list:
- Task List Type (PLKO-PLNTY) can be any of: A - General Maintenance Task List; E - Equipment Task List; T - Task List for Functional Location
- Task List Status (PLKO-STATU) can be any of: 2 - Released for Order; 3 - Released for Costing; 4 - Released (General)
- Task List Usage (PLKO-VERWE) = "004"
Maintenance Items (MPOS-WAPOS) that has at least 1 active
- legacy Functional Location (IFLOT-TPLNR) - Source System Status (JEST-STAT) not (INAC or DLFL) and </Start CR0438> (JEST-INAC <> 'X') </End CR0438>OR
- legacy Equipment (EQUI-EQUNR) - Source System Status (JEST-STAT) not (INAC or ESTO or AVLB) and </Start CR0438>(JEST-INAC <> 'X') </End CR0438>
Maintenance Items (MPOS-WAPOS) having Maintenance Planning Plant (MPOS-IWERK) in scope - Refer to Value Mapping: Plant (Maintenance Plant = Yes)
Maintenance Items assigned to assembly (MPOS-BAUTL) with no Functional Location or Equipment assigned will added to DCT as an equipment/sub-equipment by business.

The data from legacy system excludes:

Maintenance Plan with delete system status </Start CR0438> (System Status ~~TJ02T-TXT04~~ JEST-STAT = DLFL) and (JEST-INAC <> 'X') </End CR0438>
Maintenance Items (MPOS-WAPOS) that are not assigned to Maintenance Plan (MPLA-WARPL)
Maintenance Items assigned to assembly (MPOS-BAUTL) with no Functional Location or Equipment assigned will be excluded from ECC transformation

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

Maintenance Plan:

Relevant Maintenance Plan will be extracted from PF2 and WP2

70,000

S/4HANA

70,000

PF2, WP2

Maintenance Items:

Relevant Maintenance Item will be extracted from PF2 and WP2

74,000

S/4HANA

74,000

DCT

Maintenance Plan and Maintenance Item for plants which do not have data existing from PF2 and WP2

TBD

S/4HANA

TBD

Additional Information

Multi-language Requirement
Maintenance Plan description will be made available in English.
Multi language is supported for Maintenance Plan. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Maintenance Plan.

Document Management
Not Applicable

Legal Requirement
Not Applicable

Special Requirements
Not Applicable

Target Design

The technical design of the target for this conversion approach.

1.Maintenance Plan

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MPLA	WARPL	WARPL	Maintenance Plan	CHAR	12	System Key field
MPLA	MPTYP	MPTYP	Maintenance plan category	CHAR	2	Mandatory
MPLA	STRAT	STRAT	Maintenance strategy	CHAR	6	Mandatory
MPLA	WPTXT	WPTXT	Maintenance Plan Text	CHAR	40	Mandatory
MPLA	VSPOS	VERSCHPLUS	Shift Factor for Late Completion	NUMC	3	Conditional
MPLA	TOPOS	TOLERPLUS	Tolerance for Late Completion (%)	NUMC	3	Conditional
MPLA	TONEG	TOLERNEG	Tolerance for Early Completion (%)	NUMC	3	Conditional
MPLA	VSNEG	VERSCHNEG	Shift Factor for Early Completion	NUMC	3	Conditional
MPLA	SFAKT	SFAKT	Cycle modification factor	DEC	3(2)	Conditional
MPLA	FABKL	FABKL	Factory calendar key	CHAR	2	Conditional
MPLA	HORIZ	HORIZONT	Call horizon for maintenance plan calls	NUMC	3	Mandatory
MPLA	HORIZ_QUALIFIER	EAM_CC_CALLHORIZON_QUALIFIER	Calculation Type of Call Horizon	CHAR	1	Mandatory
MPLA	ABRHO	ABRHO	Scheduling Period	NUMC	3	Mandatory
MPLA	HUNIT	HUNIT	Unit for Scheduling Period	UNIT	3	Mandatory
MPLA	CALL_CONFIRM	CALL_CONFIRM	Only Create New Call Object After Completing Predecessor	CHAR	1	Conditional
MPLA	STADT	STADT	Start date	DATS	8	Conditional
RMIPM	ZEIT	TIME_KNZ	Indicator for selection of time-based maintenance	CHAR	1	Conditional
MPLA	STICH	TERMKNZ	Scheduling indicator	CHAR	1	Conditional
MPLA	PLAN_SORT	PLAN_SORT	Sort field for maintenance plans	CHAR	20	Mandatory
MPLA	ENDDT_FOR_SCHED	EAM_ENDDT_FOR_SCHED	End Date for Scheduling	DATS	8	Conditional
RMIPM	POINT	IMRC_POINT	Measuring Point	CHAR	12	Conditional

2.Maintenance Plan Long Text Header

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
STXH	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory Key field
STXH	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory Key field
STXH	TDID	TDID	Text ID	CHAR	4	Mandatory Key field
STXH	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory Key field

3.Maintenance Plan Long Text Line

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
STXL	RELID	SYCHAR02	CHAR02 data element for SYST	CHAR	2	Mandatory Key field
STXL	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory Key field
STXL	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory Key field
STXL	TDID	TDID	Text ID	CHAR	4	Mandatory Key field
STXL	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory Key field
STXL	CLUSTD_TAG	TDFORMAT	Tag column	CHAR	1	Mandatory
STXL	ROWCOUNT	ROWCOUNT	Row number	NUMC	10	Mandatory
STXL	TXLINE	TDLINE	Text Line	CHAR	72	Mandatory

Note:

Long Text is not mandatory, only load when cleansed
One Long Text Header must have at least 1 Long Text Line

4.Maintenance Item

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MPLA	WARPL	WARPL	Maintenance Plan	CHAR	12	System Link to MPLA
MPOS	WAPOS	WAPOS	Maintenance item	CHAR	16	System Key field
MPOS	PSTXT	POSTXT	Item Short Text	CHAR	40	Mandatory
MPOS	AUART	AUFART	Order Type	CHAR	4	Mandatory
MPOS	PRIOK	PRIOK	Priority	CHAR	1	Mandatory
MPOS	PLNTY	PLNTY	Task List Type	CHAR	1	Mandatory
MPOS	PLNNR	PLNNR	Key for Task List Group	CHAR	8	Mandatory
MPOS	PLNAL	PLNAL	Group Counter	CHAR	2	Mandatory
MPOS	WPGRP	INGRP	Maintenance Planner Group	CHAR	3	Conditional
MPOS	APFKT	APFKT	Execution factor for whole task list	DEC	3(0)	Conditional
MPOS	ANLZU	ANLZU	System Condition	CHAR	1	Conditional
MPOS	ILART	ILA	Maintenance activity type	CHAR	3	Mandatory
RMIPM	TPLNR	TPLNR	Functional Location	CHAR	30	Mandatory
RMIPM	EQUNR	EQUNR	Equipment Number	CHAR	18	Conditional
MPOS	IWERK	IWERK	Maintenance Planning Plant	CHAR	4	System
RMIPM	GEWRK	GEWRK	Main work Centre for maintenance tasks	CHAR	8	Conditional
RMIPM	WERGW	WERGW	Plant associated with main work center	CHAR	4	System

Note: Each Maintenance Plan can have multiple Maintenance Items

5.Maintenance Item Long Text Header

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
STXH	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory
STXH	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory
STXH	TDID	TDID	Text ID	CHAR	4	Mandatory
STXH	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory

6.Maintenance Item Long Text Line

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
STXL	RELID	SYCHAR02	CHAR02 data element for SYST	CHAR	2	Mandatory Key field
STXL	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory Key field
STXL	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory Key field
STXL	TDID	TDID	Text ID	CHAR	4	Mandatory Key field
STXL	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory Key field
STXL	CLUSTD_TAG	TDFORMAT	Tag column	CHAR	1	Mandatory
STXL	ROWCOUNT	ROWCOUNT	Row number	NUMC	10	Mandatory
STXL	TXLINE	TDLINE	Text Line	CHAR	72	Mandatory

Note:

Long Text is not mandatory, only load when cleansed
One Long Text Header must have at least 1 Long Text Line

7.Maintenance Item Object List

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MPOS	WAPOS	WAPOS	Maintenance item	CHAR	16	Link to MPOS
OBJK	OBKNR	OBJKNR	Object list number	INT8	19	System Key field
OBJK	OBZAE	OBJZA	Object list counters	INT4	10	System Key field
OBJK	SORTF	OBSORT	Object list sort field	CHAR	20	Conditional
OBJK	TPLNR	TPLNR	Functional Location	CHAR	30	Conditional
OBJK	EQUNR	EQUNR	Equipment Number	CHAR	18	Conditional

Note: Each Maintenance Item can have multiple Objects or no Object at all. Not applicable if both Functional Location and Equipment Number are blank.

8.Maintenance Plan (Characteristics Values Header)

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MPLA	WARPL	WARPL	Maintenance Plan	CHAR	12	Link to MPLA
KLAH	KLART	KLASSENART	Class Type	CHAR	3	Mandatory
INOB	OBTAB	TABELLE	Name of Database Table for Object	CHAR	30	Mandatory
KLAH	CLASS	KLASSE_D	Class number	CHAR	18	Mandatory
INOB	OBJEK	CUOBN	Key of Object	CHAR	90	Mandatory
KLAH	STATU	KLSTATUS	Class Status	CHAR	1	Mandatory

9.Maintenance Plan (Characteristics Values Allocation)

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MPLA	WARPL	WARPL	Maintenance Plan	CHAR	12	Link to MPLA
KLAH	KLART	KLASSENART	Class Type	CHAR	3	Mandatory
INOB	OBTAB	TABELLE	Name of Database Table for Object	CHAR	30	Mandatory
KLAH	CLASS	KLASSE_D	Class number	CHAR	18	Mandatory
INOB	OBJEK	CUOBN	Key of Object	CHAR	90	Mandatory
CABN	ATNAM	ATNAM	Characteristic Name	CHAR	30	Mandatory
AUSP	ATWRT	ATWRT	Characteristic Value	CHAR	30	Mandatory
KSML	POSNR	KPOSNR	Item Number	CHAR	3	Mandatory

Maintenance Plan and Item Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Maintenance Plan information follows the Master Data Standard document that is located here.

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1016-001	C3	Info Report: Maintenance Item: Assigned Equipment is not Active. These Maintenance Items are not relevant for migration.	Maintenance Plan with Maintenance Item assigned with an Equipment that belong to the criteria below: Equipment (Source System Status (JEST-STAT) and </Start CR0438> (JEST-INAC <> 'X') </End CR0438> is any of these: INAC ESTO AVLB)	Maintenance Plan, Description, Maintenance Item, Item Short Text, Plant, Equipment	PF2, WP2
1016-002	C3	Info Report: Maintenance Item: Assigned Functional Location is not Active. These Maintenance Items are not relevant for migration.	Maintenance Plan with Maintenance Item assigned with a Functional Location belong to the criteria below: Functional Location (Source System Status (JEST-STAT) and </Start CR0438> (JEST-INAC <> 'X') </End CR0438> is any of these: INAC DLFL)	Maintenance Plan, Description, Maintenance Item, Item Short Text, Plant, Functional Location	PF2, WP2
1016-003	C3	Info Report: Maintenance Item: Assigned Task List is not Active. These Maintenance Items are not relevant for migration.	Maintenance Plan with Maintenance Item assigned with a Task List does not belong to the criteria below: Task List Type (PLKO-PLNTY) can be any of: A - General Maintenance Task List; E - Equipment Task List; T - Task List for Functional Location Task List Status (PLKO-STATU) can be any of: 2 - Released for Order; 3 - Released for Costing; 4 - Released (General) Task List Usage (PLKO-VERWE) = "004"	Maintenance Plan, Description, Maintenance Item, Item Short Text, Plant, Task List	PF2, WP2
1016-004	C2	Maintenance Plan: Duplicate Maintenance Plan by Technical Object	Maintenance Plan and Items as per Relevancy Criteria where there is more than Maintenance Plan assigned to the same Technical Object	Maintenance Plan, Description, Maintenance Item, Item Short Text, Plant, Functional Location, Equipment	PF2, WP2
1016-005	C1	Maintenance Item-Priority: is blank	Maintenance Plan and Items as per Relevancy Criteria where the Priority is blank	Maintenance Plan, Description, Maintenance Item, Item Short Text, Plant, Priority	PF2, WP2
1016-006	C1	Maintenance Plan-Sort field: is blank	Maintenance Plan and Items as per Relevancy Criteria where the Sort field is blank	Maintenance Plan, Description, Maintenance Item, Item Short Text, Plant, Sort field	PF2, WP2
1016-007	C2	Maintenance Plan-Description: Informally deleted	Maintenance Plan and Items as per Relevancy Criteria where Description contains: DELETE DEL	Maintenance Plan, Description	PF2, WP2
1016-008	C3	Info Report: Maintenance Plan: Long Text for cleansing	Long Text for Manual Review. Note: This is used to create Inclusion-Maintenance Plan Long Text* . Business will then select which Long Text are still relevant from Inclusion-Maintenance Plan Long Text.*	Maintenance Plan, Description, Rownum, Long Text	PF2, WP2
1016-009	C3	Info Report: Maintenance Item: Long Text for cleansing	Long Text for Manual Review. Note: This is used to create Inclusion-Maintenance Item Long Text* . Business will then select which Long Text are still relevant from Inclusion-Maintenance Item Long Text.*	Maintenance Item, Description, Plant, Rownum, Long Text	PF2, WP2
1016-010	C2	Maintenance Items assigned to assembly only	Maintenance Items assigned to assembly with no Functional Location or Equipment assigned. Note: This is a list of Maintenance Items for business to create in DCT as enrichment activity.	Maintenance Item, Description, Plant	PF2, WP2
1016-011	Not Applicable	External Cleansing Report: Maintenance Plan not in SAP	Business to create the Maintenance Plans in legacy as part of this cleansing activity. Note: This will be a business-led cleansing activity to be executed as part of the SyWay process. No report development by ADMM	Not Applicable	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 diagram below:

Image Added

Collection will be done manually in the Data Collection Template for the following scenarios:

For sites not on SAP-PF2 or WP2 systems

The high-level process for DCT is represented by the diagram below:

Image Added

Data Privacy and Sensitivity

Not Applicable

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate 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 Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads.

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from source system based on relevancy rule	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 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 Data Construction Rules

Field Name	Field Description	Rule
zLegacyWARPL	Legacy Maintenance Plan	Mandatory. Key field
STRAT	Maintenance strategy	Mandatory. Must reference Strategy in Maintenance Strategy DCT. Must be the same strategy as the Task List strategy.
TOPOS	Tolerance for Late Completion (%)	Conditional. Numeric values only, values from 0 to 100 Note: Will default to "10" if blank
TONEG	Tolerance for Early Completion (%)	Conditional. Numeric values only, values from 0 to 100 Note: Will default to "10" if blank
SFAKT	Cycle modification factor	Conditional. Note: Will default to "1" if blank
FABKL	Time-factory caldr	Conditional. Select from configuration (TFACD)
HORIZ	Call horizon for maintenance plan calls	Mandatory. Numeric values only, values from 0 to 100 Note: Will default to "100" if blank
ABRHO	Scheduling Period	Mandatory. Note: Will default to "3" if blank
HUNIT	Unit for Scheduling Period	Mandatory. Note: Will default to "YR" if blank
CALL_CONFIRM	Completion Requirement	Conditional. Allowed values: "X" - checked blank - unchecked
STADT	Start date	Conditional. All Date format should be DDMMYYYY
STICH	Scheduling indicator	Conditional. If first 2 Chars of the Strategy <> " 02" (Performance-Based Strategy) then the allowed values: blank - Time "1" - Time - key date "2" - Time - factory calendar If the first 2 Chars of the Strategy = "02" (Performance-Based Strategy) then allowed value: "3" - Performance-based
PLAN_SORT	Sort field for maintenance plans	Mandatory. Select from configuration (T399G) Note: Group Maintenance Plans based on below design principal: Frequency + Maintenance Activity Each group (Sort Field) gets its own deadline monitoring variant. Example: 6M_INSP: Monthly Inspection All Maintenance Plans of Inspection for 6M Inspection will be grouped with this Sort field.
POINT	Measuring Point	Conditional. Must reference Measuring Point DCT. Must not be blank if the first 2 Chars of the Strategy = "02" (Performance-Based Strategy) Must be blank if the first 2 Chars of the Strategy <> " 02" (Performance-Based Strategy)
ENDDT_FOR_SCHED	End Date for Scheduling	Conditional. All Date format should be DDMMYYYY. Can be blank Note: End Date must always be later than Start date
CHAR_DISCRETE_TO_ASSET	Discrete to the Asset Characteristic	Mandatory. Allowed values: "YES" or "NO" Note: Will default to "NO" in left blank

2.Maintenance Plan Long Text Line Data Construction Rules

Field Name	Field Description	Rule
zLegacyWARPL	Legacy Maintenance Plan	Mandatory. Key to link to Maintenance Plan
TDSPRAS	Language Key	Mandatory Must be either one of the following: English(E) , French(F), Italian(I), Mandarin(1), Portuguese(including Brazilian Portuguese)(P), German(D) and Spanish(S)
ROWCOUNT	Row number	Mandatory. Must be unique and ascending sequential number
TXLINE	Text Line	Mandatory Free Text

3.Maintenance Item Data Construction Rules

Field Name	Field Description	Rule
zLegacyWARPL	Legacy Maintenance Plan	Mandatory. Key to link to Maintenance Plan
zLegacyWAPOS	Legacy Maintenance Item	Mandatory. Key field
PSTXT	Item Short Text	Mandatory. Free text. Note: Description must be defined as Frequency + TOT + Asset Tag.
TPLNR	Functional Location	Mandatory. Must reference category "A" Functional Location with a CT in Functional Location DCT. Must not be blank if Equipment is blank. CT of Functional Location must match Task List CT
EQUNR	Equipment Number	Conditional. Must reference Equipment Number in Equipment DCT. Must not be blank if Functional Location is blank. CT of the Equipment must match Task List CT
IWERK	Planning Plant	Mandatory. Must reference Value Mapping: Plant (Maintenance Plant = Yes)
GEWRK	Main work center for maintenance tasks	Conditional. Must reference Work Centre DCT. Note: If blank, default to the Work Centre derived from Equipment. If Equipment is blank then default to the Work Centre derived from Functional Location.
WERGW	Plant associated with main work center	Mandatory. Must reference Value Mapping: Plant (Maintenance Plant = Yes)
WPGRP	Maintenance Planner Group	Conditional. Select from configuration (T024I). Note: If blank, default to Planner Group derived from Equipment. If Equipment is blank then default to Planner Group derived from Functional Location.
PRIOK	Priority	Mandatory. Select from configuration (T356).
PLNNR	Key for Task List Group	Mandatory. Key for Task List Group + Group Counter: Should exist in Task List DCT. Task List CT must be the same as the Technical Object CT. All Maintenance Items under the same Maintenance Plan must be assigned to the same Task List
PLNAL	Group Counter	Mandatory. Key for Task List Group + Group Counter: Should exist in Task List DCT. Task List CT must be the same as the Technical Object CT. All Maintenance Items under the same Maintenance Plan must be assigned to the same Task List
APFKT	Execution factor for whole task list	Conditional. Note: Will default to to "1" if blank
ANLZU	System Condition	Conditional. Select from configuration (T357M) or can be blank
ILART	Maintenance Activity Type	Select from configuration (T353I) Note: The Maintenance Activity Type shall be updated by the business based on the activities defined in the associated Task List of the Maintenance Item.

4.Maintenance Item Long Text Line Data Construction Rules

Field Name	Field Description	Rule
zLegacyWARPL	Legacy Maintenance Plan	Mandatory. Key to link to Maintenance Plan
zLegacyWAPOS	Legacy Maintenance Item	Mandatory. Key to link to Maintenance Item
TDSPRAS	Language Key	Mandatory Must be either one of the following: English(E) , French(F), Italian(I), Mandarin(1), Portuguese(including Brazilian Portuguese)(P), German(D) and Spanish(S)
ROWCOUNT	Row number	Mandatory. Must be unique and ascending sequential number
TXLINE	Text Line	Mandatory Free Text

5.Maintenance Item Object List Data Construction Rules

Field Name	Field Description	Rule
zLegacyWARPL	Legacy Maintenance Plan	Mandatory. Key to link to Maintenance Plan
zLegacyWAPOS	Legacy Maintenance Item	Mandatory. Key field
zOBZAE	Object list counters	Mandatory. Key field
SORTF	Object list sort field	Conditional. Must be unique and ascending sequential number starting from 1
EQUNR	Equipment Number	Conditional. Must reference Equipment Number in Equipment DCT.
TPLNR	Functional Location	Conditional. Must reference category "A" Functional Location with a CT in Functional Location DCT

6.Inclusion-Maintenance Plan Long Text Data Construction Rules

Field Name

Field Description

Rule

zLegacyWARPL

Legacy Maintenance Plan

Mandatory.

Key to link to Maintenance Plan

zLegacySPRAS

Legacy Language Key

Mandatory.

Allowed values:
1. "E" - English
2. "F" - French
3. "1" - Mandarin/Simplified Chinese
4. "I' - Italian
5. "P" - Portuguese/Brazilian
6. "D" - German
7. "S" - Spanish

zLegacyWERKS

Legacy Plant

Mandatory

Note: Only Long Texts that are this list will be migrated.

7.Inclusion-Maintenance Item Long Text Data Construction Rules

Field Name

Field Description

Rule

zLegacyWAPOS

Legacy Maintenance Plan

Mandatory.

Key to link to Maintenance Item

zLegacySPRAS

Legacy Language Key

Mandatory.

Allowed values:
1. "E" - English
2. "F" - French
3. "1" - Mandarin/Simplified Chinese
4. "I' - Italian
5. "P" - Portuguese/Brazilian
6. "D" - German
7. "S" - Spanish

zLegacyWERKS

Legacy Plant

Mandatory

Note: Only Long Texts that are this list will be migrated.

Note: List of DCTs is maintained here: Conversion Specs Register (DCT & Cleansing Report)

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Relevancy Criteria for Equipment	SyWay A2D Data Team
2	Relevancy Criteria for Functional Location	SyWay A2D Data Team
3	Relevancy Criteria for Task List	SyWay A2D 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 to make the data Target ready:

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
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 A2D 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 and Item	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	Generate load files	Syniti

Transformation Rules

1.Maintenance Plan Transformation Rule (ECC)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2, WP2	MPLA	WARPL	Maintenance Plan	S/4HANA	MPLA	WARPL	Maintenance Plan	System (Internal numbering)
2	-	-	-	-	S/4HANA	MPLA	MPTYP	Maintenance plan category	Default to "PM"
3	PF2, WP2	MPLA	STRAT	Maintenance Strategy	S/4HANA	MPLA	STRAT	Maintenance Strategy	Value Mapping: Maintenance Strategy
4	PF2, WP2	PLKO	KTEXT	Description	S/4HANA	MPLA	WPTXT	Maintenance Plan Text	Direct mapping
5	-	-	-	-	S/4HANA	MPLA	VSPOS	Shift Factor for Late Completion	Default to 0 if Time based Maintenance Plan. Default to 100 if Performance based Maintenance Plan. Refer to the Notes below for definition of Time-Based and Performance-Based Strategy
6	PF2, WP2	MPLA	TOPOS	Tolerance for Late Completion (%)	S/4HANA	MPLA	TOPOS	Tolerance for Late Completion (%)	Direct mapping. If blank, default to "10"
7	-	-	-	-	S/4HANA	MPLA	VSNEG	Shift Factor for Early Completion	Default to 0 if Time based Maintenance Plan. Default to 100 if Performance based Maintenance Plan. Refer to the Notes below for definition of Time-Based and Performance-Based Strategy
8	PF2, WP2	MPLA	TONEG	Tolerance for Early Completion (%)	S/4HANA	MPLA	TONEG	Tolerance for Early Completion (%)	Direct mapping. If blank, default to "10"
9	PF2, WP2	MPLA	SFAKT	Cycle modification factor	S/4HANA	MPLA	SFAKT	Cycle modification factor	Direct mapping. If blank, default to "1"
10	PF2, WP2	MPLA	FABKL	Factory calendar key	S/4HANA	MPLA	FABKL	Factory calendar key	If STICH = "1" or "2" then Value Mapping: Factory Calendar Definition, otherwise default to blank
11	PF2, WP2	MPLA	HORIZ	Call horizon for maintenance plan calls	S/4HANA	MPLA	HORIZ	Call horizon for maintenance plan calls	Direct mapping. If blank, default to "100"
12	-	-	-	-	S/4HANA	MPLA	HORIZ_QUALIFIER	Calculation Type of Call Horizon	Default to "%"
13	PF2, WP2	MPLA	ABRHO	Scheduling Period	S/4HANA	MPLA	ABRHO	Scheduling Period	Direct mapping. If blank, default to "3"
14	PF2, WP2	MPLA	HUNIT	Unit for Scheduling period	S/4HANA	MPLA	HUNIT	Unit for Scheduling period	Direct mapping. If blank, default to "YR"
15	PF2, WP2	MPLA	CALL_CONFIRM	Completion Requirement	S/4HANA	MPLA	CALL_CONFIRM	Completion Requirement	Direct mapping.
16	PF2, WP2	MPLA	STADT	Start date	S/4HANA	MPLA	STADT	Start date	Default to blank
17	PF2, WP2	MPLA	STICH	Scheduling indicator	S/4HANA	MPLA	STICH	Scheduling indicator	Direct Mapping. Default to "3" if Performance based Maintenance Plan. Refer to the Notes below for definition of Time-Based and Performance-Based Strategy
18	PF2, WP2	MPLA	PLAN_SORT	Sort field for maintenance plans	S/4HANA	MPLA	PLAN_SORT	Sort field for maintenance plans	Value Mapping: Maintenance Plan Sort Field
19	PF2, WP2	RMIPM	POINT	Measuring Point	S/4HANA	RMIPM	POINT	Measuring Point	Value Mapping: Measuring Point
20	PF2, WP2	MPLA	ENDDT_FOR_SCHED	End Date for Scheduling	S/4HANA	MPLA	ENDDT_FOR_SCHED	End Date for Scheduling	Direct Mapping

Notes:

If STICH = blank, 1 or 2 then Strategy is Time-Based
If STICH 3 then Strategy is Performance-Based

2.Maintenance Plan Transformation Rule (DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	S/4HANA	MPLA	WARPL	Maintenance Plan	System (Internal numbering)
2	-	-	-	-	S/4HANA	MPLA	MPTYP	Maintenance plan category	Default to "PM"
3	DCT	MPLA	STRAT	Maintenance Strategy	S/4HANA	MPLA	STRAT	Maintenance Strategy	Direct mapping.
4	-	-	-	-	S/4HANA	MPLA	WPTXT	Maintenance Plan Text	Derive from assigned Task List Header Description
5	-	-	-	-	S/4HANA	MPLA	VSPOS	Shift Factor for Late Completion	Default to 0 if Time based Maintenance Plan. Default to 100 if Performance based Maintenance Plan. Refer to the Notes below for definition of Time-Based and Performance-Based Strategy
6	DCT	MPLA	TOPOS	Tolerance for Late Completion (%)	S/4HANA	MPLA	TOPOS	Tolerance for Late Completion (%)	Direct mapping. If blank, default to "10"
7	-	-	-	-	S/4HANA	MPLA	VSNEG	Shift Factor for Early Completion	Default to 0 if Time based Maintenance Plan. Default to 100 if Performance based Maintenance Plan. Refer to the Notes below for definition of Time-Based and Performance-Based Strategy
8	DCT	MPLA	TONEG	Tolerance for Early Completion (%)	S/4HANA	MPLA	TONEG	Tolerance for Early Completion (%)	Direct mapping. If blank, default to "10"
9	DCT	MPLA	SFAKT	Cycle modification factor	S/4HANA	MPLA	SFAKT	Cycle modification factor	Direct mapping. If blank, default to "1"
10	DCT	MPLA	FABKL	Factory calendar key	S/4HANA	MPLA	FABKL	Factory calendar key	Direct mapping.
11	DCT	MPLA	HORIZ	Call horizon for maintenance plan calls	S/4HANA	MPLA	HORIZ	Call horizon for maintenance plan calls	Direct mapping. If blank, default to "100"
12	-	-	-	-	S/4HANA	MPLA	HORIZ_QUALIFIER	Calculation Type of Call Horizon	Default to "%"
13	DCT	MPLA	ABRHO	Scheduling Period	S/4HANA	MPLA	ABRHO	Scheduling Period	Direct mapping. If blank, default to "3"
14	DCT	MPLA	HUNIT	Unit for Scheduling period	S/4HANA	MPLA	HUNIT	Unit for Scheduling period	Direct mapping. If blank, default to "YR"
15	DCT	MPLA	CALL_CONFIRM	Completion Requirement	S/4HANA	MPLA	CALL_CONFIRM	Completion Requirement	Direct mapping.
16	DCT	MPLA	STADT	Start date	S/4HANA	MPLA	STADT	Start date	Direct mapping.
17	DCT	MPLA	STICH	Scheduling indicator	S/4HANA	MPLA	STICH	Scheduling indicator	Direct mapping.
18	DCT	MPLA	PLAN_SORT	Sort field for maintenance plans	S/4HANA	MPLA	PLAN_SORT	Sort field for maintenance plans	Direct Mapping
19	DCT	RMIPM	POINT	Measuring Point	S/4HANA	RMIPM	POINT	Measuring Point	Value Mapping: Measuring Point
20	DCT	MPLA	ENDDT_FOR_SCHED	End Date for Scheduling	S/4HANA	MPLA	ENDDT_FOR_SCHED	End Date for Scheduling	Direct Mapping

Notes:

If first 2 Characters of the Strategy <> " 02" then it is Time-Based Strategy
If first 2 Characters of the Strategy = "02" then it is Performance-Based Strategy

3.Maintenance Plan Long Text Header Transformation Rule (ECC)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4HANA	STXL	TDOBJECT	Texts: application object	Default to "MPLA"
2	PF2, WP2	MPLA	WARPL	Maintenance Plan	S/4HANA	STXL	TDNAME	Name	Value Mapping: Maintenance Plan
3	-	-	-	-	S/4HANA	STXL	TDID	Text ID	Default to "LTXT"
4	PF2, WP2	STXL	SPRAS	Language Key	S/4HANA	STXL	SPRAS	Language Key	Direct Mapping

Note: Only the records marked as Cleansed in INC-Maintenance Plan Long Text will be migrated

4.Maintenance Plan Long Text Header Transformation Rule (DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4HANA	STXL	TDOBJECT	Texts: application object	Default to "MPLA"
2	DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	S/4HANA	STXL	TDNAME	Name	Value Mapping: Maintenance Plan
3	-	-	-	-	S/4HANA	STXL	TDID	Text ID	Default to "LTXT"
4	DCT	STXL	SPRAS	Language Key	S/4HANA	STXL	SPRAS	Language Key	Direct Mapping

5.Maintenance Plan Long Text Line Transformation Rule (ECC)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4HANA	STXL	RELID	CHAR02 data element for SYST	Default to "TX"
2	-	-	-	-	S/4HANA	STXL	TDOBJECT	Texts: application object	Default to "MPLA"
3	PF2, WP2	MPLA	WARPL	Maintenance Plan	S/4HANA	STXL	TDNAME	Name	Value Mapping: Maintenance Plan
4	-	-	-	-	-	STXL	TDID	Text ID	Default to "LTXT"
5	PF2, WP2	STXL	SPRAS	Language Key	S/4HANA	STXL	SPRAS	Language Key	Direct Mapping
6	-	-	-	-	S/4HANA	STXL	CLUSTD_TAG	Tag column	Default to "*"
7	PF2, WP2	STXL	ROWCOUNT	Row number	S/4HANA	STXL	ROWCOUNT	Row number	Direct Mapping
8	PF2, WP2	STXL	TXLINE	Text Line	S/4HANA	STXL	TXLINE	Text Line	Direct Mapping

Note: Only the records marked as Cleansed in INC-Maintenance Item Long Text will be migrated

6.Maintenance Plan Long Text Line Transformation Rule (DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4HANA	STXL	RELID	CHAR02 data element for SYST	Default to "TX"
2	-	-	-	-	S/4HANA	STXL	TDOBJECT	Texts: application object	Default to "MPLA"
3	DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	S/4HANA	STXL	TDNAME	Name	Value Mapping: Maintenance Plan
4	-	-	-	-	S/4HANA	STXL	TDID	Text ID	Default to "LTXT"
5	DCT	STXL	SPRAS	Language Key	S/4HANA	STXL	SPRAS	Language Key	Direct Mapping
6	-	-	-	-	S/4HANA	STXL	CLUSTD_TAG	Tag column	Default to "*"
7	DCT	STXL	ROWCOUNT	Row number	S/4HANA	STXL	ROWCOUNT	Row number	Direct Mapping
8	DCT	STXL	TXLINE	Text Line	S/4HANA	STXL	TXLINE	Text Line	Direct Mapping

7.Maintenance Item Transformation Rule (ECC)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2, WP2	MPOS	WAPOS	Maintenance Item	S/4HANA	MPOS	WAPOS	Maintenance Item	System (Internal numbering)
2	PF2, WP2	MPOS	WARPL	Maintenance Plan	S/4HANA	MPLA	WARPL	Legacy Maintenance Plan	Value Mapping: Maintenance Plan
3	PF2, WP2	MPOS	PSTXT	Item Short Text	S/4HANA	MPOS	PSTXT	Item Short Text	Direct mapping
4	PF2, WP2	MPOS	TPLNR	Functional Location	S/4HANA	MPOS	TPLNR	Functional Location	Value Mapping: Functional Location
5	PF2, WP2	MPOS	TPLNR	Functional Location	S/4HANA	MPOS	EQUNR	Equipment Number	Value Mapping: Functional Location where New Equipment is not blank
6	PF2, WP2	MPOS	EQUNR	Equipment Number	S/4HANA	MPOS	EQUNR	Equipment Number	Value Mapping: Equipment Number
7	PF2, WP2	MPOS	IWERK	Planning Plant	S/4HANA	MPOS	IWERK	Planning Plant	Value Mapping: Plant (Maintenance Plant = Yes)
8	PF2, WP2	MPOS	AUART	Order Type	S/4HANA	MPOS	AUART	Order Type	Default to "YA02"
9	PF2, WP2	MPOS	GEWRK	Main work center for maintenance tasks	S/4HANA	MPOS	GEWRK	Main work center for maintenance tasks	Value Mapping: Work Centre If blank then: 1. default to Work Centre derived from Equipment 2. If Equipment is blank then default to the Work Centre derived from Functional Location
10	PF2, WP2	CRHD	WERKS	Plant	S/4HANA	RMIPM	WERGW	Plant associated with main work center	Value Mapping: Plant (Maintenance Plant = Yes)
11	PF2, WP2	MPOS	WPGRP	Maintenance Planner Group	S/4HANA	MPOS	WPGRP	Maintenance Planner Group	Value Mapping: Maintenance Planner Group If blank then: 1. default to Planner Group derived from Equipment 2. If Equipment is blank then default to the Planner Group derived from Functional Location
12	PF2, WP2	MPOS	PRIOK	Priority	S/4HANA	MPOS	PRIOK	Priority	Value Mapping: Priority
13	PF2, WP2	MPOS	PLNTY	Task List Type	S/4HANA	MPOS	PLNTY	Task List Type	Value Mapping: Task List Header
14	PF2, WP2	MPOS	PLNNR	Key for Task List Group	S/4HANA	MPOS	PLNNR	Key for Task List Group	Value Mapping: Task List Header
15	PF2, WP2	MPOS	PLNAL	Group Counter	S/4HANA	MPOS	PLNAL	Group Counter	Value Mapping: Task List Header
16	PF2, WP2	MPOS	APFKT	Execution factor for whole task list	S/4HANA	MPOS	APFKT	Execution factor for whole task list	Direct mapping. If blank, default to "1"
17	PF2, WP2	MPOS	ANLZU	System Condition	S/4HANA	MPOS	ANLZU	System Condition	Value Mapping: System Condition
18	DCT	MPOS	ILART	Maintenance Activity Type	S/4HANA	MPOS	ILART	Maintenance Activity Type	Direct mapping from DCT (as part of enrichment)

8.Maintenance Item Transformation Rule (DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	MPOS	zLegacyWAPOS	Legacy Maintenance Item	S/4HANA	MPOS	WAPOS	Maintenance Item	System (Internal numbering)
2	DCT	MPOS	zLegacyWARPL	Legacy Maintenance Plan	S/4HANA	MPLA	WARPL	Maintenance Plan	Value Mapping: Maintenance Plan
3	DCT	MPOS	PSTXT	Item Short Text	S/4HANA	MPOS	PSTXT	Item Short Text	Direct Mapping
4	DCT	MPOS	TPLNR	Functional Location	S/4HANA	MPOS	TPLNR	Functional Location	Direct Mapping
5	DCT	MPOS	EQUNR	Equipment Number	S/4HANA	MPOS	EQUNR	Equipment Number	Value Mapping: Equipment Number
6	DCT	MPOS	IWERK	Planning Plant	S/4HANA	MPOS	IWERK	Planning Plant	Direct Mapping
7	-	-	-	-	-	MPOS	AUART	Order Type	Default to "YA02"
8	DCT	MPOS	GEWRK	Main work centre for maintenance tasks	S/4HANA	MPOS	GEWRK	Main work centre for maintenance tasks	Direct Mapping. If blank then: 1. default to Work Centre derived from Equipment 2. If Equipment is blank then default to the Work Centre derived from Functional Location
9	DCT	MPOS	WERGW	Plant associated with main work center	S/4HANA	RMIPM	WERGW	Plant associated with main work center	Direct Mapping
10	DCT	MPOS	PRIOK	Priority	S/4HANA	MPOS	PRIOK	Priority	Direct Mapping
11	DCT	MPOS	WPGRP	Maintenance Planner Group	S/4HANA	MPOS	WPGRP	Maintenance Planner Group	Direct Mapping. If blank then: 1. default to Planner Group derived from Equipment 2. If Equipment is blank then default to the Planner Group derived from Functional Location
12	DCT	MPOS	PLNTY	Task List Type	S/4HANA	MPOS	PLNTY	Task List Type	Value Mapping: Task List Header
13	DCT	MPOS	PLNNR	Key for Task List Group	S/4HANA	MPOS	PLNNR	Key for Task List Group	Value Mapping: Task List Header
14	DCT	MPOS	PLNAL	Group Counter	S/4HANA	MPOS	PLNAL	Group Counter	Value Mapping: Task List Header
15	DCT	MPOS	APFKT	Execution factor for whole task list	S/4HANA	MPOS	APFKT	Execution factor for whole task list	Direct Mapping. If blank, default to "1"
16	DCT	MPOS	ANLZU	System Condition	S/4HANA	MPOS	ANLZU	System Condition	Direct Mapping.
17	DCT	MPOS	ILART	Maintenance Activity Type	S/4HANA	MPOS	ILART	Maintenance Activity Type	Direct Mapping

9.Maintenance Item Object List Transformation Rule (ECC)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2, WP2	MPOS	zLegacyWAPOS	Legacy Maintenance Item	-	-	-	-	Value Mapping: Maintenance Plan Note: This will be used as part of pre-load report
2	-	-	-	-	S/4HANA	OBJK	OBKNR	Object list number	System (Internal numbering)
3	-	-	-	-	S/4HANA	OBJK	OBZAE	Object list counters	System (Internal numbering)
4	-	-	-	-	S/4HANA	OBJK	ILOAN	Location and account assignment for technical object	System (Internal numbering)
5	PF2, WP2	OBJK	SORTF	Object list sort field	S/4HANA	OBJK	SORTF	Object list sort field	Direct Mapping.
6	PF2, WP2	OBJK	TPLNR	Functional Location	S/4HANA	OBJK	TPLNR	Functional Location	Value Mapping: Functional Location
7	PF2, WP2	OBJK	TPLNR	Functional Location	S/4HANA	OBJK	EQUNR	Equipment Number	Value Mapping: Functional Location where New Equipment is not blank
8	PF2, WP2	OBJK	EQUNR	Equipment Number	S/4HANA	OBJK	EQUNR	Equipment Number	Value Mapping: Equipment Number

10.Maintenance Item Object List Transformation Rule (DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	MPOS	zLegacyWAPOS	Legacy Maintenance Item	-	-	-	-	Value Mapping: Maintenance Plan Note: This will be used as part of pre-load report
2	-	-	-	-	-	OBJK	OBKNR	Object list number	System (Internal numbering)
3	-	-	-	-	-	OBJK	OBZAE	Object list counters	System (Internal numbering)
4	-	-	-	-	-	OBJK	ILOAN	Location and account assignment for technical object	System (Internal numbering)
5	DCT	OBJK	SORTF	Object list sort field	S/4HANA	OBJK	SORTF	Object list sort field	Direct Mapping.
6	DCT	OBJK	TPLNR	Functional Location	S/4HANA	OBJK	TPLNR	Functional Location	Direct Mapping.
7	DCT	OBJK	EQUNR	Equipment Number	S/4HANA	OBJK	EQUNR	Equipment Number	Value Mapping: Equipment Number

11.Maintenance Plan (Characteristics Values Header) (ECC and DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2, WP2	MPLA	zLegacyWARPL	Legacy Maintenance Plan	-	-	-	-	Value Mapping: Maintenance Plan Note: This will be used as part of pre-load report
2	-	-	-	-	S/4HANA	KLAH	KLART	Class Type	Default to "080"
3	-	-	-	-	S/4HANA	INOB	OBTAB	Name of Database Table for Object	Default to "MPLA"
4	-	-	-	-	S/4HANA	KLAH	CLASS	Class number	Default to "EAM_9999"
5	-	-	-	-	S/4HANA	INOB	OBJEK	Key of Object	Value Mapping: Maintenance Plan Note: Use mapping table Maintenance Plan to get New Object Number (OBJNR)
6	-	-	-	-	S/4HANA	KLAH	STATU	Class Status	Default to "1"

12.Maintenance Plan (Default Characteristics Values Allocation - Allowed CT) (ECC and DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2, WP2, DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	-	-	-	-	Value Mapping: Maintenance Plan Note: This will be used as part of pre-load report
2	-	-	-	-	S/4HANA	KLAH	KLART	Class Type	Default to "018"
3	-	-	-	-	S/4HANA	INOB	OBTAB	Name of Database Table for Object	Default to "MPLA"
4	-	-	-	-	S/4HANA	KLAH	CLASS	Class number	Default to "EAM_9999"
5	PF2, WP2, DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	S/4HANA	INOB	OBJEK	Key of Object	Value Mapping: Maintenance Plan. Note: Use mapping table Maintenance Plan to get New Object Number (OBJNR)
6	-	-	-	-	S/4HANA	CABN	ATNAM	Characteristic Name	Value Mapping: Characteristic A2D where ATNAM = "A_ALLOWED_CT"
7	-	-	-	-	S/4HANA	AUSP	ATWRT	Characteristic Value	If A_DISCRETE_TO_ASSET = "YES" then blank. If A_DISCRETE_TO_ASSET = "NO" then 1. default to CT derived from Equipment 2. If Equipment is blank then default to the CT derived from Functional Location
8	-	-	-	-	S/4HANA	KSML	POSNR	Item Number	Default to "001'

Note: Each Maintenance Plan can have only 1 Allowed CT characteristic

13.Maintenance Plan (Default Characteristics Values Allocation - Discrete to the Asset) (ECC and DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2, WP2, DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	-	-	-	-	Value Mapping: Maintenance Plan Note: This will be used as part of pre-load report
2	-	-	-	-	S/4HANA	KLAH	KLART	Class Type	Default to "018"
3	-	-	-	-	S/4HANA	INOB	OBTAB	Name of Database Table for Object	Default to "MPLA"
4	-	-	-	-	S/4HANA	KLAH	CLASS	Class number	Default to "EAM_9999"
5	PF2, WP2, DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	S/4HANA	INOB	OBJEK	Key of Object	Value Mapping: Maintenance Plan. Note: Use mapping table Maintenance Plan to get New Object Number (OBJNR)
6	-	-	-	-	S/4HANA	CABN	ATNAM	Characteristic Name	Value Mapping: Characteristic A2D where ATNAM = "A_DISCRETE_TO_ASSET"
7	DCT	-	CHAR_DISCRETE_TO_ASSET	Discrete to the Asset Characteristic	S/4HANA	AUSP	ATWRT	Characteristic Value	Direct Mapping from DCT (as part of enrichment) If not "YES" then default to "NO"
8	-	-	-	-	S/4HANA	KSML	POSNR	Item Number	Default to "001"

Note: Each Maintenance Plan can have only 1 Discrete to the Assetcharacteristic

14.Maintenance Plan (Default Characteristics Values Allocation - Regulatory) (ECC and DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2, WP2, DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	-	-	-	-	Value Mapping: Maintenance Plan Note: This will be used as part of pre-load report
2	-	-	-	-	S/4HANA	KLAH	KLART	Class Type	Default to "018"
3	-	-	-	-	S/4HANA	INOB	OBTAB	Name of Database Table for Object	Default to "MPLA"
4	-	-	-	-	S/4HANA	KLAH	CLASS	Class number	Default to "EAM_9999"
5	PF2, WP2, DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	S/4HANA	INOB	OBJEK	Key of Object	Value Mapping: Maintenance Plan. Note: Use mapping table Maintenance Plan to get New Object Number (OBJNR)
6	-	-	-	-	S/4HANA	CABN	ATNAM	Characteristic Name	Value Mapping: Characteristic A2D where ATNAM = "A_REGULATORY"
7	-	-	-	-	S/4HANA	AUSP	ATWRT	Characteristic Value	Derive from Task List Header Data Construction "A_REGULATORY" Characteristic Value
8	-	-	-	-	S/4HANA	KSML	POSNR	Item Number	Default to "001"

Note:

Each Maintenance Plan can have only 1 Regulatory characteristic
To link Maintenance Plan to Task List Header Data Construction, join MPOS-PLNTY, MPOS-PLNNR, MPOS-PLNAL to PLKO-PLNTY, PLKO-PLNNR, PLKO-PLNAL

15.Maintenance Plan (Default Characteristics Values Allocation - Nature of Work) (ECC and DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2, WP2, DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	-	-	-	-	Value Mapping: Maintenance Plan Note: This will be used as part of pre-load report
2	-	-	-	-	S/4HANA	KLAH	KLART	Class Type	Default to "018"
3	-	-	-	-	S/4HANA	INOB	OBTAB	Name of Database Table for Object	Default to "MPLA"
4	-	-	-	-	S/4HANA	KLAH	CLASS	Class number	Default to "EAM_9999"
5	PF2, WP2, DCT	MPLA	zLegacyWARPL	Legacy Maintenance Plan	S/4HANA	INOB	OBJEK	Key of Object	Value Mapping: Maintenance Plan. Note: Use mapping table Maintenance Plan to get New Object Number (OBJNR)
6	-	-	-	-	S/4HANA	CABN	ATNAM	Characteristic Name	Value Mapping: Characteristic A2D where ATNAM = "A_NATURE_OF_WORK"
7	-	-	-	-	S/4HANA	AUSP	ATWRT	Characteristic Value	Derive from Task List Header Data Construction "A_NATURE_OF_WORK" Characteristic Value
8	-	-	-	-	S/4HANA	KSML	POSNR	Item Number	Default to "001"

Note:

Each Maintenance Plan can have only 1 Nature of Work characteristic
To link Maintenance Plan to Task List Header Data Construction, join MPOS-PLNTY, MPOS-PLNNR, MPOS-PLNAL to PLKO-PLNTY, PLKO-PLNNR, PLKO-PLNAL

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

Transformation Mapping

Mapping Table Name	Mapping Table Description
Maintenance Plan	Old to new Maintenance Plan
Maintenance Item	Old to new Maintenance Item
Maintenance Strategy	Old to new Maintenance Strategy
Functional Location	Old to new Functional Location
Equipment Number	Old to new Equipment Number
Material Number	Old to new Material Number
Task List Header	Old to new Task List Header
Measuring Point	Old to new Measuring Point
Work Centre	Old to new Work Centre
Maintenance Plan Sort Field	Old to new Maintenance Plan Sort Field
Priority	Old to new Priority
Order Type	Old to new Order Type
System Condition	Old to new System Condition
Maintenance Planner Group	Old to new Maintenance Planner Group

List of Transformation Mappings with additional details is maintained here: Transformation Mappings

Target Design

Task List Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Maintenance plan and item information follows the Master Data Standard document that is located here

Google Drive Live Link

url	https://docs.google.com/spreadsheets/d/17vm5-ay0BnU7K9v2YT5Kls1fFS1u9Nvs/edit?gid=273892188#gid=273892188&fvid=807014431

.
The technical design of the target for this conversion approach.
TableFieldData ElementField DescriptionData TypeLengthRequirementMPLAWARPLWARPLMaintenance PlanCHAR12SMPLAMPTYPMPTYPMaintenance plan categoryCHAR2RMPLASTRATSTRATMaintenance strategyCHAR6RRMIPMMEHRFACH_ZMEHRFACH_ZMultiple counter planCHAR1NURMIPMWSETWSETCycle set for multiple counter planCHAR6NUMPLAWPTXTWPTXTMaintenance Plan TextCHAR40RMPLAVSPOSVERSCHPLUSNUMC3CMPLATOPOSTOLERPLUSTolerance for Late Completion (%)NUMC3CMPLATONEGTOLERNEGTolerance for Early Completion (%)NUMC3CMPLAVSNEGVERSCHNEGShift Factor for Early CompletionNUMC3CMPLASFAKTSFAKTCycle modification factorDEC3(2)CMPLAFABKLFABKLFactory calendar keyCHAR2NUMPLAHORIZHORIZONTCall horizon for maintenance plan callsNUMC3RMPLAHORIZ_QUALIFIEREAM_CC_CALLHORIZON_QUALIFIERCalculation Type of Call HorizonCHAR1RMPLAABRHOABRHOScheduling PeriodNUMC3RMPLAHUNITHUNITUnit in scheduling intervalUNIT3CMPLACALL_CONFIRMCALL_CONFIRMOnly Create New Call Object After Completing PredecessorCHAR1CMPLASTADTSTADTStart dateDATS8CRMIPMZEITTIME_KNZIndicator for selection of time-based maintenanceCHAR1CMPLASTICHTERMKNZScheduling indicatorCHAR1CMPLAPLAN_SORTPLAN_SORTSort field for maintenance plansCHAR20RMPLABEGRUIAUTGTechnical object authorization groupCHAR4NURMIPMSTTAGMP_STTAGKey DateDATS8CMPLAENDDT_FOR_SCHEDEAM_ENDDT_FOR_SCHEDEnd Date for SchedulingDATS8(0)CMPOSWAPOSWAPOSMaintenance itemCHAR16(0)SMPOSPSTXTPOSTXTItem Short TextCHAR40(0)RMPLATPLNRTPLNRFunctional LocationCHAR30RMPLAEQUNREQUNREquipment NumberCHAR18CMPOSBAUTLBAUTLAssemblyCHAR40(0)NUMPOSIWERKIWERKMaintenance Planning PlantCHAR4(0)SMPOSAUARTAUFARTOrder TypeCHAR4(0)RRMIPMGEWERKGEWRKMain work center for maintenance tasksCHAR8SRMIPMWERGWWERGWPlant associated with main work centerCHAR4SMPOSPRIOKPRIOKPriorityCHAR1(0)RMPOSGSBERGSBERBusiness AreaCHAR4(0)NUMPOSPLNTYPLNTYTask List TypeCHAR1(0)RMPOSPLNNRPLNNRKey for Task List GroupCHAR8(0)RMPOSPLNALPLNALGroup CounterCHAR2(0)RMPOSWPGRPINGRPPlanner Group for Customer Service and Plant MaintenanceCHAR3(waiting for confirmation in MDS)MPOSAPFKTAPFKTExecution factor for whole task listDEC3(0)CMPOSANLZUANLZUSystem ConditionCHAR1(0)CMPOSSERIALNRGERNRSerial NumberCHAR18NUMPOSSERMATMATNRMaterial NumberCHAR40(0)NURMIPMOFFS1WOFFS1Maintenance package offsetCHAR22NURMIPMPAK_TEXTTXZYKLUSText for maintenance package/cycle (time/performance)CHAR30NUMMPTPOINTIMRC_POINTMeasuring PointCHAR12CMMPTZYKL1DZYK_ZEITMaintenance package cycle/offsetFLTP16(16)SMMPTZEIEHDZEIEHUnit for the performance of maintenance tasksUNIT3SMITEM_OBJLIST_DEQUIPMENTEQUNREquipment NumberCHAR18(0)CMITEM_OBJLIST_DFUNCTIONALLOCATIONFunctional locationTPLNR_UNCONVERTEDCHAR30(0)C
Data Cleansing
Work Order Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Class information follows the Master Data Standard document that is located here <include hyperlink>.
IDCriticalityError Message/Report DescriptionRuleOutputSource System
1016-001
C1
Invalid, Inactive or no maintenance item attached to Maintenance Plan
Maintenance Plan as per Relevancy Criteria assigned with inactive or no Maintenance Items attached.
Maintenance Item
PF2, WP2
1016-002
C1
Invalid, Inactive or no Task List allocated to Maintenance Plan
Maintenance Plan as per Relevancy Criteria assigned with a Task List which does not belong below:
1. Task List as per Relevancy Criteria
Task List
PF2, WP2
1016-003
C2
Active maintenance plans not triggered
TBD
Maintenance Plan Status
PF2, WP2
1016-004
C3
Duplicate Maintenance Plan Items by Technical Object, Task List, Strategy, Description
Maintenance Plan Items as per Relevancy Criteria where there is more than one Technical Object + Task List + Strategy + Description Combination.
Technical Object, Task List, Strategy, Description
PF2, WP2
1016-005
C1
Invalid, Inactive or no Characteristic allocated to Maintenance Plan
Maintenance Plan as per Relevancy Criteria assigned with a Characteristic which does not belong below:
1. Characteristic as per Relevancy Criteria
Characteristic
PF2, WP2
1016-006
C1
Invalid, Inactive or no Class allocated to Maintenance Plan
Maintenance Plan as per Relevancy Criteria assigned with a Class which does not belong below:
1. Class as per Relevancy Criteria
Class
PF2, WP2
1016-007
C1
Invalid, Inactive or no Equipment or Functional Location allocated to Maintenance Plan
Maintenance Plan as per Relevancy Criteria assigned with an Equipment or Functional Location which does not belong below:
1. Equipment as per Relevancy Criteria
2. Functional Location as per Relevancy Criteria
Equipment, Functional Location
PF2, WP2
1016-008
C1
Invalid, Inactive or no Maintenance Strategy allocated to Maintenance Plan
Maintenance Plan as per Relevancy Criteria assigned with a Maintenance Strategy which does not belong below:
1. Maintenance Strategy as per Relevancy Criteria
Maintenance Strategy
PF2, WP2
1016-009
C1
Invalid, Inactive or no Work Centres linked to Maintenance Plans
Maintenance Plan as per Relevancy Criteria assigned with a Work Centre which does not belong below:
1. Work Centre as per Relevancy Criteria
Work Centre
PF2, WP2
1016-010
C1
Invalid, Inactive or no Maintenance Plans linked to Maintenance Items
Maintenance Item as per Relevancy Criteria assigned with no or inactive Maintenance Plan attached.
Maintenance Plan
PF2, WP2
1016-011
C1
Invalid or Inactive Measuring Point linked to Maintenance Plan
Maintenance Plan as per Relevancy Criteria assigned with a Measuring Point which does not belong below:
1. Measuring Point as per Relevancy Criteria
Measuring Point
PF2, WP2
1016-012
C1
Missing Maintenance Plan Descriptions
Task List as per Relevancy Criteria where there are blank Task ListDescriptions.
Maintenance Plan Description
PF2, WP2
1016-013
C2
Maintenance Plan Descriptions with Informal Words
Maintenance Plan as per Relevancy Criteria which contain [Informal Words] in the Maintenance Plan Description
Maintenance Plan Description
PF2, WP2
1016-014
C1
Maintenance Plan and Item Plant incorrect.
Maintenance Plan and Item as per Relevancy Criteria with Invalid Plant (T001W)
Plant
PF2, WP2
1016-015
C1
Maintenance Plan and Item UOM Missing / incorrect.
Maintenance Plan and Item as per Relevancy Criteria with no UoM Assigned or Invalid UoM (T006)
Unit of Measure
PF2, WP2
1016-016
C1
Invalid or no Planner Group linked to Maintenance Plan and Item
Maintenance Plan and Item as per Relevancy Criteria with no Planner Group Assigned or Invalid Planner Group (T024I)
Planner Group
PF2, WP2
1016-017
C1
Maintenance Plan and Item Technical object authorization group incorrect.
Maintenance Plan and Item as per Relevancy Criteria with Invalid Authorization Group (T370F)
Authorization Group
PF2, WP2
1016-018
C2
Functional Item Planning Plant and Maintenance Plant are not the same.
Maintenance Item as per Relevancy Criteria with Planning Plant <> Maintenance Plant
Maintenance Plant, Planning Plant
PF2, WP2
Informal Words **
Group 1
Group 2
Group 3
Group 4
Group 5
;

:

::

?/

@

&

=

+

$

%|[]"
Conversion Process
The high-level process is represented by the diagram below:
Image Removed
For sites that are not on SAP-PF2 and WP2 systems, collection will be done manually in the data collection template.
The high-level process for DCT is represented by the diagram below:
Image Removed
Data Privacy and Sensitivity
Not Applicable
Extraction
Extract data from a source into . There are 2 possibilities:
The data exists. connects to the source and loads the data into . There are 3 methods:
Perform full data extraction from relevant tables in the source system(s).
Perform extraction through the application layer.
Only if Syniti Migrate 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 Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate
The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads
Extraction Run Sheet
Req #Requirement DescriptionTeam Responsible
1
Extract data from source system based on relevancy rule
SyWay Data Team
2
Google Sheet report pre-populated with WP2 and WP2 information to be generated based on relevancy criteria.
SyWay Data Team
Selection Screen
Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/setNot Applicable
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for Maintenance Plan and Item data with exception of some fields which require transformation as mentioned in the transformation rule.
Maintenance Plan and Item DCT Rules
Field NameField DescriptionRuleZHIS-WARPLLegacy Maintenance PlanReference information from WP2, WP2MPLA-WARPLMaintenance Plan
Running number NNNNNNNN to NNNNNNNN for Maintenance Plan Category = XXX.
MPLA-MPTYPMaintenance Plan categoryMust reference to active Maintenance Plan category in S4/HANA (T399W)MPLA-WPTXTMaintenance Plan text40 Char text
MPLA-STRAT
Maintenance strategyMust be a valid strategy.
Must be the same strategy as the task list strategy
MPLA-HORIZ_QUALIFIER
Calculation Type of Call Horizon
Default to "% " if blank
MPLA-ABRHO
Scheduling Period
Default to "3" YR, if blank
MPLA-HUNIT
Unit in scheduling interval
Default to "YR" if if blank and ABRHO is blank
MPLA-PLAN_SORT
Sort field for maintenance plans
Must reference to active Sort field for maintenance plans in S4/HANA (T399G)
MPOS-PSTXT
Item Short Text
Description shall be defined as Frequency + TOT + Asset Tag
MPLA-TPLNR
Functional Location
Must reference to active Functional Location in S4/HANA (IFLO)
MPLA-EQUNREquipment Number
Must reference to active Equipment Number in S4/HANA (EQUI)
Can be Blank only if FLOC is updated.
Valid Entry if CT of the Equipment = Task List CT
MPOS-AUFARTOrder Type
Must reference to active Order Type in S4/HANA (T003O).
Default to YA02
MPOS-PRIOKPriority
Must reference to active Priority in S4/HANA (T356)
MPOS-PLNTYTask List Type
Must reference to active Task List Type Task List Type (TCA01)
MPOS-PLNNRKey for Task List Group
Must reference to active Key for Task List Group in S4/HANA (PLKO)
MPOS-PLNALGroup Counter
Group - Group Counter CT shall be equal to the Technical Object CT.
RMIPM-POINT
Measuring Point
Must reference to active Measuring Point in S4/HANA (IMPTT)
Must not be blank if the first 2 Chars of the Strategy = 02.
Extraction Dependencies
Item #Step DescriptionTeam Responsible
1
Ensure Syniti has the necessary connection and access to legacy servers
SyWay A2D Data Team
2
Ensure that the necessary cleansing activities in legacy sources are complete
SyWay A2D Data Team / Business
3
Ensure that create, change and deletion of master data is freeze in legacy Production system
Legacy IT
4Relevancy Criteria for Characteristics
SyWay A2D Data Team
5Relevancy Criteria for ClassSyWay A2D Data Team6Relevancy Criteria for Construction TypeSyWay A2D Data Team7Relevancy Criteria for EquipmentSyWay A2D Data Team8Relevancy Criteria for Functional LocationSyWay A2D Data Team9Relevancy Criteria for Maintenance StrategySyWay A2D Data Team10Relevancy Criteria for Measuring PointSyWay A2D Data Team11Relevancy Criteria for Task ListSyWay A2D Data Team12Relevancy Criteria for Work CentreSyWay A2D Data Team13Relevancy Criteria for Material MasterSyWay A2D 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 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
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 DescriptionTeam Responsible
1
Obtain DCT Sign-off from Business
SyWay A2D Data Team
2
In dspMigrate, select the wave –R3 S/HANA – Plant Maintenance
Syniti
3
Go to Process Area Launch and Process the Object – Maintenance Plan
Syniti
4
Execute the transformation to prepare the target ttMPLA, ttMPOS, ttOBJK, ttMMPT
Syniti
5
Review and Validate Error and Preload Reports
SyWay A2D Data Team
6
Generate Load Files
Syniti
Transformation Rules
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic1PF2, WP2MPLAHORIZ_QUALIFIER Calculation Type of Call HorizonS/4HANA MPLAHORIZ_QUALIFIER Calculation Type of Call HorizonIf no legacy data provided, default to "%"2PF2, WP2MPLAABRHOScheduling PeriodS/4HANA MPLAABRHOScheduling PeriodIf no legacy data provided, default to "3YR"3PF2, WP2MPLAHUNITUnit in scheduling intervalS/4HANA MPLAHUNITUnit in scheduling intervalIf no legacy data provided, default to "Yr"4PF2, WP2MPLATPLNRFunctional LocationS/4HANA MPLATPLNRFunctional Location
Equipment field must be blank.
Functional Location CT = Task List CT.
System Generated if Equipment is Updated
5PF2, WP2MPLAEQUNREquipment NumberS/4HANA MPLAEQUNREquipment NumberCan be Blank only if FLOC is updated.
CT of the Equipment must match Task List CT6PF2, WP2MPOSPLNALGroup CounterS/4HANA MPOSPLNALGroup CounterGroup - Group Counter CT must be same as the Technical Object CT7PF2, WP2MPOSPOSTXTItem Short TextS/4HANA MPOSPOSTXTItem Short TextDescription shall be defined as Frequency + TOT + Asset Tag8PF2, WP2MPLAMPTYPMaintenance plan categoryS/4HANA MPLAMPTYPMaintenance plan categoryDefault to "PM"9PF2, WP2MPLAWPTXTMaintenance Plan TextS/4HANA MPLAWPTXTMaintenance Plan TextMaintenance Plan description must match Task list Description10PF2, WP2MPOSAUFARTOrder TypeS/4HANA MPOSAUFARTOrder TypeDefault to "YA02"11PF2, WP2MMPTPOINTMeasuring PointS/4HANA MMPTPOINTMeasuring PointUpdated if the first 2 Chars of the Strategy = 02. 12PF2, WP2MPLAVSPOSShift Factor for Late CompletionS/4HANA MPLAVSPOSShift Factor for Late CompletionIf no legacy data provided, default to "0"13PF2, WP2MPLATOPOSTolerance for Late Completion (%)S/4HANA MPLATOPOSTolerance for Late Completion (%)If no legacy data provided, default to "10%"14PF2, WP2MPLAVSNEGShift Factor for Early CompletionS/4HANA MPLAVSNEGShift Factor for Early CompletionIf no legacy data provided, default to '0"15PF2, WP2MPLATONEGTolerance for Early Completion (%)S/4HANA MPLATONEGTolerance for Early Completion (%)If no legacy data provided, default to "10%"16PF2, WP2MPLASFAKTCycle modification factorS/4HANA MPLASFAKTCycle modification factorIf no legacy data provided, default to "1"17PF2, WP2MPLACALL_CONFIRMOnly Create New Call Object After Completing PredecessorS/4HANA MPLACALL_CONFIRMOnly Create New Call Object After Completing Predecessor
If no legacy data provided, default to blank.
System Generated if Equipment is Updated
18PF2, WP2MPLASTADTStart dateS/4HANA MPLASTADTStart dateIf no legacy data provided, default to blank19PF2, WP2RMIPMZEITIndicator for selection of time-based maintenanceS/4HANA RMIPMZEITIndicator for selection of time-based maintenanceIf no legacy data provided, default to "X"
Transformation Mapping
Mapping Table NameMapping Table Description
xtSTRAT
Xref for maintenance strategy. Fields: zLegacySTRAT, zLegacyKTEXT, STRAT, KTEXT
xtPOINT
Xref for measuring point. Fields: zLegacyPOINT, zLegacyPTTXT, POINT, PTTXT
xtMATNR
Xref for material number. Fields: zLegacyMATNR, MATNR
xtPLNNR
xref for task list. Fields: zLegacyPLNNR, PLNNR
Assembly
Legacy Assembly XREF table
xtTPLNR
Xref for functional location. Fields: zLegacyTPLNR, TPLNR
xtEQUNR
Xref for equipment number. Fields: zLegacyEQUNR, EQUNR
xtARBPL
Xref for Work Centre. Fields: zLegacyARBPL, ARBPL
Transformation Dependencies
List the steps that need to occur before transformation can commence
Item # Step Description Team Responsible
1
Ensure DCT tables completeness
SyWay
A2D
Data Team
2
Value Mappings are according to the latest design -<List of Value Mappings>
Ensure all Transformation mappings are up to date.
SyWay
SyWay A2D
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 legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets.
Verify Data Integrity	SyWay A2D Data Team to verify that the total number of Operations per Work Oder header extracted from legacy systems and DCTs (if any) should be equal to the total number of operations identified 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:
Mandatory Fields
Field and Value Mapping Correctness
Null Checks
Text Length 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 legacy systems and DCTs (if any) 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 fields below meet pass the checks:
Mandatory Fields
Field and Value Mapping Correctness
Null Checks
Text Length Checks

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

Obtain DCT Sign-off from Business

SyWay A2D Data Team

2

Syniti will provide load file

Syniti

3Go to <Load Tool>SyWay A2D Data Team4Load 3 records for "Create Maintenance Plan" function (IP01) to validate if data is loaded successfully without errorsSyWay A2D Data Team5Proceed with full load if step 4 is validatedSyWay A2D Data Team6Validate few records loaded by accessing standard transactions from S/4HNA E.g. IP03SyWay A2D Data Team7Generate post load report if step 6 is validatedSyWay A2D Data Team

Load Phase and Dependencies

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

Pre-Cutover

Configuration

Item #	Configuration Item
1	T399W

- Maintenance plan category
2
T351
-Maintenance
strategy
3
T399G - Maintenance Plan Sort Field details
4
Number Ranges for Work Plan & Item
5
T357M - System Condition
6
T356 - Priorities details
7
T399I - Maintenance Planning Plants
8
Plan Category
2
T024A-Planner Groups
3
T356-Priority
4
T003O-Order
Types details
Type
9
5
T001W - Plants/Branches details
10
TCA01 - Task List Type
11
T006 - Units of Measurement details
T399G-Maintenance Plan Sort Field
6
TFACD-Factory Calendar Definition
7
T353I-Maintenance activity types

Conversion Objects

Object #	Preceding Object Conversion Approach
1002	EQUI - Equipment
1003	IFLO - Functional Location
1005	PLKO - Task List
1006	Work Centre
1009	Class
1012	Measuring Point
1015	IMPTT - Measuring pointCharacteristic
1017	T351 - Maintenance Strategy

Error Handling

Error Type	Error Description	Action Taken
Configuration	Invalid Maintenance Plan Category	Engage Functional team to expedite and fix the error in the system	Configuration	Invalid Planner Group	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid PlantPlanner Group	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Planning Plant	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid System ConditionPlanning Plant	Engage Functional team to expedite and fix the error in the system
Configuration Configuration	Invalid Authorization GroupSystem Condition	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Maintenance Activity Type	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid PriorityEngage Functional team to expedite and fix the error in the system	Configuration	Invalid Notification Type	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Order Type	Engage Functional team to expedite and fix the error in the system
Invalid Data	Invalid Maintenance Strategy	Expedite whether the master data is changed in the system
Invalid Data	Invalid Work Centre	Expedite whether the master data is changed in the system
Invalid Data	Invalid Task List	Expedite whether the master data is changed in the system
Invalid Data	Invalid Functional Location	Expedite whether the master data is changed in the system
Invalid Data	Invalid Equipment	Expedite whether the master data is changed 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 Maintenance plan 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 plan data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
Maintenance Plan and Item is in scope based on data design and any exception requested by business.
All data cleansing and preparation has been completed.
Maintenance Plan collection timeline are the same as Equipment and Functional Location collection. Maintenance Plan collection needs to go hand in hand with equipment and functional location collection. Drop down for equipment and functional location in the maintenance plan DCT relies on the input in equipment and functional location DCT.
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.
Not all legacy Maintenance Plan and Item need to be mapped to S/4 HANA Maintenance Plan and Item. If any of the successor objects is dependent on a Maintenance Plan and Item field with no mapped values, this will be an enrichment activity or manual transformation for the successor object to derive the Maintenance Plan and Item.All Maintenance Plans and Items mapped to valid Technical Objects in S/4 HANA

Change log

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Apr 30, 2026	Actor	Type	Activity	Version
Update in progress	ERGUIZA-ext, Pinky Love	Comment	commented 9:29 am PDM-1764: Updated Updated: Plant to Maintenance Plant Added: Language Key MOUSSA-ext, Eva PRASANNA-ext, Devi
		Comment	commented 9:29 am PDM-1764: Updated Added: Maintenance Plant, Language Key MOUSSA-ext, Eva PRASANNA-ext, Devi
		State	changed state to Update in progress at 9:28 am	v409
Lead Approval	ERGUIZA-ext, Pinky Love	Edit	updated the page at 9:27 am
Apr 27, 2026
	MOUSSA-ext, Eva	State	changed expiry date to '04 May, 2026 09:56 am' at 9:56 am
	MOUSSA-ext, Eva	State	changed state to Lead Approval at 9:56 am	v408
Tech Review of Updates	MOUSSA-ext, Eva	State	gave Minor change approval at 9:56 am
Tech Review of Updates	MOUSSA-ext, Eva	State	changed state to Tech Review of Updates at 9:56 am v. 408 PDM-1764 approved	v408
Update in progress	ERGUIZA-ext, Pinky Love	Edit	updated the page at 9:55 am
		Comment	commented 9:45 am PDM-1764: Added Long Text in the structure of report PRASANNA-ext, Devi MOUSSA-ext, Eva
		Comment	commented 9:44 am PDM-1764: Added Long Text in the structure of report PRASAD-ext, Devi MOUSSA-ext, Eva
		Edit	updated the page at 9:44 am
		State	changed state to Update in progress at 9:43 am	v406

Plan Category
2	T024A-Planner Groups
3	T356-Priority
4	T003O-Order

T399G-Maintenance Plan Sort Field
6	TFACD-Factory Calendar Definition
7	T353I-Maintenance activity types

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 40

New Version 408

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Conversion Scope

Additional Information

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Transformation

Transformation Run Sheet

Transformation Mapping

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history