Status	Approved
Owner	ERGUIZA-ext, Pinky Love
Stakeholders

Purpose

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

Legacy Plant Maintenance Characteristics is using a diverse range of formats across the different systems. There are instances where the same characteristics are duplicated within and across sources, with informal words, and linked to Plant Maintenance Classes but are not used by Plant Maintenance objects at all. This results in data inconsistency. As per SyWay design, EAM Characteristics will be standardized.

Conversion Scope

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

Characteristics define a single custom field used to capture specific properties, attributes or values of an object. In SAP, Classes and Characteristics together form the “Classification System”.
For Syensqo, Characteristics will be used to record key attributes supporting reliability categorization and various analyses. It will be primarily used for information and reporting of attribute data across a large set of technical objects (e.g. Functional Location Structure). These Characteristics will be created centrally and assigned to relevant Classes.

From the current source systems’ perspective, Class and Characteristic concepts already exist (but in slightly different structure). Characteristic data and their allowed values are independently managed between PF2 and WP2. While these have been identified as source systems, a considerable amount of data construction will be required to support the production of data load sheets in the desired format.

While these systems serve as sources, extensive construction will be necessary to produce properly formatted data load sheets for S/4 HANA.
The scope of this document covers the approach for converting active Characteristics from Legacy systems (PF2, WP2) and creation of New EAM Characteristics into S/4 HANA following the Characteristics Master Data Design Standard.

The data from legacy system includes:

Characteristics assigned to Classes with below Class Type
- 001-Materials: PM Assembly (PF2, WP2)
- 002-Equipment class (PF2, WP2)
- 003-Functional location (PF2, WP2)
- 018-Task list class (WP2)
- 037-Measuring point (WP2)
Valid from [Current Date]
Status = 1 (Released)

The data from legacy system excludes:

Characteristics 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

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

Any additional Characteristics 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 characteristics in the DCT.

6,500

13,000

Additional Information

Multi-language Requirement

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

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

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
CABN	ATNAM	ATNAM	Characteristic Name	CHAR	30	Mandatory
CABN	DATUV	DATUV	Valid-From Date	DATS	8
CABN	ATKLA	ATKLA	Characteristics Group	CHAR	10
CABN	ATMST	ATMST	Status of a characteristic	CHAR	1	Mandatory
CABN	ATFOR	ATFOR	Data Type	CHAR	4	Mandatory
CABN	ANZST	ANZST	Number of Characters	INT2	5
CABN	ANZDZ	ANZDZ	Number of Decimal Places	INT2	5
CABN	ATKLE	ATKLE	Case Sensitive	CHAR	1
CABN	CURRENCY	CURRENCY	Currency Key	CUKY	1
CABN	MSEHI	MSEHI	Unit of Measure	UNIT	6
CABN	ATSCH	ATSCH	Value with template	CHAR	30
CABN	ATDEX	ATDEX	Exponent Display Format	NUMC	1
CABN	ATEIN	ATEIN	Single Value	CHAR	1
CABN	ATAME	ATAME	Indicator: More Than One Value Allowed for Characteristic	CHAR	1
CABN	ATGLA	ATGLA	Indicator: restrictable characteristic	CHAR	1
CABN	ATERF	ATERF	Entry Required	CHAR	1
CABN	ATINT	ATINT	Interval values allowed	CHAR	1
CABN	ATVOR	ATVOR	Value with Plus or Minus Sign	CHAR	1
CABN	ATSON	ATSON	Indicator: Additional Values	CHAR	1

4. Characteristic Values

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
CABN	ATNAM	ATNAM	Characteristic Name	CHAR	30	Mandatory
CAWN	ATWRT	ATWRT	Characteristic Value	CHAR	30
CAWN	ATSTD	ATSTD	Default value	CHAR	1

3. Characteristic Restrictions to Class Types

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
CABN	ATNAM	ATNAM	Characteristic Name	CHAR	30	Mandatory
KSML	KLART	KLASSENART	Class Type	0	3	Mandatory

4. Characteristic Values

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
CABN	ATNAM	ATNAM	Characteristic Name	CHAR	30	Mandatory
CAWN	ATWRT	ATWRT	Characteristic Value	CHAR	30
CAWN	ATSTD	ATSTD	Default value	CHAR	1

5. Characteristic Value Descriptions

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
CABN	ATNAM	ATNAM	Characteristic Name	CHAR	30	Mandatory
CAWNT	SPRAS	SPRAS	Language Key (Characteristic Value Description)	LANG	1
CAWN	ATWRT	ATWRT	Characteristic Value	CHAR	30
CAWNT	ATWTB	ATWTB	Characteristic Value Description	CHAR	30

Data Cleansing

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

As a result, the cleansed Characteristics 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 Characteristics that need to be created to support the to-be design

Data Privacy and Sensitivity

Not Applicable

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:
1. 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.
2. 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
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 Characteristics 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.

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.

Characteristics DCT Rules

Field Name	Field Description	Rule
zLegacyATNAM	Legacy Characteristic Name	Conditional: Legacy Characteristic Name if comes from PF2 or WP2 Legacy Characteristic Name: For reference only
zLegacyKTEXT	Characteristic description	Conditional: Legacy Characteristic Description if comes from PF2 or WP2 Legacy Characteristic Description: For reference only
ATNAM	Characteristic Name	Mandatory. List down naming convention here. E.g Must begin with PM_
SPRAS	Language	Mandatory. Default to "EN". English is required for all Classes.
KTEXT	Characteristic description	Mandatory. List down naming convention here. Ensure no duplicate. Ensure populated with Description as per specified Language. Approach if the description is more than 30 characters: Abbreviate to required length (30 Chars) by eliminating vowels, use '&' for 'and', ensure short text best describes the characteristic.
ATMST	Characteristic Group	Mandatory. Must be a valid Characteristic Group.
ATMST	Status	Always 1 (Released).
ATFOR	Data type of characteristic	Mandatory Character format (CHAR): for characteristic values that consist of a character string Numeric format (NUM): for numeric characteristic values Date format (DATE): for characteristic values that represent a date Time format (TIME): for characteristic values that represent a time Currency format (CURR): for characteristic values that are entered in a currency
ANZST	Number of Characters	Must not have decimal, plus or minus sign. Not applicable for data type: Date and Time
ATKLE	Case Sensitive	Indicator (check box)
ANZDZ	Number of Decimal Places	Conditional. Optional for NUM data type. Defaulted for CURR format. Blank for others Data Types. If populated, must be less than Number of Characters.
MSEHI	Unit of Measure	Conditional. Optional for NUM format. Blank for others. Only valid UOM allowed.
ATSCH	Value with template
ATKLE	Indicator: Case Sensitive	Indicator (check box)
ATKLA	Chars Group
ATEIN	Single value	Radio button between Single value and multiple value. This is defaulted, do not hide.
ATLIS	Multiple value	Radio button between Single value and multiple value
ATAME	Multilingual characteristic
MSEHI	Unit of Measurement
ATDIM	Exponent display
ATMST	Status of a characteristic
zComment	Comments	Comments as per DCT Build

Characteristics DCT (Non-EN Language) Rules

Field Name	Field Description	Rule
zLegacyATNAM	Legacy Characteristic Name	Conditional: Legacy Characteristic Name if comes from PF2 or WP2 Legacy Characteristic Name: For reference only
zLegacyKTEXT	Characteristic description	Conditional: Legacy Characteristic Description if comes from PF2 or WP2 Legacy Characteristic Description: For reference only
ATNAM	Characteristic Name	Mandatory. List down naming convention here. E.g Must begin with PM_
SPRAS	Language	Mandatory. Populate for Languages not in English. Must be one of the installed language key : (List down as per Language KDD)
KTEXT	Characteristic description	Mandatory. List down naming convention here. Ensure no duplicate. Ensure populated with Description as per specified Language. Approach if the description is more than 30 characters: Abbreviate to required length (30 Chars) by eliminating vowels, use '&' for 'and', ensure short text best describes the characteristic.
zComment	Comments	Comments as per DCT Build

Characteristics Value DCT Rules

Field Name	Field Description	Rule
ATNAM	Characteristic Name
SPRAS	Language	Mandatory. Default to "EN". English is required for all Classes.
KTEXT	Characteristic description	Only applicable for Data Type CHAR No special characters allowed Ensure no duplicate description
ATWRT	Characteristic Value	Must be same data type as defined in CABN-ATFOR If populated, Ensure no duplicate per characteristic and Description combination
ATWTB	Characteristic value description	Only applicable for Data Type CHAR. No special characters allowed Ensure no duplicate description

Characteristics Value DCT (Non-EN Language) Rules

Field Name	Field Description	Rule
ATNAM	Characteristic Name
SPRAS	Language	Mandatory. Populate for Languages not in English. Must be one of the installed language key : (List down as per Language KDD)
KTEXT	Characteristic description	Only applicable for Data Type CHAR No special characters allowed Ensure no duplicate description
ATWRT	Characteristic Value	Must be same data type as defined in CABN-ATFOR If populated, Ensure no duplicate per characteristic and Description combination
ATWTB	Characteristic value description	Only applicable for Data Type CHAR. No special characters allowed Ensure no duplicate description

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Relevancy Criteria for PM Assembly / 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

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.

Source system	Source Field	Source Description	Target Table	Target Field	Target Description	Transformation Logic
DCT	ATNAM	Characteristic Name	CABN	ATNAM	Characteristic Name	Direct Mapping
DCT	KTEXT	Characteristic description	CABNT	ATBEZ	Description	Direct Mapping
DCT	ATKLA	Characteristics Group	CABN	ATKLA	Characteristics Group	Direct Mapping
DCT	ATMST	Status of a characteristic	CABN	ATMST	Status of a characteristic	Direct Mapping
			CABN	ATAUTH	Authorization Group for Characteristics Maintenance
DCT	ATFOR	Data type of characteristic	CABN	ATFOR	Data type of characteristic	Direct Mapping
DCT	ANZST	Number of Characters	CABN	ANZST	Number of Characters	Direct Mapping
DCT	ANZDZ	Number of Decimal Places	CABN	ANZDZ	Number of Decimal Places	Direct Mapping
DCT	ATKLE	Case Sensitive	CABN	ATKLE	Case Sensitive	Direct Mapping
DCT	ATSCH	Value with template	CABN	ATSCH	Value with template	Direct Mapping
DCT	ATEIN	Single Value	CABN	ATEIN	Single Value	Direct Mapping
			CABN	ATERF	Entry Required
			CABN	WAERS	Currency
			CABN	ATINT	Interval Values Allowed
			CABN	ATVOR	Value with Plus or Minus Sign
DCT	MSEHI	Unit of Measurement Technical Format	CABN	MSEHI	Unit of Measurement Technical Format	Direct Mapping
			CABN	ATTAB	Table Name
			CABN	ATFEL	Field Name
			CABN	ATWRD	Display Allowed Values Defined in Characteristic
			TCME	KLART	Valid Class Type
			CABN	ATSON/ATLIS	Indicator: Additional Values/More Than One Value Allowed for Characteristic
DCT	ATWRT	Characteristic Value	CAWN	ATWRT	Characteristic Value	Direct Mapping
			CAWN	ATSTD	Default value
			CABN	ATBSO	Display of values assigned to a characteristic
			CAWN	DATUB	Valid-to date
			CAWN	DATUV	Valid-From Date
			CABN	ATPRT	Check table

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	Run relevancy procedures in Syniti Migrate	SyWay A2D Data Team
3	Value Mappings are according to the latest design - None for Characteristics	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 Characteristics" function to validate if data is loaded successfully without errors	SyWay A2D Data Team
3	Load 3 records for "Create Characteristic Values" function to validate if data is loaded successfully without errors	SyWay A2D Data Team
4	Load 3 records for "Assign Characteristic Values" function to validate if data is loaded successfully without errors	SyWay A2D Data Team
5	Proceed with full load if steps 2, 3 and 4 are validated	SyWay A2D Data Team
6	Validate few records loaded by accessing standard transactions from S/4HNA E.g. CT04 / CT10 for Characteristics	SyWay A2D Data Team
7	Generate post load report if step 6 is validated	SyWay A2D Data Team

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	T002-Language Keys
2	T006-Units of Measurement
3	TCMG-Characteristic Group
4	TCMS-Characteristic Status

Conversion Objects

Object #	Preceding Object Conversion Approach
Not Applicable

Error Handling

Error Type	Error Description	Action Taken
Configuration	Invalid Language Key	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Units of Measurement	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Characteristic Group	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Characteristic Status	Engage Functional team to expedite and fix the error 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	SyWay A2D Data Team to verify that the EAM Characteristics 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 Characteristics 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. 28)	Mar 17, 2026 07:56	ERGUIZA-ext, Pinky Love
v. 141	Dec 10, 2025 15:40	ERGUIZA-ext, Pinky Love
v. 140	Dec 10, 2025 15:22	ERGUIZA-ext, Pinky Love
v. 139	Nov 13, 2025 12:14	ERGUIZA-ext, Pinky Love
v. 138	Nov 13, 2025 12:10	ERGUIZA-ext, Pinky Love
v. 137	Nov 13, 2025 12:01	ERGUIZA-ext, Pinky Love
v. 136	Nov 13, 2025 11:50	ERGUIZA-ext, Pinky Love
v. 135	Nov 04, 2025 14:35	ERGUIZA-ext, Pinky Love	Consolidation of Char Values from 3 fields to 1 DCT Field
v. 134	Nov 04, 2025 14:30	ERGUIZA-ext, Pinky Love
v. 133	Nov 04, 2025 14:11	ERGUIZA-ext, Pinky Love

Go to Page History

Workflow history

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

Mar 25, 2026	Actor	Type	Activity	Version
Approved	MOUSSA-ext, Eva	State	changed state to Approved at 10:09 pm	v142
Revision under Review	MOUSSA-ext, Eva	State	gave Minor change approval at 10:09 pm PDM-1366
Revision under Review	MOUSSA-ext, Eva	State	changed state to Revision under Review at 10:08 pm	v142
Mar 18, 2026
Revision in Progress	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:39 pm	v142
Mar 17, 2026
Edited following Approval	ERGUIZA-ext, Pinky Love	Comment	commented 7:58 am PDM-1366: Updates on ATCOD & ATBEW required or Load Note I also renumbered the Rule # as 5 was after 3 previously (missing 4)
		Comment	commented 7:58 am PDM-1366: Updates on ATCOD & ATBEW required or Load Note I also renumbered the Rule # as 5 was after 3 previously (missing 4)
		Comment	commented 7:58 am PDM-1366: Updates on ATCOD & ATBEW required or Load Note I also renumbered the Rule # as 5 was after 3 previously (missing 4)
		Comment	commented 7:58 am PDM-1366: Updates on ATCOD & ATBEW required or Load
		Comment	commented 7:57 am PDM-1366: Updates on ATCOD & ATBEW required or Load
		Comment	commented 7:57 am PDM-1366: Updates on ATCOD & ATBEW required or Load
		Comment	commented 7:57 am PDM-1366: Updates on ATCOD & ATBEW required or Load
		Comment	commented 7:57 am PDM-1366: Updates on ATCOD & ATBEW required or Load
		Edit	updated the page at 7:56 am
		State	changed state to Edited following Approval at 6:56 am	v142
Dec 10, 2025
Approved	MOUSSA-ext, Eva	State	changed state to Approved at 4:35 pm	v141

Workflow history

Space shortcuts

Page tree

CNV-1015 Characteristic

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

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