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:

Revisions within Maintenance Plants (T352R-IWERK) in scope (Value Mapping: Plant where Maintenance Plant = Yes)
Revisions with missing Date Start or Date End (T352R-REVBD = "" or T352R-REVED = "") with Open Legacy Work Order Assigned (AUFK-AUFNR)

The data from legacy system excludes:

Completed Revisions (T352R-REVTY = "X")
Revisions in the Past (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 Start or Date End (T352R-REVBD = "" or T352R-REVED = "") with NO Open Legacy Work Order Assigned (AUFK-AUFNR)

Note: Open Legacy Work Order (AUFK-AUFNR) Criteria: System Status (JEST-STAT) <> TECO (Technically Completed)

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		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	MAINTENANCEPLANNINGPLANT	IWERK	Maintenance Planning Plant	CHAR	4	Mandatory
IMR__VH	MAINTENANCEREVISION	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 the Maintenance Planning Bucket	CHAR	40	Mandatory
IMR__VH	MAINTPLANNINGBUCKETDESCRIPTION	EAM_PLNGBKTLABEL	Description of the Maintenance Planning Bucket	CHAR	40	Mandatory

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 = ("Events-Based", <blank>)
Missing Date Start or Missing Date End

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.

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 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
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. XXXXX
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	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
zMAINTPLNGBUCKETSTARTTIME	Start Time of the Maintenance Planning Bucket	Mandatory. Start time of validity of the Maintenance Planning Bucket Must be in HHMMSS format
zMAINTPLNGBUCKETENDDATE	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 Bucket Must be in DDMMYYYY format
zMAINTPLNGBUCKETENDTIME	End Time of the Maintenance Planning Bucket	Mandatory. End time of validity of the Maintenance Planning Bucket Must be in HHMMSS format
PERSONRESPONSIBLE	Person Responsible	Conditional. Must be a valid Person Responsible Needs to be selected from value list (TC24) 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)

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 (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 ", " REVBZ
8	PF2, WP2	T352R	REVBZ	Time of revision start	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETSTARTDATETIME	Start of the Maintenance Planning Bucket
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 ", " REVEZ
10	PF2, WP2	T352R	REVEZ	Time of revision end	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETENDDATETIME	End of the Maintenance Planning Bucket
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	MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	S/4 Hana	EAM_PLNGBKT	MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	Direct Mapping
3	DCT	EAM_PLNGBKT	MAINTENANCEPLANNINGPLANT	Maintenance Planning Plant	S/4 Hana	EAM_PLNGBKT	MAINTENANCEPLANT	Plant	Direct Mapping
4	DCT	EAM_PLNGBKT	MAINTPLNGBUCKETLABEL	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	DCT	EAM_PLNGBKT	MAINTPLANNINGBUCKETDESCRIPTION	Description of the Maintenance Planning Bucket	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	DCT	EAM_PLNGBKT	zMAINTPLNGBUCKETSTARTDATE	Start Date of the Maintenance Planning Bucket	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETSTARTDATETIME	Start of the Maintenance Planning Bucket	Concatenate from source fields of DCT EAM_PLNGBKT: zMAINTPLNGBUCKETSTARTDATE ", " zMAINTPLNGBUCKETSTARTTIME
8	DCT	EAM_PLNGBKT	zMAINTPLNGBUCKETSTARTTIME	Start Time of the Maintenance Planning Bucket	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETSTARTDATETIME	Start of the Maintenance Planning Bucket
9	DCT	EAM_PLNGBKT	zMAINTPLNGBUCKETENDDATE	End Date of the Maintenance Planning Bucket	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETENDDATETIME	End of the Maintenance Planning Bucket	Concatenate from source fields of DCT EAM_PLNGBKT: zMAINTPLNGBUCKETENDDATE ", " zMAINTPLNGBUCKETENDTIME
10	DCT	EAM_PLNGBKT	zMAINTPLNGBUCKETENDTIME	End Time of the Maintenance Planning Bucket	S/4 Hana	EAM_PLNGBKT	MAINTPLNGBUCKETENDDATETIME	End of the Maintenance Planning Bucket
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	Direct Mapping
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

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 Revision to Maintenance Planning Bucket Mapping

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

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	TC24-Person responsible for the work center
4	TJ02-System status
5	TBD-Maintenance Planning Bucket 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	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
Configuration	Invalid Maintenance Planning Bucket 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.

Change log

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