Status	Approved
Owner	ERGUIZA-ext, Pinky Love
Stakeholders

Purpose

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

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

Conversion Scope

The scope of this document covers the approach for converting active Classes from Legacy systems (PF1, WP1) and creation of New EAM Classes into S/4 HANA following the <Project Name> Class Master Data Design Standard.

The data from legacy system includes:

Classes with below Class Type
- 001-Materials (Construction Types)
- 002-Equipment class (PF2, WP2)
- 003-Functional location (PF2, WP2)
- 018-Task list class (WP2)
- 019-Work center class (PF2, WP2)
- 037-Measuring point (WP2)
Valid from [Current Date]
Status = 1 (Released)

The data from legacy system excludes:

Classes for Deletion (Deletion Indicator = X)

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

Class will be collected via DCT. An initial extract of the relevant classes will be provided in google sheet format to assist business in decision making on including any relevant classes from PF2 and WP2 as EAM Class.

Any additional classes that need to be created to support the new design may be added in the DCT.

A review and standardization will be done across all classes in the DCT.

Please see an indication of what will be baselined from source systems below and what will be constructed in the DCT.

1,500

3,000

Additional Information

Multi-language Requirement

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

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

EAM Class 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.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement

Data Cleansing

No data cleansing is required for Class in the legacy system. If any cleansing is deemed necessary, it will be performed outside of the system.

As a result, the cleansed Class data will be populated directly in the Data Collection Template (DCT).

Conversion Process

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

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

For sites not on SAP-PF2 or WP2 systems
For new classes that need to be created to support the to-be design

Data Privacy and Sensitivity

Extraction

Syniti Migrate connects to the sources.
An initial extract of the relevant Characteristics will be loaded into a google sheet report to assist business with any standardization.

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from source system based on relevancy rule	SyWay Data Team
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data Team

Selection Screen

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 EAM Class data with exception of some fields which require transformation as mentioned in the transformation rule.

The extracted report will be loaded into the required structure using the DCT.
Standardization activities (including deduplication, standardization and additions) will be carried out within the DCT.

Class DCT Rules

Discuss with Syniti Later if we will plug all languages in one DCT or if to split another DCT for other Languages

Field Name	Field Description	Rule
zLegacyCLASS	Legacy Class number	Conditional: Legacy Class Number if comes from PF2 or WP2 Legacy Class Number: For reference only
zLegacyKLBEZ	Legacy Description	Conditional: Legacy Class Description if comes from PF2 or WP2 Legacy Description: For reference only
KLART	Class Type	Mandatory. Should be from the values defined below 001-Materials (Construction Type) 002-Equipment class 003-Functional location 017–Document Info Record 018-Task list class 037-Measuring point 019-Work center class 080-Maintenance Plans
CLASS	Class number	Mandatory. Ensure no duplicate.
SPRAS	Language	Conditional. Populate if Language is not in English. Must be one of the installed language key : (List down as per Language KDD)
KLBEZ	Description	Mandatory. Ensure no duplicate (With other classes within the same class type). Ensure populated with Description as per specified Language. Approach if the description is more than 40 characters: Abbreviate to required length (40 Chars) by eliminating vowels, use '&' for 'and', ensure short text best describes the characteristic.
STATU	Class status	Default to "1"
KLAGR	Class Group	Mandatory. Must be a valid class group.
VONDT	Valid From	2 years prior to cutover date Hide since this is the default rule.
BISDT	Valid To	31.12.9999
zComment	Comments	Comments as per DCT Build

Characteristic Assignment DCT Rules

Field Name

Field Description

Rule

CLASS

Class number

Mandatory.

Class Number as per Class DCT.

ATNAM

Characteristic Name

Mandatory.

Characteristic Name as per Characteristic DCT

zComment

Comments

Comments as per DCT Build

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Relevancy Criteria for Construction Types	SyWay A2D Data Team
2	Relevancy Criteria for Functional Location	SyWay A2D Data Team
3	Relevancy Criteria for Equipment	SyWay A2D Data Team
4	Relevancy Criteria for Task List	SyWay A2D Data Team
5	Relevancy Criteria for Work Centre	SyWay A2D Data Team
6	Relevancy Criteria for Measuring Point	SyWay A2D Data Team
7	Data cleansing of legacy EAM Class data must be completed. If standardization within the DCT begins using relevant data from PF2 and WP2 before the cleansing is finalized, it is understood that the business will take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.	Business

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

There are no transformation rules all values will be copied from DCT.

Transformation Mapping

Mapping Table Name	Mapping Table Description
Not Applicable

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 - None for Class	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 the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task

Action

Conversion Accuracy

SyWay A2D Data Team to verify that all fields below meet pass the checks:

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 the the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data).

Load

The load process includes:

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

Load Run Sheet

Item #	Step Description	Team Responsible
1	Go to <Load Tool>	SyWay A2D Data Team
2	Load 3 records for "Create Class" function to validate if data is loaded successfully without errors	SyWay A2D Data Team
3	Load 3 records for "Assign Characteristics" function to validate if data is loaded successfully without errors	SyWay A2D Data Team
4	Proceed with full load if steps 2 and 3 are validated	SyWay A2D Data Team
5	Validate few records loaded by accessing standard transactions from S/4HNA E.g. CL03 / CL6AN for Class	SyWay A2D Data Team
6	Generate post load report if step 5 is validated	SyWay A2D Data Team

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	TCLA-Class Types
2	TCLG-Class Groups
3	TCLU-Class Status

Conversion Objects

Object #	Preceding Object Conversion Approach
1015	Characteristics

Error Handling

Error Type	Error Description	Action Taken
Configuration	Invalid Class Type	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Class Group	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Class Status	Engage Functional team to expedite and fix the error in the system
Invalid Data	Invalid or Inactive Characteristic assigned	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 Reference Functional Location 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 Reference Functional Location 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.
is in scope based on data design and any exception requested by business.

Change log

Version	Published	Changed By	Comment
CURRENT (v. 14)	Jan 05, 2026 04:34	ERGUIZA-ext, Pinky Love	CR0240: Refer to </Start CR0240> </End CR0240> texts. Note: The requirement has been pre-approved within the CS before. Just formally added </Start CR0240> </End CR0240> texts since the CR has been approved
v. 139	Jan 05, 2026 04:34	ERGUIZA-ext, Pinky Love
v. 138	Dec 05, 2025 13:24	ERGUIZA-ext, Pinky Love	Removed 017-Document Management as missed on previous update as part of CR0164
v. 137	Dec 05, 2025 10:44	ERGUIZA-ext, Pinky Love
v. 136	Dec 04, 2025 12:25	ERGUIZA-ext, Pinky Love
v. 135	Dec 04, 2025 12:21	ERGUIZA-ext, Pinky Love
v. 134	Dec 04, 2025 12:19	ERGUIZA-ext, Pinky Love
v. 133	Nov 13, 2025 12:27	ERGUIZA-ext, Pinky Love	Characteristic Name to use Value Mapping: Characteristic A2D
v. 132	Nov 13, 2025 12:22	ERGUIZA-ext, Pinky Love
v. 131	Nov 13, 2025 12:21	ERGUIZA-ext, Pinky Love

Go to Page History

Workflow history

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

Jan 19, 2026	Actor	Type	Activity	Version
Approved	LEIGHTON-ext, Dean	State	changed state to Approved at 5:50 am	v140
Lead Approval	LEIGHTON-ext, Dean	State	gave POD Lead Review approval at 5:50 am CR0164 Updates Approved
Jan 05, 2026
	MOUSSA-ext, Eva	State	changed expiry date to '12 Jan, 2026 05:35 pm' at 5:35 pm
	MOUSSA-ext, Eva	State	changed state to Lead Approval at 5:35 pm	v140
Tech Review	MOUSSA-ext, Eva	State	gave Syniti Team Review approval at 5:35 pm
		State	changed expiry date to '10 Jan, 2026 05:35 pm' at 5:35 pm
		State	changed state to Tech Review at 5:35 pm Version 140. CR0240	v140
Pending adjustment	MOUSSA-ext, Eva	State	changed state to Pending adjustment at 5:35 pm	v140

Workflow history

Space shortcuts

Page tree

CNV-1009 Class

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