Status	Revision in Progress
Owner	TEE-ext, Paul
Stakeholders	WELENSKY-ext, Dave ERGUIZA-ext, Pinky Love 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.

No data from legacy system will be migrated and all new strategies will be constructed using DCT.

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.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
DCT	All Maintenance Strategy will be constructed using 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
T351T	SPRAS	SPRAS	Language Key	LANG	1	Mandatory
T351T	KTEXT	TXWSTRA	Description of maintenance strategy	CHAR	30	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 Package

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
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
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 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

All data will be constructed for Maintenance Strategy using DCT.

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

Data Privacy and Sensitivity

Extraction

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 all legacy Maintenance Strategy data. This includes Maintenance Strategy, Maintenance Strategy Texts, Maintenance Package, Maintenance Strategy Package Texts (T351, T351T, T351P, T351X). The data will not be migrated but used for mapping of old to new Maintenance Strategy.	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.

Maintenance Strategy DCT Rules

Maintenance Strategy

Field Name	Field Description	Rule
STRAT	Strategy	Maintenance Strategies shall follow the below Mask XX_XXX where: XX = As per the Maintenance strategy defined below: 01 - Time-Based Strategy 02 - Performance-Based Strategy 03 - Corrective Strategy 04 - Turnaround/Shutdown Strategy XXX = Sequential Number starting 001
ZEIEH	Unit for the performance of maintenance tasks	Must not be blank Must reference active Units of Measurement in config (T006)
TOLE1	Tolerance for Late Completion (%)	Default to 0 unless provided by business
TOLE2	Tolerance for Early Completion (%)	Default to 0 unless provided by business
VERS1	Shift Factor for Late Completion	Default to 0 unless provided by business
VERS2	Shift Factor for Early Completion	Default to 0 unless provided by business
TERMK	Scheduling indicator	If the Maintenance Strategy is Time Based then Scheduling Indicator = TIME If the Maintenance Strategy is Performance Based then the Scheduling Indicator = Activity The Time Based or Performance based can be identified based on the Naming Convention of the strategy
HORIZ	Call horizon for maintenance plan calls	Default to 100 unless provided by business
HORIZ_QUALIFIER	Calculation Type of Call Horizon	Default to "%"

Strategy Text

Field Name

Field Description

Rule

STRAT

Strategy

Must reference STRAT from Maintenance Strategy

SPRAS

Language Key

Must not be blank.

Must reference active Language Key in config (T002)

KTEXT

Description

Must not be blank

Maintenance Package

Field Name	Field Description	Rule
STRAT	Strategy	Must reference STRAT from Maintenance Strategy
ZAEHL	Maintenance Package Number	Must not be blank. Numeric values only. Sequential ascending values only.
ZEIEH	Unit for the performance of maintenance tasks	Must not be blank. Must reference active Units of Measurement in config (T006)
OFFZT	Start offset of a time-based maintenance package
KTEX1	Text for maintenance package/cycle (time/performance)	Must not be blank. Refer FLOC and EQUIP MDS for Multilingual Description rules Refer FLOC and EQUIP MDS for Restricted chars rules
KZYK1	Short text for the maintenance cycle (time/performance)	Must not be blank. Refer FLOC and EQUIP MDS for Multilingual Description rules Refer FLOC and EQUIP MDS for Restricted chars rules
KTXHI	Short text of the maintenance package hierarchy	Must not be blank. Refer FLOC and EQUIP MDS for Multilingual Description rules Refer FLOC and EQUIP MDS for Restricted chars rules

Maintenance Package Texts

Field Name	Field Description	Rule
STRAT	Strategy	Must reference STRAT from Maintenance Strategy
PAKET	Maintenance Package Number	Must not be blank. Numeric values only. Sequential ascending values only.
SPRAS	Language Key	Must not be blank. Must reference active Language Key in config (T002)
KTEX1	Text for maintenance package/cycle (time/performance)	Must not be blank
KZYK1	Short text for the maintenance cycle (time/performance)	Must not be blank
KTXHI	Short text of the maintenance package hierarchy	Must not be blank

Extraction Dependencies

No extraction of legacy data will be done as all data will be constructed.

Item #	Step Description	Team Responsible
Not Applicable

Transformation

All data will be constructed with the target values. No transformation is required.

The data is maintained in Syniti Data Construction page.

Transformation Run Sheet

Item #	Step Description	Team Responsible
	Not Applicable

Transformation Rules

Rule #

Source system

Source Table

Source Field

Source Description

Target System

Target Table

Target Field

Target Description

Transformation Logic

1

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.

Validation:

Cannot have duplicate records based on corresponding language text (example: 2 Maintenance Strategy must not have the same Description in English, or 2 Maintenance Strategy must not have the same Description in Spanish)
Text must be translated according to the language key (example: English text cannot be assigned to French language key)

2

DCT

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.

Validation:

Cannot have duplicate records based on corresponding language text (example: 2 Maintenance Strategy must not have the same Description in English, or 2 Maintenance Strategy must not have the same Description in Spanish)
Text must be translated according to the language key (example: English text cannot be assigned to French language key)

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
	Not Applicable

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:

Mandatory Fields
Field and Value Mapping Correctness
Null Checks
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 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	Syniti will provide load file	Syniti
3	Go to <Load Tool>	SyWay A2D Data Team/Syniti
4	Load 3 records for Maintenance Strategy for function (IP11) to validate if data is loaded successfully without errors	SyWay A2D Data Team/Syniti
5	Proceed with full load if step 4 is validated	SyWay A2D Data Team/Syniti
6	Validate few records loaded by accessing standard transactions from S/4HNA E.g. IP12	SyWay A2D Data Team/Syniti
7	Generate post load report if step 6 is validated	SyWay A2D Data Team/Syniti

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	Unit of Measure

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

Change log

Version	Published	Changed By	Comment
CURRENT (v. 80)	Apr 02, 2026 13:43	ERGUIZA-ext, Pinky Love	Changed Owner to Iesha
v. 205	Mar 03, 2026 13:16	TEE-ext, Paul
v. 204	Mar 03, 2026 12:03	TEE-ext, Paul
v. 203	Mar 03, 2026 08:57	TEE-ext, Paul
v. 202	Mar 03, 2026 08:29	TEE-ext, Paul
v. 201	Mar 03, 2026 06:44	TEE-ext, Paul
v. 200	Mar 03, 2026 06:31	TEE-ext, Paul
v. 199	Mar 03, 2026 06:26	TEE-ext, Paul
v. 198	Feb 27, 2026 12:45	TEE-ext, Paul
v. 197	Feb 27, 2026 12:30	TEE-ext, Paul

Go to Page History

Workflow history

Title	Last Updated By	Updated	Status
There are no pages at the moment.

Apr 02, 2026	Actor	Type	Activity	Version
Revision in Progress	ERGUIZA-ext, Pinky Love	Edit	updated the page at 1:43 pm Changed Owner to Iesha
Revision in Progress	ERGUIZA-ext, Pinky Love	State	changed state to Revision in Progress at 11:43 am	v206
Mar 24, 2026
Approved	TAN-ext, Charmaine	State	changed state to Approved at 9:15 am (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v205
Lead Approval	TAN-ext, Charmaine	State	gave Minor change approval at 9:15 am [PMO Comments] Conversion Spec completed as per CS register and functional review completed
Mar 05, 2026
	MOUSSA-ext, Eva	State	changed expiry date to '12 Mar, 2026 12:11 pm' at 12:11 pm
	MOUSSA-ext, Eva	State	changed state to Lead Approval at 12:11 pm	v205
Tech Review	MOUSSA-ext, Eva	State	gave Syniti Team Review approval at 12:11 pm v. 205 approved, CR0378
		State	changed expiry date to '10 Mar, 2026 12:11 pm' at 12:11 pm
		State	changed state to Tech Review at 12:11 pm	v205

Workflow history

Space shortcuts

Page tree

CNV-1017 Maintenance Strategy

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history