Purpose

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

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

Conversion Scope

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

In Syensqo’s SAP S/4HANA landscape, Equipment is used to define an individual asset or a sub-component of an asset. Each Equipment record represents a maintainable unit, serving as a critical master data for executing maintenance and work management processes.

Depending on its installation context, Equipment can be categorized as either a Static asset or a rotable part which can be dismantled and installed at a different location. Regardless of its type, every piece of Equipment is installed at a relevant superior Functional Location, ensuring its position within the asset hierarchy is clearly defined.
This structured approach supports efficient maintenance planning, traceability, and lifecycle management of assets across Syensqo’s operations.

The data from legacy system includes:

• Equipment having Maintenance Plant (IFLOT-WERKS) in scope (Value Mapping : Plant, where Maintenance Plant = 'Yes')
• Functional Locations to be migrated as Equipment as part of Inclusion List (EXC-Functional Location_ID)

The data from legacy system excludes:

• Equipment with System Status (JEST-STAT) = Inactive 'INAC'
• Equipment with System Status (JEST-STAT) = Deletion Flag 'DLFL'
• Equipment with System Status (JEST-STAT) = In the warehouse 'ESTO'
• Equipment with System Status (JEST-STAT) = Available 'AVLB'
• Equipment with System Status (JEST-STAT) <> Installed 'INST'
• Equipment with Serial Number (EQUI-SERNR) <> '' (BLANK)

List of Tables to extract for this object is maintained here: Extract Table Register.

Additional Information

Multi-language Requirement

Equipment description will be made available in English.

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

Document Management

1. <Types of documents> documents currently attached to Equipment will be migrated to <TBD>.
2. Refer to the conversion approach for <TBD>.

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

EAM Equipment Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Equipment information follows the Master Data Standard document DD-FUN- 050 Master Data Standard Equipment.xlsx.

The technical design of the target for this conversion approach.

Data Cleansing

Conversion Process

Conversion will involve both Source System Extraction as well as using DCT (Data Collection Template) - 

The high-level process for Source System Extraction is represented by the diagram below:

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:

Data Privacy and Sensitivity

Extraction

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

1. 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.
2. 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

Selection Screen

Data Collection Template (DCT)

DCT Rules

Extraction Dependencies

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:

1. 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
2. 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

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

The load process includes:

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

Load Run Sheet

Load Phase and Dependencies

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Equipment is in scope based on data design and any exception requested by business.
• All data cleansing and preparation has been completed.

See also

Change log

Workflow history