Status	Approved
Owner
Stakeholders

Purpose

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

Depending on how Revision is used in S4, what Revision Types are configured

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.

The data from legacy system includes:

All valid legacy Revision

The data from legacy system excludes:

Closed Revision
Revision with Dates (Start? End?) in the past
Any other criteria?

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	3000	S/4HANA	3000
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

N/A

Legal Requirement

N/A

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
9003-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	All key fields	PF2, WP2
9003-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	All key fields	PF2, WP2
9003-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	All key fields	PF2, 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:

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.
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 Description	Team Responsible
1	Extract data from source system based on relevancy rule	Data Team
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	Data Team

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value 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 Name	Field Description	Rule

Extraction Dependencies

Item #	Step Description	Team Responsible

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:

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

Transformation Rules

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

Transformation Mapping

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

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:

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

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

Load Run Sheet

Item #	Step Description	Team Responsible

Load Phase and Dependencies

Configuration

Item #	Configuration Item
N/A

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

Error Handling

Error Type	Error Description	Action Taken

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.

Change log

Version	Published	Changed By	Comment
CURRENT (v. 6)	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.

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

CNV-9003 Maintenance Planning Bucket

Purpose

Conversion Scope

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)

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

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history