Purpose

The purpose of this document is to define the conversion approach to create PM Assembly / Construction Type in S/4 HANA. For the purpose of this document, the term A/CT shall refer to the object PM Assembly / Construction Type.

In SAP Plant Maintenance (SAP S/4 HANA EAM), the Construction Type is a material master reference assigned to a technical object (equipment or functional location) to represent its standard design or assembly structure. This allows the system to link standard data such as Bills of Materials (BOM), Task Lists, and Catalogs to multiple technical objects that share the same physical construction 

The Catalog profile assigned to the construction type is used to define the Object Parts, Causes, Damages of the asset.

Below are the guiding principles of the Construction Type:

• Grouping Similar Assets:
  A Construction Type is created to group assets that share similar construction characteristics and are built using the same components.

• Standardized Maintenance Strategy:
  Each Construction Type is linked to a specific maintenance strategy. If the maintenance strategy differs, a separate Construction Type is required.

• BOM-Based Structuring:
  Construction Types are defined based on Bill of Materials (BOMs) that apply across similar asset types. These BOMs outline the construction hierarchy using sub-assemblies (Assembly).

• FMECA-Driven Classification:
  Construction Types also take into account Failure Modes, Effects, and Criticality Analysis (FMECA) codes relevant to the construction of the asset, supporting reliability-centered maintenance planning for all similar types of Assets.

A/CT needs to be constructed as a logical grouping based on the above.

Conversion Scope

The scope of this document covers the approach for creation of A/CT in S/4 HANA following the PM Assembly / Construction Type Master Data Design Standard. 

The creation of A/CT follows the endorsed EAM Core Data Design describing the Asset Identification Methodology.

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

Legacy system did not have the concept of using Construction Type in the similar manner as S/4 Hana. Hence, there is no extraction of Construction Type required from Legacy.

However, in the Legacy system, the assembly is used as part of Bill of Material (BOM) to represent the assembly structure. These assembly will be extracted for migration into S/4 Hana.

The data from legacy system includes:

1. All active Material Master with the Material Type from the below list:

• IBAU-Maintenance Assembly
• Z750-0 Aggregates PM IBAU (PF1 only)
• ZZ90-Maintenance Assembly (PF1 only)
• ZIBA-Maintenance Assembly (WP1 Only)

2. From the above list, only extract the objects that are assigned to:

• BOM Header (MAST-MATNR)
• BOM Item (STPO-IDNRK)
• Functional Location Construction Type (IFLOT.SUBMT)
• Equipment Construction Type (EQUZ.SUBMT)
• Task List Construction Type (PLKO-ISTRU)

for the relevant plants in scope

The data from legacy system excludes:
1. Construction Types marked for deletion (mara.lvorm = 'x')
2. If the Material in the BOM Header is not assigned as a Construction Type to the Functional Location  / Equipment  / Task List 
3. If the Material in the BOM Item is assigned to a BOM Header from (2).
4. Material assigned to Material BOM Header where all the BOM Items are also part of the Material Type from the above inclusion list (1)

List of source systems and approximate number of records 

Additional Information

Multi-language Requirement

A/CT description will be made available in English.

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

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. A/CT (Material Basic View)

2. A/CT (Short Text)

Note: Each A/CT must have 1 entry for each language in scope: English ,French, Italian, Mandarin, Brazilian Portuguese, German and Spanish

3. A/CT (Characteristics Values Header)

4. A/CT (Characteristics Values Allocation)

Data Cleansing

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

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

Conversion Process

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

 1. Source = PF2/WP2:

2. Source = DCT

 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 A/CTs that need to be created to support the to-be design

Data Privacy and Sensitivity

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

Selection Screen

Data Collection Template (DCT)

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

1. A/CT (Material Basic View) Data Construction Rules

2. A/CT (Characteristics Value Allocation) Data Construction Rules

Extraction Dependencies

List the steps that need to occur before extraction can commence

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 Syniti Migrate 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 Syniti Migrate
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

2. A/CT (Material Basic View) - ECC

2. A/CT (Short Text)

UNION

UNION

UNION

UNION

UNION

UNION

3. A/CT (Characteristics Values Header)

4. A/CT (Characteristics Values Allocation)

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

Pre-Cutover

Configuration

List the Configurations required before loading can commence

Conversion Objects

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

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.
• Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.
• Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
• Not all legacy Construction Type need to be mapped to S/4 HANA Construction Type. If any of the successor objects is dependent on a Construction Type field with no mapped values, this will be an enrichment activity or manual transformation for the successor object to derive the Construction Type.

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log