Purpose

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

In SAP Plant Maintenance (SAP S4/HANA EAM), a piece of equipment is an individual object that is to be maintained independently. Each piece of equipment is managed independently in the system, so that you can: 

• Manage individual data from a maintenance perspective for the object

• Perform individual maintenance tasks for the object

• Keep a record of the maintenance tasks performed for the object

• Collect and evaluate data over a long period of time for the object

As per Syensqo's design, all maintainable asset will be represented by Equipment, with the exception where the asset is maintained by Syensqo but not owned, in which case the asset will be migrated as a Functional Location. As per SyWay design, EAM Equipment will be standardized.

Conversion Scope

The scope of this document covers the approach for creation of Equipment in 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. An Equipment is defined based on its construction and a defined Maintenance strategy is followed by to ensure its Reliability and sustainability.

An Equipment is only created when there is a defined Maintenance Strategy defined for it and a criticality derived from Risk Assessment process.

Depending on its installation context, Equipment is categorized by a user status to define its current state in its lifecycle from Planning to Retire. Every piece of Equipment that is Inservice is installed at a relevant superior Asset Functional Location or superior Equipment, 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.

Conversion from legacy will adopt a hybrid method: DCT and Extraction for migration.

• Extraction to include all the active Equipment as well the specific Functional Locations flagged to be migrated as Equipment
• DCT to include all relevant Assemblies flagged to be migrated as Equipment

Equipment in Syensqo to-be asset structure will be positioned under the Category 'A' (Asset) Functional Location and will comprise of 2 levels. 

Note: Please refer CNV-1003 Function Location for details on the Functional Location Asset Level conversion. 

The data from legacy system includes:

• Equipment (EQUI-EQUNR) having Maintenance Plant (EQUI-WERKS) in scope (Value Mapping : Plant, where Maintenance Plant = 'Yes')
• Functional Locations (IFLOT-TPLNR) to be migrated as Equipment as part of mapping (Functional Location, where New Technical Object = 'EQ')

The data from legacy system excludes:

• Equipment (EQUI-EQUNR) with System Status (JEST-STAT) = Inactive 'INAC'
• Equipment (EQUI-EQUNR) with System Status (JEST-STAT) = Deletion Flag 'DLFL'
• Equipment (EQUI-EQUNR) with System Status (JEST-STAT) = In the warehouse 'ESTO'
• Equipment (EQUI-EQUNR) with System Status (JEST-STAT) = Available 'AVLB'
• Equipment (EQUI-EQUNR) with System Status (JEST-STAT) <> Installed 'INST'
• Equipment (EQUI-EQUNR) 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

Refer to the KDD085 - Document Management in the SyWay Solution

Note: Documents attached to Equipment will be migrated as part of 9104-EAM Attachments.

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

The technical design of the target for this conversion approach.

1. Equipment Master

2. Equipment Short Text

Note: Each Equipment must have 1 entry for English language and 1 entry for the language(s) of the country in which each Maintenance Plant assigned is located (French, Italian, Mandarin, Brazilian Portuguese, German or Spanish). 

3. Equipment Classification (Header)

 4. Equipment Classification (Characteristics Value Allocation)

5. Equipment Partner

6. Equipment User Status

7. Equipment Long Text Header

8. Equipment Long Text Line

Note:

1. Long Text is not mandatory, only load when there is data
2. One Long Text Header must have at least 1 Long Text Line

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 that is located here.

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