Status
Owner	TEE-ext, Paul
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

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.

The data from legacy system includes:

1. All legacy strategies & packages assigned to valid legacy

• • strategy Task Lists
  • Maintenance Items

The data from legacy system excludes:

1. All legacy strategies & packages NOT assigned to any valid legacy

• • strategy Task Lists
  • Maintenance Items

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

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
T351	STRAT	STRAT	Maintenance Strategy	CHAR	6(0)
T351T	SPRAS	SPRAS	Language Key	LANG	1(0)	Config Table: T002
T351T	KTEXT	TXWSTRA	Description of maintenance strategy	CHAR	30(0)
T351	ZEIEH	DZEIEH	Unit for the performance of maintenance tasks	UNIT	3(0)	Config Table: T006
T351	LEIEH	LEIEH	Maintenance strategy activity unit	UNIT	3(0)	Config Table: T006
T351	ZYK1G	DZYK1_GES	Total cycle duration of a maintenance strategy	FLTP	16(16)
T351	ZYK2G	DZYK2_GES	Total cycle duration of a maintenance strategy	FLTP	16(16)
T351	ZYK1K	DZYK1_GGT	Smallest step between two maintenance packages	FLTP	16(16)
T351	ZYK2K	DZYK2_GGT	Smallest step between two performance-based MaintPackages	FLTP	16(16)
T351	ANZP1	ANZPAK1	Number of MaintPackages in the MaintStrategy	NUMC	2(0)
T351	ANZP2	ANZPAK2	Number of MaintPackages in the MaintStrategy (peformance)	NUMC	2(0)
T351	TOLE1	TOLERPLUS	Tolerance for Late Completion (%)	NUMC	3(0)
T351	TOLE2	TOLERNEG	Tolerance for Early Completion (%)	NUMC	3(0)
T351	VERS1	VERSCHPLUS	Shift Factor for Late Completion	NUMC	3(0)
T351	VERS2	VERSCHNEG	Shift Factor for Early Completion	NUMC	3(0)
T351	TERMK	TERMKNZ	Scheduling indicator	CHAR	1(0)
T351	HORIZ	HORIZONT	Call horizon for maintenance plan calls	NUMC	3(0)
T351	HORIZ_QUALIFIER	EAM_CC_CALLHORIZON_QUALIFIER	Calculation Type of Call Horizon	CHAR	1(0)
T351	FABKL	FABKL	Factory calendar key	CHAR	2(0)	Config Table: TFACD
T351	AUTHGR	EAM_AUTH_GROUP	Authorization Group	CHAR	4(0)	Config Table: T370B

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1	C1	Description must not be blank	KTEXT is blank	STRAT, KTEXT	PF2, WP2, DCT
2	C1	Unit for the performance of maintenance tasks not in T006	ZEIEH is not in T006	STRAT, KTEXT, ZEIEH	PF2, WP2, DCT

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

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

Syniti will extract data from source system based on relevancy rule. This is done only ONCE at the start of the project.

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	Syniti will extract data from source system based on relevancy rule. This is done only ONCE at the start of the project.	Syniti
2	The legacy data will then be used in Syniti Data construction page.	Syniti

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

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 Object data with exception of some fields which require transformation as mentioned in the transformation rule.

Maintenance Strategy DCT Rules

Field Name	Field Description	Rule
LegacySTRAT	Legacy Strategy	Mandatory(Key)
LegacyKTEXT	Legacy Description	Mandatory
LegacyZEIEH	Legacy Unit for the performance of maintenance tasks	Mandatory
STRAT	Strategy	S4/HANA value
KTEXT	Description	S4/HANA value
ZEIEH	Unit for the performance of maintenance tasks	Values must exist in config table T006
LegacyHORIZ	Legacy Call horizon for maintenance plan calls
LegacyHORIZ_QUALIFIER	Legacy Calculation Type of Call Horizon
LegacyLEIEH	Legacy Maintenance strategy activity unit
LegacyZYK1G	Legacy Total cycle duration of a maintenance strategy
LegacyZYK2G	Legacy Total cycle duration of a maintenance strategy
LegacyZYK1K	Legacy Smallest step between two maintenance packages
LegacyZYK2K	Legacy Smallest step between two performance-based MaintPackages
LegacyANZP1	Legacy Number of MaintPackages in the MaintStrategy
LegacyANZP2	Legacy Number of MaintPackages in the MaintStrategy (performance)
LegacyTOLE1	Legacy Tolerance for Late Completion (%)
LegacyTOLE2	Legacy Tolerance for Early Completion (%)
LegacyVERS1	Legacy Shift Factor for Late Completion
LegacyVERS2	Legacy Shift Factor for Early Completion
LegacyTERMK	Legacy Scheduling indicator
LegacyFABKL	Legacy Factory calendar key
LegacyAUTHGR	Legacy Authorization Group

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team 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 Description	Team 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 system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

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

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team 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

The following pre-load validations will be performed by the 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

The following pre-load validations will be performed by the 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:

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 Description	Team Responsible

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item
1	T006  - Units of Measurement 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

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

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

The following post-load validations will be performed by the 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

The following post-load validations will be performed by the 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.
• 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

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

Workflow history