Status	Revision in Progress
Owner	TEE-ext, Paul
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Task List in S/4 HANA.

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

Conversion Scope

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

The data from legacy system includes:

Task List Type:
A-General Maintenance Task List
E-Equipment Task List
T-Task List for Functional Location
Task lists created on or after July 1, 2024

The data from legacy system excludes:

1. Task lists not used over 3 years. (Definition: No Active Maintenance Items Assigned, No Open Notifications, No Open Work Orders)
Exceptions:
1. Task lists used as part of a periodic plan (e.g., every X period) – to be manually reviewed by the Business
Task lists With Deletion Indicator or marked for deletion

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

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

60347

S/4HANA

60347

Additional Information

Multi-language Requirement

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

Target Design

Task List 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>.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1005-001	C1	Invalid, Inactive or no Material allocated to Task List component	Task List as per Relevancy Criteria assigned with a Material which does not belong below: 1. Material Master (S2P) as per Relevancy Criteria	Material	PF1, WP1
1005-002	C1	Invalid, Inactive or no Operations attached to Active Task List Header	Task List as per Relevancy Criteria assigned with inactive or no Task List Operations attached.	Task List Operation	PF1, WP1
1005-003	C2	Task lists not used within the last 3 years	Task List as per Relevancy Criteria but are note used across below: 1. Maintenance Items as per Relevancy Criteria 2. Notifications as per Relevancy Criteria 3. Work Order as per Relevancy Criteria	Task List	PF1, WP1
1005-004	C1	Invalid, Inactive or no Class allocated to Task List component Task List as per Relevancy Criteria assigned with a Class which does not belong below: 1. Class as per Relevancy Criteria	Class Task List as per Relevancy Criteria assigned with a Class which does not belong below: 1. Class as per Relevancy Criteria	Class	PF1, WP1
1005-005	C1	Invalid, Inactive or no Characteristic allocated to Task List component	Task List as per Relevancy Criteria assigned with a Characteristic which does not belong below: 1. Characteristic as per Relevancy Criteria	Characteristic	PF1, WP1
1005-006	C1	Invalid, Inactive or no Construction Type allocated to Task List component	Task List as per Relevancy Criteria assigned with a Construction Type which does not belong below: 1. Construction Type as per Relevancy Criteria	Construction Type	PF1, WP1
1005-007	C1	Invalid, Inactive or no Production Resources & Tool allocated to Task List component	Task List as per Relevancy Criteria assigned with a Production Resources & Tool which does not belong below: 1. Production Resources & Tool as per Relevancy Criteria	Production Resources & Tool	PF1, WP1
1005-008	C1	Invalid or Inactive Bill of Material linked to Task List	Task List as per Relevancy Criteria assigned with a Bill of Material which does not belong below: 1. Bill of Material as per Relevancy Criteria	Bill of Material	PF1, WP1
1005-009	C1	Active Task List Operations allocated to inactive Task List Headers	Task List Operation as per Relevancy Criteria assigned with no or inactive Task List Headers attached.	Task List Operation	PF1, WP1
1005-010	C1	Active task list components allocated to inactive tsk list operation	Task List Component as per Relevancy Criteria assigned with no or inactive Task List Operations attached.	Task List Component	PF1, WP1
1005-011	C2	Invalid or Inactive Business Partner (Vendor) linked to Task List	Task List as per Relevancy Criteria assigned with a Material BOM which does not belong below: 1. Business Partner / Vendor (S2P) as per Relevancy Criteria	Business Partner (Vendor)	PF1, WP1
1005-012	C1	Invalid or Inactive Maintenance Strategy linked to Task List	Task List as per Relevancy Criteria assigned with a Maintenance Strategy which does not belong below: 1. Maintenance Strategy as per Relevancy Criteria	Maintenance Strategy	PF1, WP1
1005-013	C1	Invalid, Inactive or no Work Centres linked to Task List	Task List as per Relevancy Criteria assigned with a Work Centre which does not belong below: 1. Work Centre as per Relevancy Criteria	Work Centre	PF1, WP1
1005-014	C1	Missing Task Lists Descriptions	Task List as per Relevancy Criteria where there are blank Task ListDescriptions.	Task List Description	PF1, WP1
1005-015	C2	Task Lists Descriptions with Informal Words	Task Lists Description	Task List as per Relevancy Criteria which contain [Informal Words] in the Task List Description	PF1, WP1
1005-016	C1	Task List Plant incorrect.	Task List as per Relevancy Criteria with Invalid Plant (T001W)	Plant	PF1, WP1
1005-017	C1	Task List Controlling Areas incorrect.	Task List as per Relevancy Criteria with Invalid Controlling Areas (TKA01)	Controlling Area	PF1, WP1

Informal Words **

Group 1	Group 2	Group 3	Group 4	Group 5
*DNU	Delete	donot	Formerly	Old #
..	Deletion	DONT USE	From	Old[ ]
/	DELISTED	DON'T USE	Incorrect	PLEASE USE
?	Discontinued	Dup Use	Invalid	Pls Use
@	Disposable	DUPLICATE	New	Previously
^	DNU	-DUPLICATE	NOT ACTIVE	Replace
+	Do Not	DUPLICATION	not in use	Replaced
++	Do Not Re	Duplicidad	Not Used	RESERVED
£	Do Not Sell	Duplikat	NOT VALID	Retired
Defective	Do Not Use	Former	Obsolete	ZZDEL

Conversion Process

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

Data Privacy and Sensitivity

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:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Only if ; 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 . This is to be conducted using DCT (Data Collection Template) in

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
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data Team

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

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

Task List DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Ensure Syniti has the necessary connection and access to legacy servers	Data
2	Ensure that the necessary cleansing activities in legacy sources are complete	Data / Business
3	Ensure that create, change and deletion of master data is freeze in legacy Production system	Legacy IT

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	<Add steps from Syniti Migrate here>	SyWay A2D Data Team
3	Review and Validate Error and Preload Reports	SyWay A2D Data Team
4	Generate Load Files	SyWay A2D Data Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Mapping Table Name	Mapping Table Description
IFLOT	Functional Locations
T003O	Order Type & Priority
TQ80	Notification Type
EQUI	Equipment
CRHD	Work Centres
CSKU	Cost Centre

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>	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	Syniti will provide load file	Syniti

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	Planning Plants
2	Maintenance Plants
3	Number Ranges for Task List Groups
4	Task List Planner Groups
5	System Condition
6	Purchasing Group and Purchasing Organization
7	Material Group

Conversion Objects

Object #	Preceding Object Conversion Approach
1003	Functional location
1002	Equipment
1016	Maintenance plan and item
1017	Maintenance Strategies & Packages
	Construction Types/ Assemblies
	Documents/DIR
2019	Material Master
	Vendors
	Service Masters
	Cost Element

Error Handling

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

Completeness

Task	Action
Verify Count	SyWay A2D Data Team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA.
Verify Logs	Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.).

Accuracy

Task	Action
Conversion Accuracy	SyWay A2D Data Team to verify that the Work order 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 Work order 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.
Task List is in scope based on data design and any exception requested by business.
All data cleansing and preparation has been completed.

Change log

Version	Published	Changed By	Comment
CURRENT (v. 2)	Apr 30, 2026 03:07	MAHAJAN-ext, iesha
v. 815	Apr 14, 2026 13:52	JOSHI-ext, Aditya
v. 814	Apr 13, 2026 15:16	JOSHI-ext, Aditya
v. 813	Apr 13, 2026 08:54	JOSHI-ext, Aditya
v. 812	Apr 10, 2026 06:03	JOSHI-ext, Aditya
v. 811	Apr 10, 2026 05:19	JOSHI-ext, Aditya
v. 810	Apr 07, 2026 13:06	ERGUIZA-ext, Pinky Love
v. 809	Apr 07, 2026 10:15	ERGUIZA-ext, Pinky Love	CR0438: Update in Relevancy Criteria JEST Inactive Flag
v. 808	Apr 07, 2026 10:12	ERGUIZA-ext, Pinky Love
v. 807	Apr 02, 2026 13:41	ERGUIZA-ext, Pinky Love

Go to Page History

Workflow history

Title	Last Updated By	Updated	Status
There are no pages at the moment.

Apr 30, 2026	Actor	Type	Activity	Version
Revision in Progress	MAHAJAN-ext, iesha	State	changed state to Revision in Progress at 3:07 am	v816
Approved	MAHAJAN-ext, iesha	Edit	updated the page at 3:07 am Other contributors:
Apr 28, 2026
	TAN-ext, Charmaine	State	changed state to Approved at 7:35 am (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v815
Lead Approval	TAN-ext, Charmaine	State	gave Minor change approval at 7:35 am [PMO Comments] Conversion Spec completed as per CS register and functional review completed
Apr 15, 2026
	MOUSSA-ext, Eva	State	changed expiry date to '22 Apr, 2026 12:11 am' at 12:11 am
	MOUSSA-ext, Eva	State	changed state to Lead Approval at 12:11 am	v815

Workflow history

Space shortcuts

Page tree

CNV-1005 Task List

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

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