| Status | Revision in Progress |
|---|---|
| Owner | |
| Stakeholders | WELENSKY-ext, DaveERGUIZA-ext, Pinky Love TEE-ext, Paul JOSHI-ext, Aditya VILARES, ines LEIGHTON-ext, Dean Anirudh Lakkad; Aurelia Stefanescu ; [Syniti POD Lead]; [Syniti Consultant] |
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 Construction Type 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 (CT) is created to group assets that share similar construction characteristics and are built using the same components.
- Standardized Maintenance Strategy:
Each CT is linked to a specific maintenance strategy. If the maintenance strategy differs, a separate CT is required.
- BOM-Based Structuring:
CTs are defined based on Bill of Materials (BOMs) that apply across similar asset types. These BOMs outline the construction hierarchy using sub-assemblies.
- FMECA-Driven Classification:
CTs 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.
Construction Type 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 Construction Type in S/4 HANA following the PM Assembly / Construction Type Master Data Design Standard.
The creation of Construction Type follows the endorsed EAM Core Data Design describing the Asset Identification Methodology.
Legacy system did not have the concept of using PM Assembly in the similar manner as S/4 Hana. Hence there is no extraction of Construction Type required from Legacy.
The data from legacy system includes:
- 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)
The data from legacy system excludes:
- Construction Types marked 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 | Construction Type will be collected via DCT. An initial extract of the relevant Construction Type will be provided in google sheet format to assist business in decision making on including any relevant Construction Type from PF2 and WP2 as Construction Type in S/4 HANA. Any additional Construction Type 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 Construction Type in the DCT. Please see an indication of what will be baselined from source systems below and what will be constructed in the DCT. | 150,000 | S/4 HANA | 150,000 |
Additional Information
Multi-language Requirement
Construction Type description will be made available in English.
Multi language is supported for Construction Type. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Construction Type.
Document Management
Not Applicable
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Target Design
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 Construction Type 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).
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| Not Applicable |
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 Construction Types that need to be created to support the to-be design
Data Privacy and Sensitivity
Not ApplicableExtraction
Extract data from a source into Syniti Migrate. There are 2 possibilities:
- The data exists.Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- 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 data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
| Not Applicable |
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:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti Migrate
- 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 Data Team |
2 | In dspMigrate, select the wave – S4/HANA – Plant Maintenance | Syniti |
3 | Go to Process Area Launch and Process the Object – Catalog Profile | Syniti |
4 | Review and Validate Error and Preload Reports | Syniti |
5 | Execute the transformation to prepare the target tables | Syniti |
6 | Validate data from pre-load and error reports | Business/Data owner |
7 | Generate load files | SyWay Data Team |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Record Count | Data team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Data team to verify that all fields below meet pass the checks: 1. Mandatory Fields 2. Field and Value Mapping Correctness 3. Null Checks 4. 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 team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Business to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off 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 |
|---|---|---|
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
| 1 | Number Range |
| 2 | Class Types |
| 3 | Units of Measurement |
| 4 | Material Types |
5 | Industries for materials |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1008 | Catalog Profile |
| 1015 | Characteristics |
| 1009 | Class |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Count | 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 | Data team to verify that the Construction Type 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 Measuring Point 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.
- 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.