You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

Status

  Revision in Progress

Owner

TEE-ext, Paul 

Stakeholders

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

01 - Time-Based Strategy

-Description:
Used for assets that require preventive maintenance at fixed time intervals.
-Application:
Maintenance cycles defined in days, weeks, months, or years.
-Example:
Lubrication every 3 months, inspection every 12 months.

02 - Performance-Based Strategy

-Description:
Used for assets that require preventive maintenance based on operational usage or performance.
-Application:
Maintenance cycles defined in measured units such as operating hours, kilometres, or production counts.
-Example:
Preventive maintenance every 2,000 operating hours.

03 - Corrective Strategy 

-Description:
Used to manage corrective or run-to-failure maintenance and to differentiate task lists created for repeated corrective activities.
-Application:
This strategy contains a dummy package (not assigned in task lists) and acts as a placeholder to enable reuse of corrective task lists.
-Example:
Standard repair procedures applied upon failure.

04 - Turnaround/Shutdown Strategy

-Description:
Used for assets undergoing maintenance during planned turnarounds or shutdowns.
-Application:
Defines repetitive and pre-planned maintenance work that occurs during turnaround/shutdown periods.
-Example:
Boiler overhaul during annual plant shutdown.


List of source systems and approximate number of records 

SourceScope

Source Approx No. of Records

Target SystemTarget Approx No. of Records

DCT

An initial extract will be provided to business to evaluate.

Additional data/records may be required and these will be constructed via DCT.

Enrichment of in-scope data may be required and will be added via transformation rules (business/technical).

352

S/4HANA

352

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.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable




Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
T351STRATSTRATMaintenance StrategyCHAR6Mandatory
T351TKTEXTTXWSTRADescription of maintenance strategyCHAR30Mandatory
T351ZEIEHDZEIEHUnit for the performance of maintenance tasksUNIT3

Mandatory

Config Table: T006

T351TOLE1TOLERPLUSTolerance for Late Completion (%)NUMC3 Conditional
T351TOLE2TOLERNEGTolerance for Early Completion (%)NUMC3Conditional
T351VERS1VERSCHPLUSShift Factor for Late CompletionNUMC3Conditional
T351VERS2VERSCHNEGShift Factor for Early CompletionNUMC3Conditional
T351TERMKTERMKNZScheduling indicatorCHAR1Mandatory
T351HORIZHORIZONTCall horizon for maintenance plan callsNUMC3Conditional
T351HORIZ_QUALIFIEREAM_CC_CALLHORIZON_QUALIFIERCalculation Type of Call HorizonCHAR1Conditional
T351FABKLFABKLFactory calendar keyCHAR2NU
T351AUTHGREAM_AUTH_GROUPAuthorization GroupCHAR4NU
T351PZAEHLPAKETZAEHLMaintenance Package NumberNUMC2Mandatory
T351PZEIEHDZEIEHUnit for the performance of maintenance tasksUNIT3

Mandatory

Config Table: T006

T351POFFZTDZYK_OFFZTStart offset of a time-based maintenance packageFLTP16(16)Conditional
T351POFFLSDZYK_OFFLSStart offset of a performance-based maintenance packageFLTP16(16)NU
T351XPUFFPPUFF_VORLLead Float in DaysNUMC3NU
T351XPUFFNPUFF_NACHLFollow-up float in daysNUMC3NU
T351XKTEX1TXZYKLUSText for maintenance package/cycle (time/performance)CHAR30Mandatory
T351XKZYK1KTEXTZYKShort text for the maintenance cycle (time/performance)CHAR2Mandatory
T351XKTXHIKTEXTHIERShort text of the maintenance package hierarchyCHAR2Mandatory


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
1017-001C1Maintenance Strategy not used in Task Lists or Maintenance PlansMaintenance Strategy as per Relevancy Criteria however not assigned to below:
1. Task Lists as per Relevancy Criteria
2. Maintenance Plans as per Relevancy Criteria		Maintenance StrategyPF2, WP2
1017-002C3Duplicate Maintenance Strategy by DescriptionMaintenance Strategy as per Relevancy Criteria where the Maintenance Strategy Description exist more than once for a Maintenance Strategy Code.Maintenance Strategy DescriptionPF2, WP2
1017-003C1Missing Maintenance Strategy DescriptionsMaintenance Strategy as per Relevancy Criteria where there are blank Maintenance Strategy Descriptions.Maintenance Strategy DescriptionPF2, WP2

Informal Words **

Group 1

Group 2

Group 3

Group 4

Group 5

*DNU

Delete

donot

Formerly

Old #

..

Deletion

DONT USE

From

Old[ ]

/

DELISTED

DON'T USE

Incorrect

PLEASE USE

?

Discontinued

Dup Use

Invalid

Pls Use

@

Disposable

DUPLICATE

New

Previously

^

DNU

-DUPLICATE

NOT ACTIVE

Replace

+

Do Not

DUPLICATION

not in use

Replaced

++

Do Not Re

Duplicidad

Not Used

RESERVED

£

Do Not Sell

Duplikat

NOT VALID

Retired

Defective

Do Not Use

Former

Obsolete

ZZDEL


Conversion Process

The high-level process 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

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

Extraction Run Sheet

Req #Requirement DescriptionTeam Responsible


Not Applicable


Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue 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.

Maintenance Strategy DCT Rules

Field NameField DescriptionRule
LegacySTRATLegacy StrategyMandatory(Key)
LegacyKTEXTLegacy DescriptionMandatory
LegacyZEIEHLegacy Unit for the performance of maintenance tasksMandatory
STRATStrategyS4/HANA value
KTEXTDescriptionS4/HANA value
ZEIEHUnit for the performance of maintenance tasksValues must exist in config table T006
LegacyHORIZLegacy Call horizon for maintenance plan calls
LegacyHORIZ_QUALIFIERLegacy Calculation Type of Call Horizon
LegacyLEIEHLegacy Maintenance strategy activity unit
LegacyZYK1GLegacy Total cycle duration of a maintenance strategy
LegacyZYK2GLegacy Total cycle duration of a maintenance strategy
LegacyZYK1KLegacy Smallest step between two maintenance packages
LegacyZYK2KLegacy Smallest step between two performance-based MaintPackages
LegacyANZP1Legacy Number of MaintPackages in the MaintStrategy
LegacyANZP2Legacy Number of MaintPackages in the MaintStrategy (performance)
LegacyTOLE1Legacy Tolerance for Late Completion (%)
LegacyTOLE2Legacy Tolerance for Early Completion (%)
LegacyVERS1Legacy Shift Factor for Late Completion
LegacyVERS2Legacy Shift Factor for Early Completion
LegacyTERMKLegacy Scheduling indicator
LegacyFABKLLegacy Factory calendar key
LegacyAUTHGRLegacy Authorization Group

Extraction Dependencies

Item #Step DescriptionTeam Responsible

Not Applicable




Transformation

The legacy data is maintained in Syniti Data Construction page. All mapping is performed in Syniti Data Construction page.

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

1

Obtain DCT Sign-off from Business

SyWay A2D Data Team

2

<Add steps from Syniti Migrate here>

SyWay A2D Data Team

3

Review and Validate Error and Preload Reports

SyWay A2D Data Team

4

Generate Load Files

SyWay A2D Data Team


Transformation Rules

All transformation and mapping is performed in Syniti Data Construction page.

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic




















List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

All transformation and mapping is performed in Syniti Data Construction page.
Mapping Table NameMapping Table Description


Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible

1

Ensure DCT completeness

Business & SyWay A2D Data Team

2

T006 configuration must be completed

Business & SyWay A2D Data Team


Pre-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

Conversion Accuracy

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

TaskAction

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

TaskAction

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:

  1. Execute the automated data load into target system using load tool or produce 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

Item #Step DescriptionTeam Responsible
1Go to <Load Tool>SyWay A2D Data Team
2Load 3 records for Maintenance Strategy to validate if data is loaded successfully without errorsSyWay A2D Data Team
3Proceed with full load if step 2 is validatedSyWay A2D Data Team
4Validate few records loaded by accessing standard transactions from S/4HNA E.g. IP12 SyWay A2D Data Team
5Generate post load report if step 4 is validatedSyWay A2D Data Team


Load Phase and Dependencies

Configuration

Item #Configuration Item
1T006 - Units of Measurement details
2TFACD - Factory calendar definition details
3T370B - Technical object authorization group details

Conversion Objects

Object #Preceding Object Conversion Approach

list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)




Error Handling

Error TypeError DescriptionAction Taken







Post-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

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

TaskAction

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

TaskAction

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.
  • Maintenance Strategy is in scope based on data design and any exception requested by business.
  • Valid legacy data objects dependent on S4/HANA strategies have relevant S4/HANA strategy/packages mapped


See also

Change log

Version Published Changed By Comment
CURRENT (v. 23) 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.

  • No labels