Status

Page Status

Owner

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

will primarily be used to release maintenance orders, enabling material staging, permit processing, and job scheduling, while preventing further structural changes to

the

planning data.

Some of the key information required to support Maintenance Planning Buckets is not consistently maintained in the source systems.

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

Event-Based
Weekly revisions.

These revision types are typically distinguished by a Revision Type. However, this field is not used in the source systems, despite being a key identifier for differentiating revision behaviour. In addition, revision dates are not maintained even when the they are reused across open transactional data.

From a conversion perspective, the scope includes only the creation of Event-Based revisions into Event-Based Maintenance Planning Buckets. Weekly revisions will be handled during 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., which will be owned by the core Functional team..

That said, to support data continuityHowever, from a conversion perspective, the mapping from legacy revisions to target Maintenance Planning Buckets for Weekly revisions will still be maintained as part of conversion. This ensures that downstream objects - such as Notifications and Work Orders - can correctly map to reference the appropriate target Maintenance Planning Bucket.

The data from legacy system includes:

Given this, and considering the estimated data volume, this object will be fully constructed. However, a source system report will still be required to supplement specific information needed to support the target system requirements.

Thedata from legacy system includes:

Revisions with Event-Based Revision Type (T352R-REVTY = "Event-Based")

Revisions within Maintenance Planning Plants (T352R-IWERK) in scope (Value Mapping: Plant where Maintenance Plant = Yes)

The data from legacy system excludes:

Completed Revisions (T352R-REVTY = "X")
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

Revisions with a Date of Revision End in the future, based on the following conditions:
- Populated Date of Revision Start (T352R-REVBD <> "") and Date of Revision End (T352R-REVED <> "")
- Date of Revision End (T352R-REVED) is in the future (T352R-REVED) > Migration Date (Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9101" and Field Name = "T352R-REVED"))
Revisions with Missing Date of Revision Start (T352R-REVBD = "") or Date of Revision End (T352R-REVED = "") with Open Legacy Work Order Assigned (AUFK-AUFNR)

The data from legacy system excludes:

Completed Revisions (Indicator: Revisions Completed (T352R-REVTY = "X"))
Revisions in the Past (Date of Revision End (T352R-REVED) < Migration Date (Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9101" and Field Name = "T352R-REVED")
Revisions with Missing Date of Revision Start (T352R-REVBD = "") or Date of Revision End (T352R-REVED = "") with NO Open Legacy Work Order Assigned (AUFK-AUFNR)

Note: Open Legacy Work Order (AUFK-AUFNR) Criteria: </Start CR0438> ~~System Status (JEST-STAT) <> TECO (Technically Completed)~~ With Active (JEST-INAC <> 'X') System Status (JEST-STAT) = Created (CRTD) or Released (REL) </End CR0438>

List of Tables to extract for this object is maintained here: Extract Table Register.

List of source systems and approximate number of records.

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
DCT	Maintenance Planning Bucket will be collected via DCT. An initial extract of all relevant Revisions will be provided in google sheet format to assist business in decision making on including any relevant Revision from PF2 and WP2 as Maintenance Planning Buckets. Note: A full Data Construct will be created for Maintenance Planning Bucket as explained in Conversion Scope.	250	S/4HANA	250
DCT	Maintenance Planning Bucket for plants which do not have data existing from PF2 and PF2	50	S/4HANA	50

Additional Information

Multi-language Requirement

Maintenance Planning Bucket does not have multi language support. Maintenance Planning Bucket 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	MAINTENANCEPLANNINGBUCKET	EAM_PLNGBCKT_OBJNR	Object Number of Maintenance Planning Bucket	CHAR	20	System
EAM_PLNGBKT	MAINTENANCEPLANNINGPLANT	IWERK	Maintenance Planning Plant	CHAR	4	Mandatory
EAM_PLNGBKT	MAINTENANCEPLANT	WERKS_D	Plant	CHAR	4	Mandatory
EAM_PLNGBKT	MAINTPLNGBUCKETLABEL	EAM_PLNGBKTLABEL	Label used for identifying the Maintenance Planning Bucket	CHAR	40	Mandatory
EAM_PLNGBKT	MAINTPLANNINGBUCKETDESCRIPTION	EAM_PLNGBKTDESC	Description of the Maintenance Planning Bucket	CHAR	40	Mandatory
EAM_PLNGBKT	MAINTPLANNINGBUCKETTYPE	EAM_PLNGBKTTYPE	Maintenance Planning Bucket Type	CHAR	3	Mandatory
EAM_PLNGBKT	MAINTPLNGBUCKETSTARTDATETIME	EAM_PLNGBKTSTARTDATETIME	Start of the Maintenance Planning Bucket	DEC	15	Mandatory
EAM_PLNGBKT	MAINTPLNGBUCKETENDDATETIME	EAM_PLNGBKTENDDATETIME	End of the Maintenance Planning Bucket	DEC	15	Mandatory
EAM_PLNGBKT	MAINTENANCESYSTEMSTATUSCODE	J_STATUS	Object status	CHAR	5	Mandatory
EAM_PLNGBKT	MAINTENANCEEVENT	REVNI	Revision for Plant Maintenance and Customer Service	CHAR	8	System
EAM_PLNGBKT	PERSONRESPONSIBLE	EAM_PERSONRESP_CHAR8	Person Responsible	CHAR	8	Conditional

2. Maintenance Events

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
IMR__VH

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2Valid Revisions3,000S/4HANA3,000DCTRevisions for plants which do not have data existing from PF2 and PF2nnnS/4HANAnnn

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

EAM_PLNGBKT0EAMPLNGBKTMAINTPLNGBUCKETLABELDescription of 0EAMPLNGBKTEAMNMBROFBUCKETSINADVANCEStart 150End of the

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
EAM_PLNGBKT	MAINTPLANNINGBUCKETUUID	SYSUUID_X	UUID in X form (binary)	16	0	EAM_PLNGBKT	MAINTPLANNINGBUCKETTYPE	EAM_PLNGBKTTYPE	Maintenance Planning Bucket Type	3	0
	MAINTENANCEPLANNINGPLANT	IWERK	Maintenance Planning Plant	CHAR	4
Mandatory
IMR__
VH
MAINTENANCEREVISION
EAM_PLNGBKTLABEL	Label used for identifying the Maintenance Planning Bucket	40	0
REVNI	Revision for Plant Maintenance and Customer Service	CHAR	8	System
IMR__VH	MAINTENANCEEVENTTYPE	DIWPS_REVTY_CORE	Revision Type	CHAR	2	Mandatory
IMR__VH	MAINTPLNGBUCKETLABEL	REVTX	Label used for identifying
EAM_PLNGBKT	MAINTPLANNINGBUCKETDESCRIPTION	EAM_PLNGBKTDESC
the Maintenance Planning Bucket	CHAR	40
Mandatory
IMR_
NROFMAINTPLNGBUCKETSINADVANCE
_
Number of planning buckets the system will create in advance	3	0
VH	MAINTPLANNINGBUCKETDESCRIPTION	EAM_PLNGBKTLABEL	Description
EAM_PLNGBKT	MAINTPLNGBUCKETSTARTDATETIME	EAM_PLNGBKTSTARTDATETIME
of the Maintenance Planning Bucket
CHAR
40
EAM_PLNGBKT	MAINTPLNGBUCKETENDDATETIME	EAM_PLNGBKTENDDATETIME
Mandatory

Note: Each Maintenance Planning Bucket

150EAM_PLNGBKTPERSONRESPONSIBLEEAM_PERSONRESP_CHAR8Person Responsible80EAM_PLNGBKTMAINTENANCEEVENTREVNIRevision for Plant Maintenance and Customer Service80EAM_PLNGBKTMAINTENANCEPLANTWERKS_DPlant40T352RIWERKIWERKMaintenance Planning Plant40T352RREVNRREVNIRevision for Plant Maintenance and Customer Service80

will correspond to one Maintenance Event.

Data Cleansing

ID

Criticality

Error Message/Report Description

Rule

Output

Source System

9101-001

C2

Missing Events-Based Revision Start and End Dates

Events-Based Revision as per Relevancy Criteria where either Start or End Date is not available

Revision Type from Value Mapping: Maintenance Planning Bucket (Old to New Mapping) = ("Events-Based", <blank>)
Revisions missing from Value Mapping: Maintenance Planning Bucket (Old to New Mapping)
Missing Date of Revision Start or Date of Revision End

Maintenance Planning Plant, Revision, Description, Date of Revision Start, Date of Revision End

PF2, WP2

9101-002

C3

Info Report: Non-Relevant Events-Based Revision (Will not be migrated)

Events-Based Revision of in scope Maintenance Plants and falls in any of the criteria below:

Completed (Indicator: Revisions Completed (T352R-REVTY = "X"))
Revisions in the Past (Date of Revision End (T352R-REVED) < Migration Date (Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9101" and Field Name = "T352R-REVED")

Note: These Revisions will not be not migrated. Where necessary, the business can set the Date of Revision End to a future date.

Maintenance Planning Plant, Revision, Description, Date of Revision Start, Date of Revision End, Indicator: Revisions Completed

PF2, WP2

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

Conversion Process

The following represents the high-level process for DCT:

Image Added

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

For sites not on SAP-PF2 or WP2 systems

Image Added

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

Relevant Events-Based Revisions from PF2 and WP2 systems

Data Privacy and Sensitivity

Not Applicable

Extraction

Extract data from a source into Advanced Data Migration and Management (ADMM) . 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 ADMM 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 Advanced Data Migration and Management (ADMM).

The agreed Relevancy criteria is applied to the extracted records as reference point to identify the records that are applicable for the data construction in the DCT.

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 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
MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	Mandatory. Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes
zLegacyREVNR	Legacy Revision for Plant Maintenance and Customer Service	Mandatory. Staging identifier used to uniquely define a Maintenance Planning Bucket. For data originating from WP2/PF2, the value must exist as a revision in PF2/WP2.
MAINTPLNGBUCKETLABEL	Label used for identifying the Maintenance Planning Bucket	Mandatory. The naming convention for Maintenance Planning Bucket will follow the structure: Structure: EVT_Year_Free Text EVT: Event-Based Maintenance Year: 4 Char Year (e.g., 2026) Free Text: Unique description for this bucket Example: EVT_2026_Shutdown 01
MAINTPLANNINGBUCKETDESCRIPTION	Description of the Maintenance Planning Bucket	Mandatory. Ensure that it does not include any of below characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes
zMAINTPLNGBUCKETSTARTDATE

Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System9101-001C1Invalid, Inactive or no Inactive or no Cost Centres linked to RevisionRevision as per Relevancy Criteria assigned with a Cost Centre which does not belong below:
1. Cost Centre (FI) as per Relevancy CriteriaPlant, Revision, DescriptionPF2, WP29101-002C1Invalid, Inactive or no WBS linked to RevisionRevision as per Relevancy Criteria assigned with a WBS which does not belong below:
1. Work Breakdown Structure (PS) as per Relevancy CriteriaPlant, Revision, DescriptionPF2, WP29101-003C1Invalid, Inactive or no Inactive or no Work Centres linked to RevisionRevision as per Relevancy Criteria assigned with a Work Centre which does not belong below:
1. Work Centre as per Relevancy CriteriaPlant, Revision, DescriptionPF2, WP29101-004C1Incomplete 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 DatePF2, 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:

Image Removed

The following represents the high-level process for DCT:

Image Removed

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:

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 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 DescriptionTeam Responsible 1Extract data from source system based on relevancy ruleData Team

Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/setNot 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 BucketEnsure this is set to current date or in the future. No date in the past.date of validity of the Maintenance Planning Bucket Must be in DDMMYYYY format
zEAM_PLNGBKTSTARTTIMEzMAINTPLNGBUCKETSTARTTIME	Start Time of the Maintenance Planning Bucket	Mandatory. Start time of validity of the Maintenance Planning Bucket Must be in HHMMSS format If the user does not provide a value, this will be set to 000000.
zEAM_PLNGBKTENDDATEzMAINTPLNGBUCKETENDDATE	End Date of the Maintenance Planning Bucket	Mandatory. End date of validity of Maintenance Planning Bucket Ensure date is in the futureafter the "Go-Live" Date. Should be later than the Start Date of the Maintenance Planning BuckeBucket Must be in DDMMYYYY format Note: "Go-Live" = "Migration Date" during Mocks
zMAINTPLNGBUCKETENDTIMEzEAM_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 DescriptionTeam ResponsibleNot 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:

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 Advanced Data Migration and Management (ADMM)

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

If the user does not provide a value, this will be set to235959.

PERSONRESPONSIBLE

Person Responsible

Conditional.

Must be a valid Person Responsible
Select supervisor who manages the Maintenance Planning Bucket. Otherwise, leave the field blank.

MAINTENANCEEVENTTYPE

Maintenance Event Type

Mandatory.

Event Type of the Maintenance Event
Needs to be selected from value list (IMAINTEVTYPEVH)

2. Maintenance Planning Bucket (Old to New Mapping) DCT Rules

Field Name	Field Description	Rule
zLegacyIWERK	Legacy Maintenance Planning Plant	Mandatory. Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes
zLegacyREVNR	Legacy Revision for Plant Maintenance and Customer Service	Mandatory. Staging identifier used to uniquely define a Maintenance Planning Bucket. For data originating from WP2/PF2, the value must exist as a revision in PF2/WP2.
zRevisionType	Legacy Revision Type	Mandatory. Allowed Values: Events-Based Weekly Revision
MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	Mandatory. Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes
MAINTPLNGBUCKETLABEL	Label used for identifying the Maintenance Planning Bucket	Mandatory. Label used for identifying the Maintenance Planning Bucket as per Maintenance Planning Bucket DCT (Maintenance Planning Bucket DCT Rules)
MAINTENANCEEVENT	Maintenance Event	Mandatory. New Maintenance Event associated to the Label used for identifying the Maintenance Planning Bucket Note: This is a system-generated field and will be populated post data load to S/4

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

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:

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 Advanced Data Migration and Management (ADMM)

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

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-

Item #Step DescriptionTeam 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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic1--- -S/4 HanaEAM_PLNGBKTMAINTPLANNINGBUCKETUUIDUUID in X form (binary)System Generated2PF2, WP2T352RIWERKMaintenance Planning PlantS/4 HanaEAM_PLNGBKTMAINTENANCEPLANNINGPLANTMaintenance Planning PlantValue Mapping: Plant (Maintenance Plant = Yes)3PF2, WP2T352RIWERKMaintenance Planning PlantS/4 HanaEAM_PLNGBKTMAINTENANCEPLANTPlantValue Mapping: Plant (Maintenance Plant = Yes)4PF2, WP2T352RREVNRRevision for Plant Maintenance and Customer ServiceS/4 HanaEAM_PLNGBKTMAINTPLNGBUCKETLABELLabel used for identifying the Maintenance Planning BucketDirect Mapping5PF2, WP2T352RREVTXRevision descriptionS/4 HanaEAM_PLNGBKTMAINTPLANNINGBUCKETDESCRIPTIONDescription of the Maintenance Planning BucketDirect Mapping6--- -S/4 HanaEAM_PLNGBKTMAINTPLANNINGBUCKETTYPEMaintenance Planning Bucket TypeDefault to "STO" for Event Based Maintenance7PF2, WP2T352RREVBDDate of revision start

S/4 Hana

EAM_PLNGBKT

MAINTPLNGBUCKETSTARTDATETIMEStart of the Maintenance Planning Bucket

Concatenate from source fields of ECC T352R:

REVBD (Date of revision start) + ", " + REVBZ (Time of revision start)

MAINTPLANNINGBUCKETUUID

UUID in X form (binary)

System Generated

Note: To be created using the Custom Load Program. Leave this field blank in the Preload file.

2

DCT

-

MAINTENANCEPLANNINGPLANT

Maintenance Planning Plant

8PF2, WP2T352RREVBZTime of revision start9PF2, WP2T352RREVEDDate of revision end

S/4 Hana

EAM_PLNGBKT

MAINTPLNGBUCKETENDDATETIME

MAINTENANCEPLANNINGPLANT

End of the

Maintenance Planning

Bucket

Concatenate from source fields of ECC T352R:

REVED (Date of revision start) + ", " + REVEZ (Time of revision start)

Plant	Direct Mapping
3	DCT	-	MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	S/4 Hana	EAM_PLNGBKT	MAINTENANCEPLANT	Plant	Direct Mapping
4	DCT	-	MAINTPLNGBUCKETLABEL	Label used for identifying the Maintenance Planning Bucket

10PF2, WP2T352RREVEZTime of revision end11--- -

S/4 Hana

EAM_PLNGBKT

MAINTENANCESYSTEMSTATUSCODEObject statusDefault to "I0001" for CRTD12

MAINTPLNGBUCKETLABEL	Label used for identifying the Maintenance Planning Bucket	Direct Mapping
5	DCT

-

MAINTPLANNINGBUCKETDESCRIPTION

Description of the Maintenance Planning Bucket

-

S/4 Hana

EAM_PLNGBKT

MAINTENANCEEVENTRevision for Plant Maintenance and Customer ServiceDefault to "0000000"

MAINTPLANNINGBUCKETDESCRIPTION	Description of the Maintenance Planning Bucket	Direct Mapping
6

13

-

S/4 Hana

EAM_PLNGBKT

PERSONRESPONSIBLEPerson ResponsibleTBD14PF2, WP2T352RIWERK

MAINTPLANNINGBUCKETTYPE	Maintenance Planning Bucket Type	Default to "STO" for Event Based Maintenance
7	DCT	-	zMAINTPLNGBUCKETSTARTDATE	Start Date of the Maintenance Planning Bucket

Maintenance Planning Plant

S/4 Hana

T352R

EAM_PLNGBKT

IWERK

MAINTPLNGBUCKETSTARTDATETIME

Start of the Maintenance Planning

PlantValue Mapping: Plant (Maintenance Plant = Yes)

Bucket

If zMAINTPLNGBUCKETSTARTTIME does not have a value in DCT, default to 000000.

Concatenate from source fields of DCT EAM_PLNGBKT:

zMAINTPLNGBUCKETSTARTDATE
", "
zMAINTPLNGBUCKETSTARTTIME

8

DCT

-

zMAINTPLNGBUCKETSTARTTIME

Start Time of the Maintenance Planning Bucket

9

DCT

-

zMAINTPLNGBUCKETENDDATE

End Date of the Maintenance Planning Bucket

15--- -S/4 HanaT352RREVNRRevision for Plant Maintenance and Customer ServiceDefault to "0000000"16--- -

S/4 Hana

T352R

EAM_PLNGBKT

REVTYRevision TypeDefault to "STO" for Event Based Maintenance

2. Maintenance Planning Bucket (DCT)

MAINTPLNGBUCKETENDDATETIME

End of the Maintenance Planning Bucket

If zMAINTPLNGBUCKETENDTIME does not have a value in DCT, default to 235959.

Concatenate from source fields of DCT EAM_PLNGBKT:

zMAINTPLNGBUCKETENDDATE
", "
zMAINTPLNGBUCKETENDTIME

10

DCT

-

zMAINTPLNGBUCKETENDTIME

End Time of the Maintenance Planning Bucket

11

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

-

S/4 Hana

EAM_PLNGBKT

MAINTPLANNINGBUCKETUUIDUUID in X form (binary)System Generated

MAINTENANCESYSTEMSTATUSCODE	Object status	Default to "I0002" for Released
12	-	-	-	-

2DCTEAM_PLNGBKTIWERKMaintenance Planning Plant

S/4 Hana

EAM_PLNGBKT

MAINTENANCEPLANNINGPLANT

MAINTENANCEEVENT

Maintenance Planning PlantDirect Mapping3DCTEAM_PLNGBKTIWERK

Revision for Plant Maintenance and Customer Service

System Generated

Note: To be created using the Custom Load Program. Leave this field blank in the Preload file.

13

-

Maintenance Planning Plant

S/4 Hana

EAM_PLNGBKT

MAINTENANCEPLANT

PERSONRESPONSIBLE

Plant

Person Responsible

Value Mapping: Plant (Maintenance Plant = Yes)

Direct Mapping

2. Maintenance Events

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	-	MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant

4PF2, WP2T352RREVNRLabel used for identifying the Maintenance Planning BucketS/4 HanaEAM_PLNGBKTMAINTPLNGBUCKETLABELLabel used for identifying the Maintenance Planning BucketDirect Mapping5PF2, WP2T352RREVTXRevision description

S/4 Hana

EAM

IMR__

PLNGBKT

VH

MAINTPLANNINGBUCKETDESCRIPTION

MAINTENANCEPLANNINGPLANT

Description of the

Maintenance Planning

Bucket

Plant

Direct Mapping

6

2

-

S/4 Hana

EAM

IMR__

PLNGBKT

VH

MAINTPLANNINGBUCKETTYPE

MAINTENANCEREVISION

Maintenance Planning Bucket TypeDefault to "STO" for Event Based Maintenance7PF2, WP2T352RREVBDDate of revision start

Revision for Plant Maintenance and Customer Service	System Generated
3	DCT	-	MAINTENANCEEVENTTYPE	Revision Type	S/4 Hana

EAM

IMR__

PLNGBKT

VH

MAINTPLNGBUCKETSTARTDATETIMEStart of the Maintenance Planning Bucket

Concatenate from source fields of ECC T352R:

REVBD (Date of revision start) + ", " + REVBZ (Time of revision start)

8PF2, WP2T352RREVBZTime of revision start

MAINTENANCEEVENTTYPE	Revision Type	Direct Mapping
4	DCT	-	MAINTPLNGBUCKETLABEL	Label used for identifying the Maintenance Planning Bucket

9PF2, WP2T352RREVEDDate of revision end

S/4 Hana

EAM

IMR__

PLNGBKT

VH

MAINTPLNGBUCKETENDDATETIME

MAINTPLNGBUCKETLABEL

Label used for identifying

End of

the Maintenance Planning Bucket

Concatenate from source fields of ECC T352R:

REVED (Date of revision start) + ", " + REVEZ (Time of revision start)

10PF2, WP2T352RREVEZTime of revision end11--- -S/4 HanaEAM_PLNGBKTMAINTENANCESYSTEMSTATUSCODEObject statusDefault to "I0001" for CRTD12--- -S/4 HanaEAM_PLNGBKTMAINTENANCEEVENTRevision for Plant Maintenance and Customer ServiceDefault to "0000000"13--- -S/4 HanaEAM_PLNGBKTPERSONRESPONSIBLEPerson ResponsibleTBD14PF2, WP2T352RIWERKMaintenance Planning PlantS/4 HanaT352RIWERKMaintenance Planning PlantValue Mapping: Plant (Maintenance Plant = Yes)15--- -S/4 HanaT352RREVNRRevision for Plant Maintenance and Customer ServiceDefault to "0000000"16--- -S/4 HanaT352RREVTYRevision TypeDefault to "STO" for Event Based Maintenance

Transformation Mapping

Mapping Table NameMapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commenceItem #Step DescriptionTeam 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

Completeness

TaskAction

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

TaskAction

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

Completeness

TaskAction

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

TaskAction

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:

Execute the automated data load into target system using load tool or product 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 DescriptionTeam 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 Item1Plant2Planning Bucket Type

Conversion Objects

Object #Preceding Object Conversion ApproachN/A

Error Handling

Error TypeError DescriptionAction Taken

Direct Mapping
5	DCT	-	MAINTPLANNINGBUCKETDESCRIPTION	Description of the Maintenance Planning Bucket	S/4 Hana	IMR__VH	MAINTPLANNINGBUCKETDESCRIPTION	Description of the Maintenance Planning Bucket	Direct Mapping

Note: Each Maintenance Planning Bucket will correspond to one Maintenance Event.

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

Transformation Mapping

Mapping Table Name	Mapping Table Description
OTH_Migration_Date Relevant Values A2D	Dates to be defaulted for A2D objects for each Migration Cycle
Plant	Old to New Plant Mapping
Maintenance Planning Bucket (Old to New Mapping)	Old Revision to Maintenance Planning Bucket Mapping

List of Transformation Mappings with additional details is maintained here: Transformation Mappings.

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

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:

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

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

Note: A custom load program is required and is to be developed by the SyWay Development Team.

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	T001W-Plants/Branches
2	T399I-Planning Plant
3	TJ02-System status
4	IMAINTEVTYPEVH-Maintenance Event Type

Conversion Objects

Object #	Preceding Object Conversion Approach
	Not Applicable

Error Handling

Error Type	Error Description	Action Taken
Configuration	Invalid Plant	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Planning Plant	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid System Status	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Maintenance Maintenance Event Type	Engage Functional team to expedite and fix the error in the system

Post-Load Validation

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

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.
Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
Weekly Revisions are not in Conversion Scope. However, to support the data conversion of downstream objects such as Work Orders, the mapping from legacy Weekly Revisions to target Maintenance Planning Buckets will still be maintained within the data value mapping.
A Maintenance Planning Bucket can only contain a single Maintenance Event. Each revision in the source system will be linked to a single Maintenance Planning Bucket and each Maintenance Planning Bucket will correspond to one Maintenance Event.

Post-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

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

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

Change log

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Apr 19, 2026	Actor	Type	Activity	Version
Approved	MOUSSA-ext, Eva	State	changed state to Approved at 11:24 pm	v116
Revision under Review	MOUSSA-ext, Eva	State	gave Minor change approval at 11:24 pm v. 116 CR0438 approved
Revision under Review	MOUSSA-ext, Eva	State	changed state to Revision under Review at 11:24 pm v. 116 CR0438 approved	v116
Apr 13, 2026
Revision in Progress	ERGUIZA-ext, Pinky Love	Comment	commented 11:59 am Updated. Please check
Revision in Progress	ERGUIZA-ext, Pinky Love	Edit	updated the page at 11:59 am
	PUN-ext, Eddy	Comment	commented 9:04 am As there are many more status apart from TECO (eg CLSD, DLFL etc)
	PUN-ext, Eddy	Comment	commented 9:03 am Better use this: Open Work Orders (AUFK-AUFNR) with Active (JEST-INAC <> 'X') System Status (JEST-STAT) = Created (CRTD) or Released (REL).
From Mar 25, 2026 to Apr 10, 2026
	ERGUIZA-ext, Pinky Love	Edit	updated the page at 5:09 am

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 28

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

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

Selection Screen

Data Collection Template (DCT)

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

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

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

Post-Load Validation