Status
Owner	ERGUIZA-ext, Pinky Love
Stakeholders	PUN-ext, Eddy JOSHI-ext, Aditya TEE-ext, Paul MOUSSA-ext, Eva LEIGHTON-ext, Dean HEARD-ext, Kevin DUNNE-ext, Al

Purpose

The purpose of this document is to define the conversion approach to create Maintenance Planning Bucket in S/4 HANA.

A Maintenance Planning Bucket is a logical container or grouping tool used by maintenance planners to organize and manage maintenance orders and notifications for a specific time period and scope. The scope of a planning bucket includes time, but also other important attributes of the maintenance jobs.

Conversion Scope

The scope of this document covers the approach for converting active Revision from Legacy Source Systems into Maintenance Planning Bucket in S/4HANA.

In Syensqo, Maintenance Planning Buckets are primarily used to release maintenance orders, enabling material staging, permit processing, and job scheduling, while preventing further structural changes to the planning data.

There are currently two types of revisions in the source systems:

• Event-Based
• Weekly revisions.

The conversion scope will include only the migration of Event-Based revisions into Maintenance Planning Buckets. Weekly revisions will be handled as part of cutover activities and triggered via batch jobs.

However, from a conversion perspective, the mapping from legacy to target Maintenance Planning Buckets for Weekly revisions will still be maintained. This ensures that downstream objects - such as Notifications and Work Orders - can correctly map to the target Maintenance Planning Bucket.

The data from legacy system includes:

1. Revisions with Event-Based Revision Type (T352R-REVTY = "Event-Based")
2. Revisions within Maintenance Plants (T352R-IWERK) in scope (Value Mapping: Plant where Maintenance Plant = Yes)

The data from legacy system excludes:

1. Completed Revisions (T352R-REVTY = "X")
2. Revisions in the Past
   • Start Date in the Past (T352R-REVBD < Migration Date)
   • End Date in the Past (T352R-REVBD) < Migration Date

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	Valid Revisions	3,000	S/4HANA	3,000
DCT	Revisions for plants which do not have data existing from PF2 and PF2	nnn	S/4HANA	nnn

Additional Information

Multi-language Requirement

Revision does not have multi language support. Revision text will be migrated using EN logon.

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

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
EAM_PLNGBKT	MAINTPLANNINGBUCKETUUID	SYSUUID_X	UUID in X form (binary)	16	0	Mandatory
EAM_PLNGBKT	MAINTPLANNINGBUCKETTYPE	EAM_PLNGBKTTYPE	Maintenance Planning Bucket Type	3	0
EAM_PLNGBKT	MAINTENANCEPLANNINGPLANT	IWERK	Maintenance Planning Plant	4	0
EAM_PLNGBKT	MAINTPLNGBUCKETLABEL	EAM_PLNGBKTLABEL	Label used for identifying the Maintenance Planning Bucket	40	0
EAM_PLNGBKT	MAINTPLANNINGBUCKETDESCRIPTION	EAM_PLNGBKTDESC	Description of the Maintenance Planning Bucket	40	0
EAM_PLNGBKT	NROFMAINTPLNGBUCKETSINADVANCE	EAM_NMBROFBUCKETSINADVANCE	Number of planning buckets the system will create in advance	3	0
EAM_PLNGBKT	MAINTPLNGBUCKETSTARTDATETIME	EAM_PLNGBKTSTARTDATETIME	Start of the Maintenance Planning Bucket	15	0
EAM_PLNGBKT	MAINTPLNGBUCKETENDDATETIME	EAM_PLNGBKTENDDATETIME	End of the Maintenance Planning Bucket	15	0
EAM_PLNGBKT	PERSONRESPONSIBLE	EAM_PERSONRESP_CHAR8	Person Responsible	8	0
EAM_PLNGBKT	MAINTENANCEEVENT	REVNI	Revision for Plant Maintenance and Customer Service	8	0
EAM_PLNGBKT	MAINTENANCEPLANT	WERKS_D	Plant	4	0
T352R	IWERK	IWERK	Maintenance Planning Plant	4	0
T352R	REVNR	REVNI	Revision for Plant Maintenance and Customer Service	8	0

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
9101-001	C1	Invalid, Inactive or no Inactive or no Cost Centres linked to Revision	Revision as per Relevancy Criteria assigned with a Cost Centre which does not belong below: 1. Cost Centre (FI) as per Relevancy Criteria	Plant, Revision, Description	PF2, WP2
9101-002	C1	Invalid, Inactive or no WBS linked to Revision	Revision as per Relevancy Criteria assigned with a WBS which does not belong below: 1. Work Breakdown Structure (PS) as per Relevancy Criteria	Plant, Revision, Description	PF2, WP2
9101-003	C1	Invalid, Inactive or no Inactive or no Work Centres linked to Revision	Revision as per Relevancy Criteria assigned with a Work Centre which does not belong below: 1. Work Centre as per Relevancy Criteria	Plant, Revision, Description	PF2, WP2
9101-004	C1	Incomplete Revision Start and End Dates	Revision as per Relevancy Criteria where either Start or End Date is not available With Start Date but No End Date With No Start Date but with End Date	Plant, Revision, Description, Start Date, End Date	PF2, WP2

Note: List of Cleansing is maintained here: Conversion Specs Register (DCT & Cleansing Report)

Conversion Process

The high-level process is represented by the diagrams below.

The following represents the high-level process for Source System Extraction:

The following represents the high-level process for DCT:

Collection will be done manually in the Data Collection Template for the following scenarios:

• For sites not on SAP-PF2 or WP2 systems 

Data Privacy and Sensitivity

Not Applicable

Extraction

Extract data from a source into the . There are 2 possibilities:

1. The data exists. connects to the source and loads the data into the repository. There are 3 methods: 
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. 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 Advanced Data Migration and Management (ADMM).

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

1. Maintenance Planning Bucket DCT Rules

Field Name	Field Description	Rule
IWERK	Maintenance Planning Plant	Mandatory.  Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes
EAM_PLNGBKTLABEL	Label used for identifying the Maintenance Planning Bucket	Mandatory.  XXXXX
EAM_PLNGBKTDESC	Description of the Maintenance Planning Bucket	Mandatory.  XXXXX
EAM_PLNGBKTTYPE	Maintenance Planning Bucket Type	Mandatory.  XXXXX
zEAM_PLNGBKTSTARTDATE	Start Date of the Maintenance Planning Bucket	Mandatory.  Start date of validity of the Maintenance Planning Bucket Ensure this is set to  current date or in the future. No date in the past. Must be in DDMMYYYY format
zEAM_PLNGBKTSTARTTIME	Start Time of the Maintenance Planning Bucket	Mandatory.  Start time of validity of the Maintenance Planning Bucket Must be in HHMMSS format
zEAM_PLNGBKTENDDATE	End Date of the Maintenance Planning Bucket	Mandatory.  End date of validity of Maintenance Planning Bucket Ensure date is in the future. Should be later than the Start Date of the Maintenance Planning Bucke Must be in DDMMYYYY format
zEAM_PLNGBKTENDTIME	End Time of the Maintenance Planning Bucket	Mandatory.  End time of validity of the Maintenance Planning Bucket Must be in HHMMSS format

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 ADMM to make the data Target ready:

1. Perform value mapping and data transformation rules. 
1. Legacy values are mapped to the to-be values (this could include a default value)
2. Values are transformed according to the rules defined in Advanced Data Migration and Management (ADMM)
2. 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 – Maintenance Planning Bucket	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	Syniti

Transformation Rules

1. Maintenance Planning Bucket (ECC)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4 Hana	EAM_PLNGBKT	MAINTPLANNINGBUCKETUUID	UUID in X form (binary)	System Generated
2	PF2, WP2	T352R	IWERK	Maintenance Planning Plant	S/4 Hana	EAM_PLNGBKT	MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	Value Mapping: Plant (Maintenance Plant = Yes)
3	PF2, WP2	T352R	IWERK	Maintenance Planning Plant	S/4 Hana	EAM_PLNGBKT	MAINTENANCEPLANT	Plant	Value Mapping: Plant (Maintenance Plant = Yes)
4	PF2, WP2	T352R	REVNR	Revision for Plant Maintenance and Customer Service	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETLABEL	Label used for identifying the Maintenance Planning Bucket	Direct Mapping
5	PF2, WP2	T352R	REVTX	Revision description	S/4 Hana	EAM_PLNGBKT	MAINTPLANNINGBUCKETDESCRIPTION	Description of the Maintenance Planning Bucket	Direct Mapping
6	-	-	-	-	S/4 Hana	EAM_PLNGBKT	MAINTPLANNINGBUCKETTYPE	Maintenance Planning Bucket Type	Default to "STO" for Event Based Maintenance
7	PF2, WP2	T352R	REVBD	Date of revision start	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETSTARTDATETIME	Start of the Maintenance Planning Bucket	Concatenate from source fields of ECC T352R: REVBD (Date of revision start) + ", " + REVBZ (Time of revision start)
8	PF2, WP2	T352R	REVBZ	Time of revision start
9	PF2, WP2	T352R	REVED	Date of revision end	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETENDDATETIME	End of the Maintenance Planning Bucket	Concatenate from source fields of ECC T352R: REVED (Date of revision start) + ", " + REVEZ (Time of revision start)
10	PF2, WP2	T352R	REVEZ	Time of revision end
11	-	-	-	-	S/4 Hana	EAM_PLNGBKT	MAINTENANCESYSTEMSTATUSCODE	Object status	Default to "I0001" for CRTD
12	-	-	-	-	S/4 Hana	EAM_PLNGBKT	MAINTENANCEEVENT	Revision for Plant Maintenance and Customer Service	Default to "0000000"
13	-	-	-	-	S/4 Hana	EAM_PLNGBKT	PERSONRESPONSIBLE	Person Responsible	TBD
14	PF2, WP2	T352R	IWERK	Maintenance Planning Plant	S/4 Hana	T352R	IWERK	Maintenance Planning Plant	Value Mapping: Plant (Maintenance Plant = Yes)
15	-	-	-	-	S/4 Hana	T352R	REVNR	Revision for Plant Maintenance and Customer Service	Default to "0000000"
16	-	-	-	-	S/4 Hana	T352R	REVTY	Revision Type	Default to "STO" for Event Based Maintenance

2. Maintenance Planning Bucket (DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4 Hana	EAM_PLNGBKT	MAINTPLANNINGBUCKETUUID	UUID in X form (binary)	System Generated
2	DCT	EAM_PLNGBKT	IWERK	Maintenance Planning Plant	S/4 Hana	EAM_PLNGBKT	MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	Direct Mapping
3	DCT	EAM_PLNGBKT	IWERK	Maintenance Planning Plant	S/4 Hana	EAM_PLNGBKT	MAINTENANCEPLANT	Plant	Value Mapping: Plant (Maintenance Plant = Yes)
4	PF2, WP2	T352R	REVNR	Label used for identifying the Maintenance Planning Bucket	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETLABEL	Label used for identifying the Maintenance Planning Bucket	Direct Mapping
5	PF2, WP2	T352R	REVTX	Revision description	S/4 Hana	EAM_PLNGBKT	MAINTPLANNINGBUCKETDESCRIPTION	Description of the Maintenance Planning Bucket	Direct Mapping
6	-	-	-	-	S/4 Hana	EAM_PLNGBKT	MAINTPLANNINGBUCKETTYPE	Maintenance Planning Bucket Type	Default to "STO" for Event Based Maintenance
7	PF2, WP2	T352R	REVBD	Date of revision start	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETSTARTDATETIME	Start of the Maintenance Planning Bucket	Concatenate from source fields of ECC T352R: REVBD (Date of revision start) + ", " + REVBZ (Time of revision start)
8	PF2, WP2	T352R	REVBZ	Time of revision start
9	PF2, WP2	T352R	REVED	Date of revision end	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETENDDATETIME	End of the Maintenance Planning Bucket	Concatenate from source fields of ECC T352R: REVED (Date of revision start) + ", " + REVEZ (Time of revision start)
10	PF2, WP2	T352R	REVEZ	Time of revision end
11	-	-	-	-	S/4 Hana	EAM_PLNGBKT	MAINTENANCESYSTEMSTATUSCODE	Object status	Default to "I0001" for CRTD
12	-	-	-	-	S/4 Hana	EAM_PLNGBKT	MAINTENANCEEVENT	Revision for Plant Maintenance and Customer Service	Default to "0000000"
13	-	-	-	-	S/4 Hana	EAM_PLNGBKT	PERSONRESPONSIBLE	Person Responsible	TBD
14	PF2, WP2	T352R	IWERK	Maintenance Planning Plant	S/4 Hana	T352R	IWERK	Maintenance Planning Plant	Value Mapping: Plant (Maintenance Plant = Yes)
15	-	-	-	-	S/4 Hana	T352R	REVNR	Revision for Plant Maintenance and Customer Service	Default to "0000000"
16	-	-	-	-	S/4 Hana	T352R	REVTY	Revision Type	Default to "STO" for Event Based Maintenance

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

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 tables completeness	SyWay Data Team
2	Ensure all Transformation mappings are up to date.	SyWay 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	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

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

1. Execute the automated data load into target system using load tool or product 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
1	Ensure Pre-load sign-offs are obtained.	SyWay Data team
2	Go to the load tool and select the correct load Program.	SyWay Data team
3	Proceed with Data load.	SyWay Data team
4	Validate few records loaded by accessing standard transactions	SyWay Data team
5	Generate the post load reports in the tool.	SyWay Data team
6	Log errors as defects, if any and address resolutions. Close defects.	SyWay Data team
7	Resolve defects by reupload and re-generate post load reports if necessary.	SyWay 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 Data team

Load Phase and Dependencies

Cutover

Configuration

Item #	Configuration Item
1	Plant
2	Planning Bucket Type

Conversion Objects

Object #	Preceding Object Conversion Approach
	N/A

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

• Maintenance Planning Bucket is in scope based on data design and any exception requested by business.
• Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.

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