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

Compare with Current View Page History

« Previous Version 39 Next »

Status

  Approved

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 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 categories of revisions:

  • 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 cutover activities and triggered via batch jobs, which will be owned by the core Functional team..

That said, to support data continuity, 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 reference the appropriate target Maintenance Planning Bucket.

Many of the key fields required for Maintenance Planning Buckets do not exist in the Revision object in the source systems. 

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.


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
    • End Date in the Past (T352R-REVED < Migration Date)


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2Valid Revisions3,000S/4HANA3,000
DCTRevisions 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

TableFieldData ElementField DescriptionData TypeLengthRequirement
EAM_PLNGBKTMAINTPLANNINGBUCKETUUIDSYSUUID_XUUID in X form (binary)160
EAM_PLNGBKTMAINTPLANNINGBUCKETTYPEEAM_PLNGBKTTYPEMaintenance Planning Bucket Type30
EAM_PLNGBKTMAINTENANCEPLANNINGPLANTIWERKMaintenance Planning Plant40
EAM_PLNGBKTMAINTPLNGBUCKETLABELEAM_PLNGBKTLABELLabel used for identifying the Maintenance Planning Bucket400
EAM_PLNGBKTMAINTPLANNINGBUCKETDESCRIPTIONEAM_PLNGBKTDESCDescription of the Maintenance Planning Bucket400
EAM_PLNGBKTNROFMAINTPLNGBUCKETSINADVANCEEAM_NMBROFBUCKETSINADVANCENumber of planning buckets the system will create in advance30
EAM_PLNGBKTMAINTPLNGBUCKETSTARTDATETIMEEAM_PLNGBKTSTARTDATETIMEStart of the Maintenance Planning Bucket150
EAM_PLNGBKTMAINTPLNGBUCKETENDDATETIMEEAM_PLNGBKTENDDATETIMEEnd of the Maintenance Planning Bucket150
EAM_PLNGBKTPERSONRESPONSIBLEEAM_PERSONRESP_CHAR8Person Responsible80
EAM_PLNGBKTMAINTENANCEEVENTREVNIRevision for Plant Maintenance and Customer Service80
EAM_PLNGBKTMAINTENANCEPLANTWERKS_DPlant40
T352RIWERKIWERKMaintenance Planning Plant40
T352RREVNRREVNIRevision for Plant Maintenance and Customer Service80


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
9101-001C1Incomplete Revision Start and End Dates

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

  1. With Start Date but No End Date
  2. 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:


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


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 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 NameField DescriptionRule
MAINTENANCEPLANNINGPLANTMaintenance Planning Plant

Mandatory. 

Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes

MAINTPLNGBUCKETLABELLabel used for identifying the Maintenance Planning Bucket

Mandatory. 

XXXXX

MAINTPLANNINGBUCKETDESCRIPTIONDescription of the Maintenance Planning Bucket

Mandatory. 

XXXXX

MAINTPLANNINGBUCKETTYPEMaintenance Planning Bucket Type

Mandatory. 

XXXXX

zMAINTPLNGBUCKETSTARTDATEStart 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
zMAINTPLNGBUCKETSTARTTIMEStart Time of the Maintenance Planning Bucket

Mandatory. 

  • Start time of validity of the Maintenance Planning Bucket
  • Must be in HHMMSS format 
zMAINTPLNGBUCKETENDDATEEnd 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
zMAINTPLNGBUCKETENDTIMEEnd 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 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 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 Logic
1--- -S/4 HanaEAM_PLNGBKTMAINTPLANNINGBUCKETUUIDUUID in X form (binary)System Generated
2PF2, 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 Mapping
5PF2, WP2T352RREVTXRevision descriptionS/4 HanaEAM_PLNGBKTMAINTPLANNINGBUCKETDESCRIPTIONDescription of the Maintenance Planning BucketDirect Mapping
6--- -S/4 HanaEAM_PLNGBKTMAINTPLANNINGBUCKETTYPEMaintenance Planning Bucket TypeDefault to "STO" for Event Based Maintenance
7PF2, WP2T352RREVBDDate of revision startS/4 Hana

EAM_PLNGBKTMAINTPLNGBUCKETSTARTDATETIMEStart of the Maintenance Planning Bucket

Concatenate from source fields of ECC T352R:

  • REVBD
  • ", "
  • REVBZ
8PF2, WP2T352RREVBZTime of revision start
9PF2, WP2T352RREVEDDate of revision endS/4 Hana

EAM_PLNGBKTMAINTPLNGBUCKETENDDATETIMEEnd of the Maintenance Planning Bucket

Concatenate from source fields of ECC T352R:

  • REVED
  • ", "
  • REVEZ
10PF2, WP2T352RREVEZTime of revision end
11--- -S/4 HanaEAM_PLNGBKTMAINTENANCESYSTEMSTATUSCODEObject statusDefault to "I0001" for CRTD
12--- -S/4 HanaEAM_PLNGBKTMAINTENANCEEVENTRevision for Plant Maintenance and Customer ServiceDefault to "0000000"
13--- -S/4 HanaEAM_PLNGBKTPERSONRESPONSIBLEPerson ResponsibleTBD
14PF2, 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

2. Maintenance Planning Bucket (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1--- -S/4 HanaEAM_PLNGBKTMAINTPLANNINGBUCKETUUIDUUID in X form (binary)System Generated
2DCTEAM_PLNGBKTMAINTENANCEPLANNINGPLANTMaintenance Planning PlantS/4 HanaEAM_PLNGBKTMAINTENANCEPLANNINGPLANTMaintenance Planning PlantDirect Mapping
3DCTEAM_PLNGBKTMAINTENANCEPLANNINGPLANTMaintenance Planning PlantS/4 HanaEAM_PLNGBKTMAINTENANCEPLANTPlantDirect Mapping
4DCTEAM_PLNGBKTMAINTPLNGBUCKETLABELLabel used for identifying the Maintenance Planning BucketS/4 HanaEAM_PLNGBKTMAINTPLNGBUCKETLABELLabel used for identifying the Maintenance Planning BucketDirect Mapping
5DCTEAM_PLNGBKTMAINTPLANNINGBUCKETDESCRIPTIONDescription of the Maintenance Planning BucketS/4 HanaEAM_PLNGBKTMAINTPLANNINGBUCKETDESCRIPTIONDescription of the Maintenance Planning BucketDirect Mapping
6--- -S/4 HanaEAM_PLNGBKTMAINTPLANNINGBUCKETTYPEMaintenance Planning Bucket TypeDefault to "STO" for Event Based Maintenance
7DCTEAM_PLNGBKTzMAINTPLNGBUCKETSTARTDATEStart Date of the Maintenance Planning BucketS/4 Hana

EAM_PLNGBKTMAINTPLNGBUCKETSTARTDATETIMEStart of the Maintenance Planning Bucket

Concatenate from source fields of DCT EAM_PLNGBKT:

  • zMAINTPLNGBUCKETSTARTDATE
  • ", "
  • zMAINTPLNGBUCKETSTARTTIME
8DCTEAM_PLNGBKTzMAINTPLNGBUCKETSTARTTIMEStart Time of the Maintenance Planning Bucket
9DCTEAM_PLNGBKTzMAINTPLNGBUCKETENDDATEEnd Date of the Maintenance Planning BucketS/4 Hana

EAM_PLNGBKTMAINTPLNGBUCKETENDDATETIMEEnd of the Maintenance Planning Bucket

Concatenate from source fields of DCT EAM_PLNGBKT:

  • zMAINTPLNGBUCKETENDDATE
  • ", "
  • zMAINTPLNGBUCKETENDTIME
10DCTEAM_PLNGBKTzMAINTPLNGBUCKETENDTIMEEnd Time of the Maintenance Planning Bucket
11--- -S/4 HanaEAM_PLNGBKTMAINTENANCESYSTEMSTATUSCODEObject statusDefault to "I0001" for CRTD
12--- -S/4 HanaEAM_PLNGBKTMAINTENANCEEVENTRevision for Plant Maintenance and Customer ServiceDefault to "0000000"
13--- -S/4 HanaEAM_PLNGBKTPERSONRESPONSIBLEPerson ResponsibleTBD
14PF2, WP2T352RIWERKMaintenance Planning PlantS/4 HanaT352RIWERKMaintenance Planning PlantDirect Mapping
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
OTH_Migration_Date Relevant Values A2DDates to be defaulted for A2D objects for each Migration Cycle
PlantOld to New Plant Mapping
Maintenance Planning BucketOld Revision to Maintenance Planning Bucket Mapping

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #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:

  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 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 Item
1T001W-Plants/Branches
2T399I-Planning Plant
3TC24-Person responsible for the work center
4TJ02-System status
5TBD-Maintenance Planning Bucket Type

Conversion Objects

Object #Preceding Object Conversion Approach

Not Applicable

Error Handling

Error TypeError DescriptionAction Taken
Configuration

Invalid Plant

Engage Functional team to expedite and fix the error in the system

Configuration

InvalidPlanning Plant

Engage Functional team to expedite and fix the error in the system

Configuration

Invalid Person Responsible

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

ConfigurationInvalid Maintenance Planning Bucket TypeEngage Functional team to expedite and fix the error in the system


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.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 39) Apr 13, 2026 11:59 ERGUIZA-ext, Pinky Love
v. 115 Apr 10, 2026 11:21 ERGUIZA-ext, Pinky Love
v. 114 Mar 25, 2026 05:09 ERGUIZA-ext, Pinky Love PDM-1373: Removal of Reference to TC24 as result of Unit Test
v. 113 Mar 25, 2026 05:04 ERGUIZA-ext, Pinky Love
v. 112 Mar 25, 2026 05:01 ERGUIZA-ext, Pinky Love
v. 111 Feb 12, 2026 13:53 ERGUIZA-ext, Pinky Love
v. 110 Feb 12, 2026 13:52 ERGUIZA-ext, Pinky Love MAINTPLNGBUCKETLABEL: Updated Rule post Functional Review
v. 109 Feb 12, 2026 13:50 ERGUIZA-ext, Pinky Love
v. 108 Feb 10, 2026 12:55 ERGUIZA-ext, Pinky Love
v. 107 Feb 04, 2026 10:25 ERGUIZA-ext, Pinky Love

Go to Page History

Workflow history

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

  • No labels