| Status | Revision in Progress |
|---|---|
| Owner | |
| Stakeholders | WELENSKY-ext, Dave ERGUIZA-ext, Pinky Love PUN-ext, Eddy 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 Maintenance Strategy in S/4 HANA.
Legacy Plant Maintenance Maintenance Strategy is using a diverse range of formats across the different systems. There are instances where the same Maintenance Strategy is duplicated within and across sources, with informal words. This results in data inconsistency. As per SyWay design, Maintenance Strategy will be standardized.
Conversion Scope
The scope of this document covers the approach for converting active Maintenance Strategy from Legacy Source Systems into S/4HANA following the Maintenance Strategy Master Data Design Standard.
A Maintenance Strategy in SAP defines how and when maintenance tasks should be performed. It’s a core concept in SAP Plant Maintenance (PM) that helps organizations plan preventive maintenance activities efficiently.
Types of strategy (defined by the first 2 characters of the strategy):
| First 2 characters | Strategy Type | Description | Application | Example |
|---|---|---|---|---|
| 01 | Time-Based | Used for assets that require preventive maintenance at fixed time intervals. | Maintenance cycles defined in days, weeks, months, or years. | Lubrication every 3 months, inspection every 12 months. |
| 02 | Performance-Based | Used for assets that require preventive maintenance based on operational usage or performance. | Maintenance cycles defined in measured units such as operating hours, kilometres, or production counts. | Preventive maintenance every 2,000 operating hours. |
| 03 | Corrective | Used to manage corrective or run-to-failure maintenance and differentiate task lists for repeated corrective activities. | Contains a dummy package and acts as a placeholder to enable reuse of corrective task lists. | Standard repair procedures applied upon failure. |
| 04 | Turnaround/Shutdown | Used for assets undergoing maintenance during planned turnarounds or shutdowns. | Defines repetitive and pre-planned maintenance work during turnaround/shutdown periods. | Boiler overhaul during annual plant shutdown. |
There will not be a direct conversion from legacy to S/4 HANA, however there will be a mapping to ensure all the valid and active legacy Maintenance Strategies are considered for data migration.
The data from legacy system includes:
- All Maintenance Strategies defined in the source systems.
The data from legacy system excludes:
- Not applicable since all Maintenance Strategies defined in the source systems are considered valid.
Please see an indication of what will be baselined from source systems below and what will be constructed in the DCT.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
PF2, WP2 | Maintenance Strategy will be collected via DCT. An initial extract of the relevant Maintenance Strategies will be provided in google sheet format to assist business in decision making on including any relevant Maintenance Strategies from PF2 and WP2 as Maintenance Strategy in S/4 HANA. Any additional Maintenance Strategies 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 Maintenance Strategies in the DCT. | 400 | S/4HANA | 400 |
Additional Information
Multi-language Requirement
Maintenance Strategy description will be made available in English.
Multi language is supported for Maintenance Strategy. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Maintenance Strategy.
To view/edit the record in other languages, in the Menu click Goto > Translation and select the required language.
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.Maintenance Strategy
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| T351 | STRAT | STRAT | Maintenance Strategy | CHAR | 6 | Mandatory |
| T351 | ZEIEH | DZEIEH | Unit for the performance of maintenance tasks | UNIT | 3 | Mandatory |
| T351 | TOLE1 | TOLERPLUS | Tolerance for Late Completion (%) | NUMC | 3 | Conditional |
| T351 | TOLE2 | TOLERNEG | Tolerance for Early Completion (%) | NUMC | 3 | Conditional |
| T351 | VERS1 | VERSCHPLUS | Shift Factor for Late Completion | NUMC | 3 | Conditional |
| T351 | VERS2 | VERSCHNEG | Shift Factor for Early Completion | NUMC | 3 | Conditional |
| T351 | TERMK | TERMKNZ | Scheduling indicator | CHAR | 1 | Mandatory |
| T351 | HORIZ | HORIZONT | Call horizon for maintenance plan calls | NUMC | 3 | Conditional |
| T351 | HORIZ_QUALIFIER | EAM_CC_CALLHORIZON_QUALIFIER | Calculation Type of Call Horizon | CHAR | 1 | Conditional |
2. Maintenance Strategy Text
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| T351 | STRAT | STRAT | Maintenance Strategy | CHAR | 6 | Mandatory |
| T351T | SPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
| T351T | KTEXT | TXWSTRA | Description of maintenance strategy | CHAR | 30 | Mandatory |
3.Maintenance Package
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| T351 | STRAT | STRAT | Maintenance Strategy | CHAR | 6 | Mandatory |
| T351P | ZAEHL | PAKETZAEHL | Maintenance Package Number | NUMC | 2 | Mandatory |
| T351P | ZEIEH | DZEIEH | Unit for the performance of maintenance tasks | UNIT | 3 | Mandatory |
| T351P | OFFZT | DZYK_OFFZT | Start offset of a time-based maintenance package | FLTP | 16(16) | Conditional |
4. Maintenance Package Text
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| T351 | STRAT | STRAT | Maintenance Strategy | CHAR | 6 | Mandatory |
| T351P | ZAEHL | PAKETZAEHL | Maintenance Package Number | NUMC | 2 | Mandatory |
| T351X | SPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
| T351X | KTEX1 | TXZYKLUS | Text for maintenance package/cycle (time/performance) | CHAR | 30 | Mandatory |
| T351X | KZYK1 | KTEXTZYK | Short text for the maintenance cycle (time/performance) | CHAR | 2 | Mandatory |
| T351X | KTXHI | KTEXTHIER | Short text of the maintenance package hierarchy | CHAR | 2 | Mandatory |
Note: Each Maintenance Strategy and Maintenance Package must have 1 entry for each language in scope: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish
Maintenance Strategy Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Maintenance Strategy information follows the Master Data Standard document that is located here.
Data Cleansing
No data cleansing is required for Maintenance Strategy in the legacy system. If any cleansing is deemed necessary, it will be performed outside of the system.
As a result, the cleansed Maintenance Strategy 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
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 Maintenance Strategy that need to be created to support the to-be design
The high-level process for DCT 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 Maintenance Strategy that need to be created to support the to-be design
Data Privacy and Sensitivity
Not applicableExtraction
Extract data from a source into the . There are 2 possibilities:
- The data exists. connects to the source and loads the data into the repository. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; 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 the repository. 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
| 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 Maintenance Strategy data with exception of some fields which require transformation as mentioned in the transformation rule.1.Maintenance Strategy DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| STRAT | Strategy | Mandatory. Maintenance Strategies shall follow the below Mask
XXX = Sequential Number starting 001 |
| ZEIEH | Unit for the performance of maintenance tasks | Mandatory. Must reference active Units of Measurement in config (T006) |
| TOLE1 | Tolerance for Late Completion (%) | Conditional. Default to "0" unless provided by business |
| TOLE2 | Tolerance for Early Completion (%) | Conditional. Default to "0" unless provided by business |
| VERS1 | Shift Factor for Late Completion | Conditional. Default to "0" unless provided by business |
| VERS2 | Shift Factor for Early Completion | Conditional. Default to "0" unless provided by business |
| TERMK | Scheduling indicator | Mandatory. If the Maintenance Strategy is Time Based then Scheduling Indicator = "TIME" |
| HORIZ | Call horizon for maintenance plan calls | Conditional. Default to "100" unless provided by business |
| HORIZ_QUALIFIER | Calculation Type of Call Horizon | Conditional. Default to "%" |
2.Strategy Text DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| STRAT | Strategy | Mandatory. Must reference STRAT from Maintenance Strategy |
| SPRAS | Language Key | Mandatory. Must reference active Language Key in config (T002) |
| KTEXT | Description | Mandatory. |
3.Maintenance Package DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| STRAT | Strategy | Mandatory. Must reference STRAT from Maintenance Strategy |
| ZAEHL | Maintenance Package Number | Mandatory. Numeric values only. Sequential ascending values only. |
| ZEIEH | Unit for the performance of maintenance tasks | Mandatory. Must reference active Units of Measurement in config (T006) |
| OFFZT | Start offset of a time-based maintenance package | Conditional. |
4.Maintenance Package Text DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| STRAT | Strategy | Mandatory. Must reference STRAT from Maintenance Strategy |
| PAKET | Maintenance Package Number | Mandatory. Numeric values only. Sequential ascending values only. |
| SPRAS | Language Key | Mandatory. Must reference active Language Key in config (T002) |
| KTEX1 | Text for maintenance package/cycle (time/performance) | Mandatory. Refer FLOC and EQUIP MDS for Multilingual Description rules |
| KZYK1 | Short text for the maintenance cycle (time/performance) | Mandatory. Refer FLOC and EQUIP MDS for Multilingual Description rules |
| KTXHI | Short text of the maintenance package hierarchy | Mandatory. Refer FLOC and EQUIP MDS for Multilingual Description rules |
Extraction Dependencies
No extraction of legacy data will be done as all data will be constructed.
| 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 S4/HANA – Plant Maintenance | Syniti |
| 3 | Go to Process Area Launch and Process the Object – Maintenance Strategy | 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
1.Maintenance Strategy Transformation Rule
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | T351 | STRAT | Maintenance Strategy | S/4HANA | T351 | STRAT | Maintenance Strategy | Direct mapping. A Global Value Mapping (Maintenance Strategy) will be created to reference old Maintenance Strategy. |
| 2 | DCT | T351 | ZEIEH | Unit for the performance of maintenance tasks | S/4HANA | T351 | ZEIEH | Unit for the performance of maintenance tasks | Direct mapping |
| 3 | DCT | T351 | TOLE1 | Tolerance for Late Completion (%) | S/4HANA | T351 | TOLE1 | Tolerance for Late Completion (%) | Direct mapping |
| 4 | DCT | T351 | TOLE2 | Tolerance for Early Completion (%) | S/4HANA | T351 | TOLE2 | Tolerance for Early Completion (%) | Direct mapping |
| 5 | DCT | T351 | VERS1 | Shift Factor for Late Completion | S/4HANA | T351 | VERS1 | Shift Factor for Late Completion | Direct mapping |
| 6 | DCT | T351 | VERS2 | Shift Factor for Early Completion | S/4HANA | T351 | VERS2 | Shift Factor for Early Completion | Direct mapping |
| 7 | DCT | T351 | TERMK | Scheduling indicator | S/4HANA | T351 | TERMK | Scheduling indicator | Direct mapping |
| 8 | DCT | T351 | HORIZ | Call horizon for maintenance plan calls | S/4HANA | T351 | HORIZ | Call horizon for maintenance plan calls | Direct mapping |
| 9 | DCT | T351 | HORIZ_QUALIFIER | Calculation Type of Call Horizon | S/4HANA | T351 | HORIZ_QUALIFIER | Calculation Type of Call Horizon | Direct mapping |
2.Strategy Text Transformation Rule
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | T351T | SPRAS | Language Key | S/4HANA | T351T | SPRAS | Language Key | Direct mapping. Select the appropriate value from a target ready list. |
| 2 | DCT | T351T | KTEXT | Description | S/4HANA | T351T | KTEXT | Description | Value Mapping: OTH_Informal Words and OTH_Informal Characters Review the value mappings for the presence of informal words or invalid characters. If any are identified, replace them with the appropriate standardized values as specified in the mappings. |
3.Maintenance Package Transformation Rule
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | T351P | ZAEHL | Maintenance Package Number | S/4HANA | T351P | ZAEHL | Maintenance Package Number | Direct mapping |
| 2 | DCT | T351P | ZEIEH | Unit for the performance of maintenance tasks | S/4HANA | T351P | ZEIEH | Unit for the performance of maintenance tasks | Direct mapping |
| 3 | DCT | T351P | OFFZT | Start offset of a time-based maintenance package | S/4HANA | T351P | OFFZT | Start offset of a time-based maintenance package | Direct mapping |
4.Maintenance Package Text Transformation Rule
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | T351X | KTEX1 | Description | S/4HANA | T351X | KTEX1 | Description | Value Mapping: OTH_Informal Words and OTH_Informal Characters Review the value mappings for the presence of informal words or invalid characters. If any are identified, replace them with the appropriate standardized values as specified in the mappings. |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
All data will be constructed with the target values. Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
| Mapping Table Name | Mapping Table Description |
|---|---|
| Maintenance Strategy | Old to new Maintenance Strategy |
| OTH_Informal Words | List of Informal Words and the words used to replace |
| OTH_Informal Characters | List of Informal Characters |
Transformation Dependencies
All data will be constructed with the target values. No transformation is required.| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure DCT tables completeness | Syniti |
| 2 | Ensure all Transformation mappings are up to date. | Syniti |
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:
|
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 produce 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 | Obtain DCT Sign-off from Business | SyWay A2D Data Team |
| 2 | Ensure Pre-load sign-offs are obtained. | SyWay A2D Data Team |
| 3 | Proceed with Data load. | SyWay A2D Data Team |
| 4 | Validate few records loaded by accessing standard transactions. | SyWay A2D Data Team |
| 5 | Generate the post load reports in the tool. | SyWay A2D Data Team |
| 6 | Log errors as defects, if any and address resolutions. Close defects. | SyWay A2D Data Team |
| 7 | Generate post load report if step 6 is validated | SyWay A2D Data Team |
| 8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
| 9 | Repeat steps 5 to 7 if necessary. | SyWay A2D Data Team |
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
| 1 | T006-Unit of Measure |
| 2 | T002-Language Key |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| Not Applicable |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Configuration | Invalid Unit of Measure | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Language Key | Engage Functional team to expedite and fix the error in the system |
Invalid Data | Maintenance Package: Invalid Maintenance Strategy | Check whether the Maintenance Strategy exist in Maintenance Strategy table |
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 Maintenance Strategy 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 Maintenance Strategy 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.
- Valid legacy data objects dependent on S4/HANA Maintenance Strategy have relevant S4/HANA strategy/packages mapped
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||