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

Compare with Current View Page History

« Previous Version 17 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 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. All valid legacy Revision based on Maintenance Plants in scope

The data from legacy system excludes:
1. Weekly Revisions



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




Target Design

The technical design of the target for this conversion approach.

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_PLNGBKTLASTCHANGEDATETIMEEAM_LASTCHANGEDATDate and time the planning bucket was last changed150
EAM_PLNGBKTMAINTPLNGBUCKETGENERATIONDATEEAM_GENERATIONBASEDATEDate based on which the planning bucket was calculated80
EAM_PLNGBKTREFMAINTPLANNINGBUCKETSYSUUID_XUUID in X form (binary)160
EAM_PLNGBKTMAINTPLNGBUCKETLABELPATTERNEAM_PLNGBKTLABELPATTERNTemplate used for the labels of generated planning buckets600
EAM_PLNGBKTMAINTPLNGBUCKETSORTFIELDEAM_PLNGBKTSORTFIELDSort field160
EAM_PLNGBKTMAINTPLNGBUCKETRECURRENCETYPEEAM_PLNGBKTRECURRENCETYPESpecifies the recurrence of the planning bucket, e.g. weekly150
EAM_PLNGBKTMAINTPLNGBUCKETDURATIONEAM_PLNGBKTDURATIONDuration of the Maintenance Planning Bucket100
EAM_PLNGBKTMAINTPLNGBUCKETDURATIONUNITEAM_PLNGBKTDURATIONUNITUnit for Duration of Maintenance Planning Bucket30
EAM_PLNGBKTMAINTPLNGBCKTRCRRCINTERVALEAM_PLNGBKTRECUREVERYSpecifies the interval of recurrence, e.g. every 3 weeks50
EAM_PLNGBKTPERSONRESPONSIBLEEAM_PERSONRESP_CHAR8Person Responsible80
EAM_PLNGBKTMAINTENANCEEVENTREVNIRevision for Plant Maintenance and Customer Service80
EAM_PLNGBKTMAINTORDERFORADMINISTRATIONAUFNROrder Number120
EAM_PLNGBKTMAINTPLNGBUCKETSTATUSOBJECTJ_OBJNRObject number220
EAM_PLNGBKTMAINTENANCEPLANNINGBUCKETEAM_PLNGBCKT_OBJNRObject Number of Maintenance Planning Bucket200
EAM_PLNGBKTSYSTEMSTATUSTEXTJ_STEXTSystem status line400
EAM_PLNGBKTMAINTENANCESYSTEMSTATUSCODEJ_STATUSObject status50
EAM_PLNGBKTMAINTENANCEPLANTWERKS_DPlant40
EAM_PLNGBKT.INCLUDEASM_MPBKT_INCL_EEW_PSPersistence Include for Maintenance Planning Bucket00
EAM_PLNGBKTDUMMY_ASM_MPBKT_INCL_EEW_PSCFD_DUMMYCustom Fields: Dummy for Use in Extension Includes10
T352RIWERKIWERKMaintenance Planning Plant40
T352RREVNRREVNIRevision for Plant Maintenance and Customer Service80
T352RREVBDREVBDDate of revision start80
T352RREVBZREVBZTime of revision start60
T352RREVEDREVEDDate of revision end80
T352RREVEZREVEZTime of revision end60
T352RREVTXREVTXRevision description400
T352RREVABREVABIndicator: Revision completed10
T352RPM_OBJTYPM_OBJTYObject Type of CIM Resources for Work Center20
T352RGEWRKGEWRKMain work center for maintenance tasks80
T352REQUNREQUNREquipment Number180
T352RTPLNRTPLNRFunctional Location300
T352RPSPELPS_PSP_ELEWork breakdown structure element (WBS element)80
T352RAUFNRNW_AUFNRNetwork number120
T352RAENAMAENAMName of Person Who Changed Object120
T352RAEDATAEDATChanged On80
T352RERNAMERNAMName of Person who Created the Object120
T352RERDATERDATDate on Which Record Was Created80
T352ROBJNRJ_OBJNRObject number220
T352RREVTYDIWPS_REVTY_CORERevision Type20
T352ROBJIDLGWIDObject ID of the Work Center80
T352RVAPLZGEWRKMain work center for maintenance tasks80
T352RVAWRKWERGWPlant associated with main work center40
T352REXTAPPLDIWPS_EXT_APPLExternal Application20
T352REXTREFDIWPS_REV_EXT_REFExternal Reference to Revision200


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
9101-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 Criteria		All key fieldsPF2, WP2
9101-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 Criteria		All key fieldsPF2, WP2
9101-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 Criteria		All key fieldsPF2, WP2








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:


Data Privacy and Sensitivity


Extraction

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

  1. The data exists. connects to the source and loads the data into . 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 . This is to be conducted using DCT (Data Collection Template) in

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
2Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. Data Team







Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set





















Data Collection Template (DCT)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field NameField DescriptionRule












Extraction Dependencies

Item #Step DescriptionTeam Responsible
1Only Revision linked to relevant Plants should be extracted.










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

Ensure all mapping tables are up to date.

Syniti

2

In dspMigrate, select the wave –R3 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 invalid reports by region 

Business/Data owner

7

Generate export(load) file (If load tool is not dspIntergrate)

Data Team


Transformation Rules

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









































Transformation Mapping

Mapping Table NameMapping Table Description








Transformation Dependencies

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













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













Load Phase and Dependencies

Configuration

Item #Configuration Item
1Plant
2Planning Bucket Type


Conversion Objects

Object #Preceding Object Conversion Approach

N/A




Error Handling

Error TypeError DescriptionAction Taken










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