Status

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 will primarily be 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 Work Orders - can correctly reference the appropriate target Maintenance Planning Bucket.

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 within Maintenance Planning Plants (T352R-IWERK) in scope (Value Mapping: Plant where Maintenance Plant = Yes)
  2. 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"))
  3. 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:

  1. Completed Revisions (Indicator: Revisions Completed (T352R-REVTY = "X"))
  2. 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")
  3. 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: System Status (JEST-STAT) <> TECO (Technically Completed)

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


List of source systems and approximate number of records.

SourceScope

Source Approx No. of Records

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

250S/4HANA250
DCT

Maintenance Planning Bucket for plants which do not have data existing from PF2 and PF2

50 S/4HANA50

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

TableFieldData ElementField DescriptionData TypeLengthRequirement
EAM_PLNGBKTMAINTENANCEPLANNINGBUCKETEAM_PLNGBCKT_OBJNRObject Number of Maintenance Planning BucketCHAR20System
EAM_PLNGBKTMAINTENANCEPLANNINGPLANTIWERKMaintenance Planning PlantCHAR4Mandatory
EAM_PLNGBKTMAINTENANCEPLANTWERKS_DPlantCHAR4Mandatory
EAM_PLNGBKTMAINTPLNGBUCKETLABELEAM_PLNGBKTLABELLabel used for identifying the Maintenance Planning BucketCHAR40Mandatory
EAM_PLNGBKTMAINTPLANNINGBUCKETDESCRIPTIONEAM_PLNGBKTDESCDescription of the Maintenance Planning BucketCHAR40Mandatory
EAM_PLNGBKTMAINTPLANNINGBUCKETTYPEEAM_PLNGBKTTYPEMaintenance Planning Bucket TypeCHAR3Mandatory
EAM_PLNGBKTMAINTPLNGBUCKETSTARTDATETIMEEAM_PLNGBKTSTARTDATETIMEStart of the Maintenance Planning BucketDEC15Mandatory
EAM_PLNGBKTMAINTPLNGBUCKETENDDATETIMEEAM_PLNGBKTENDDATETIMEEnd of the Maintenance Planning BucketDEC15Mandatory
EAM_PLNGBKTMAINTENANCESYSTEMSTATUSCODEJ_STATUSObject statusCHAR5Mandatory
EAM_PLNGBKTMAINTENANCEEVENTREVNIRevision for Plant Maintenance and Customer ServiceCHAR8System
EAM_PLNGBKTPERSONRESPONSIBLEEAM_PERSONRESP_CHAR8Person ResponsibleCHAR8Conditional


2. Maintenance Events

TableFieldData ElementField DescriptionData TypeLengthRequirement
IMR__VHMAINTENANCEPLANNINGPLANTIWERKMaintenance Planning PlantCHAR4Mandatory
IMR__VHMAINTENANCEREVISIONREVNIRevision for Plant Maintenance and Customer ServiceCHAR8System
IMR__VHMAINTENANCEEVENTTYPEDIWPS_REVTY_CORERevision TypeCHAR2Mandatory
IMR__VHMAINTPLNGBUCKETLABELREVTXLabel used for identifying the Maintenance Planning BucketCHAR40Mandatory
IMR__VHMAINTPLANNINGBUCKETDESCRIPTIONEAM_PLNGBKTLABELDescription of the Maintenance Planning BucketCHAR40Mandatory

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


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
9101-001C2Missing Events-Based Revision Start and End Dates

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

  1. Revision Type from Value Mapping: Maintenance Planning Bucket (Old to New Mapping) = ("Events-Based", <blank>)
  2. Revisions missing from Value Mapping: Maintenance Planning Bucket (Old to New Mapping)
  3. Missing Date of Revision Start or Date of Revision End
Maintenance Planning Plant, Revision, Description, Date of Revision Start, Date of Revision EndPF2, WP2
9101-002C3Info 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 CompletedPF2, 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:

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

  • For sites not on SAP-PF2 or WP2 systems 

 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:

  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 ADMM 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 as reference point to identify the records that are applicable for the data construction in the DCT.

Extraction Run Sheet

Req #Requirement DescriptionTeam 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 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

zLegacyREVNRLegacy 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.
MAINTPLNGBUCKETLABELLabel used for identifying 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

MAINTPLANNINGBUCKETDESCRIPTIONDescription 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

zMAINTPLNGBUCKETSTARTDATEStart Date of the Maintenance Planning Bucket

Mandatory. 

  • Start date of validity of the Maintenance Planning Bucket
  • 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
  • If the user does not provide a value, this will be set to 000000.
zMAINTPLNGBUCKETENDDATEEnd Date of the Maintenance Planning Bucket

Mandatory. 

  • End date of validity of Maintenance Planning Bucket
  • Ensure date is after the "Go-Live" Date. Should be later than the Start Date of the Maintenance Planning Bucket
  • Must be in DDMMYYYY format

Note: "Go-Live" = "Migration Date" during Mocks

zMAINTPLNGBUCKETENDTIMEEnd Time of the Maintenance Planning Bucket

Mandatory. 

  • End 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 235959.
PERSONRESPONSIBLEPerson 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.
MAINTENANCEEVENTTYPEMaintenance 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 NameField DescriptionRule
zLegacyIWERKLegacy Maintenance Planning Plant

Mandatory. 

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

zLegacyREVNRLegacy 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.
zRevisionTypeLegacy Revision Type

Mandatory. 

Allowed Values:

  • Events-Based
  • Weekly Revision
MAINTENANCEPLANNINGPLANTMaintenance Planning Plant

Mandatory.

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

MAINTPLNGBUCKETLABELLabel 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)
MAINTENANCEEVENTMaintenance 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 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

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1---
S/4 HanaEAM_PLNGBKTMAINTPLANNINGBUCKETUUIDUUID in X form (binary)System Generated
2DCT-MAINTENANCEPLANNINGPLANTMaintenance Planning PlantS/4 HanaEAM_PLNGBKTMAINTENANCEPLANNINGPLANTMaintenance Planning PlantDirect Mapping
3DCT-MAINTENANCEPLANNINGPLANTMaintenance Planning PlantS/4 HanaEAM_PLNGBKTMAINTENANCEPLANTPlantDirect Mapping
4DCT-MAINTPLNGBUCKETLABELLabel used for identifying the Maintenance Planning BucketS/4 HanaEAM_PLNGBKTMAINTPLNGBUCKETLABELLabel used for identifying the Maintenance Planning BucketDirect Mapping
5DCT-MAINTPLANNINGBUCKETDESCRIPTIONDescription 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
7DCT-zMAINTPLNGBUCKETSTARTDATEStart Date of the Maintenance Planning BucketS/4 Hana

EAM_PLNGBKTMAINTPLNGBUCKETSTARTDATETIMEStart of the Maintenance Planning Bucket

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

Concatenate from source fields of DCT EAM_PLNGBKT:

  • zMAINTPLNGBUCKETSTARTDATE
  • ", "
  • zMAINTPLNGBUCKETSTARTTIME
8DCT-zMAINTPLNGBUCKETSTARTTIMEStart Time of the Maintenance Planning Bucket
9DCT-zMAINTPLNGBUCKETENDDATEEnd Date of the Maintenance Planning BucketS/4 Hana

EAM_PLNGBKTMAINTPLNGBUCKETENDDATETIMEEnd 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
10DCT-zMAINTPLNGBUCKETENDTIME
End Time of the Maintenance Planning Bucket
11--- -S/4 HanaEAM_PLNGBKTMAINTENANCESYSTEMSTATUSCODEObject statusDefault to "I0002" for Released
12--- -S/4 HanaEAM_PLNGBKTMAINTENANCEEVENTRevision for Plant Maintenance and Customer ServiceSystem Generated
13--- -S/4 HanaEAM_PLNGBKTPERSONRESPONSIBLEPerson ResponsibleDirect Mapping

2. Maintenance Events

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCT-MAINTENANCEPLANNINGPLANTMaintenance Planning PlantS/4 HanaIMR__VHMAINTENANCEPLANNINGPLANTMaintenance Planning PlantDirect Mapping
2--- -S/4 HanaIMR__VHMAINTENANCEREVISIONRevision for Plant Maintenance and Customer ServiceSystem Generated
3DCT-MAINTENANCEEVENTTYPERevision TypeS/4 HanaIMR__VHMAINTENANCEEVENTTYPERevision TypeDirect Mapping
4DCT-MAINTPLNGBUCKETLABELLabel used for identifying the Maintenance Planning BucketS/4 HanaIMR__VHMAINTPLNGBUCKETLABELLabel used for identifying the Maintenance Planning BucketDirect Mapping
5DCT-MAINTPLANNINGBUCKETDESCRIPTIONDescription of the Maintenance Planning BucketS/4 HanaIMR__VHMAINTPLANNINGBUCKETDESCRIPTIONDescription of the Maintenance Planning BucketDirect 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 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 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 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

The following pre-load validations will be performed by the 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

The following pre-load validations will be performed by the 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

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

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
5IMAINTEVTYPEVH-Maintenance Event 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

Invalid Planning 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 Maintenance Event TypeEngage Functional team to expedite and fix the error in the system


Post-Load Validation

Project Team

The following post-load validations will be performed by the 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

The following post-load validations will be performed by the 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.
  • 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.

Any additional key assumptions.


See also

Maintenance Planning Bucket is managed using Fiori Application and the some of the data sits within CDS views.

Since this is a new functionality, references have been included below to support the conversion process.

1. General Information

2. Event Planning and Execution Objects

3. System Status


Change log

Workflow history