Status
Owner	The person responsible for driving this decision and documenting it. Type @ to mention people by name
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

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

Bucket: The overall structure of the Portfolio is reflected in a hierarchy of Buckets. Each Portfolio Item is assigned to a Bucket within the Portfolio.

Syensqo utilizes Portfolio Buckets to represent the Organisation structure as GBUs and functions for budget management purposes.

Conversion Scope

The scope of this document covers the approach for converting active Portfolio Bucket Hierarchy from Legacy Source Systems into S/4HANA following the Portfolio Bucket Hierarchy Master Data Design Standard.

This is a completely new object for Syensqo with the data being sourced using DCT (Data Collection Template).

Syensqo utilizes Portfolio Buckets to represent the Organisation structure as GBUs and functions for budget management purposes

• Level 1 Bucket represents Syensqo group,
• Level 2 Represents GBU and
• Level 3 represents Functions within the GBUs.

This is a completely new object for Syensqo with the data being sourced using DCT (Data Collection Template).

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
DCT	All Records	50	S/4HANA	50

Additional Information

Multi-language Requirement

PPM Portfolio will be maintained in English only.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
/RPM/BUCKET_D	EXTERNAL_ID	/RPM/TV_EXTID	Id	CHAR	24	Mandatory
CGPL_TEXT	Name	CGPL_TEXT1	Bucket Name	CHAR	40	Mandatory
/RPM/BUCKET_D	RELEASE_STATUS	/RPM/TV_RELEASE_STATUS	Status	CHAR	5	Mandatory
/RPM/PORTFOLIO_D	PORTFOLIO_ID	/RPM/TV_EXTID	Portfolio Id	CHAR	24	Mandatory
CGPL_TEXT	Parent_ID	/RPM/TV_EXTID	Parent Bucked Id	CHAR	24	Mandatory
/RPM/BUCKET_D	CURRENCY	/RPM/TV_CURRENCY	Currency	CUKY	5	Mandatory
/RPM/BUCKET_D	PERIOD_TYPE	/RPM/TV_PERIOD_TYPE	Fin Period Breakdown	NUMC	2	Mandatory
/RPM/BUCKET_D	UNIT	/RPM/TV_UNIT	Capacity Unit	UNIT	3	Mandatory
/RPM/BUCKET_D	CAP_PERIOD_TYPE	/RPM/TV_CAP_PERIOD_TYPE	Cap Period Breakdown	NUMC	2	Mandatory
/RPM/BUCKET_D	BEGDA_FIN	/RPM/TV_FINPLAN_BEGDA	Financial Planning Start	DATS	8	Mandatory
/RPM/BUCKET_D	ENDDA_FIN	/RPM/TV_FINPLAN_ENDDA	Financial Planning Finish	DATS	8	Mandatory
/RPM/BUCKET_D	BEGDA_DEM	/RPM/TV_DEMAND_BEGDA	Capacity Planning Start	DATS	8	Mandatory
/RPM/BUCKET_D	ENDDA_DEM	/RPM/TV_DEMAND_ENDDA	Capacity Planning Finish	DATS	8	Mandatory
/RPM/BUCKET_D	BEGDA_CO	/RPM/TV_COPLAN_BEGDA	Current Transfer Start	DATS	8	Mandatory
/RPM/BUCKET_D	ENDDA_CO	/RPM/TV_COPLAN_ENDDA	Current Transfer Finish	DATS	8	Mandatory
/RPM/BUCKET_D	ZOWNER	HROBJID	Bucket Owner	NUMC	8	Mandatory
/RPM/BUCKET_D	ZOWNERName	STEXT	Position Description of the Bucket Owner	CHAR	40	Mandatory
/RPM/BUCKET_D	ZAPPR	HROBJID	Bucket Approver	NUMC	8	Mandatory
/RPM/BUCKET_D	ZAPPRName	STEXT	Position Description of the Bucket Approver	CHAR	40	Mandatory
/RPM/BUCKET_D	ZPROFITCENTRE	PRCTR	Profit centre	CHAR	10	Mandatory
/RPM/BUCKET_D	ZFUNCTION		Function			Conditional

Data Cleansing

Not applicable, as data object Project Bucket Hierarchy does not exist in legacy system and will be collected specifically for data migration.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

The high-level process is represented by the diagram below:

Data Privacy and Sensitivity

Not Applicable.

Extraction

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

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

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

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

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 Object data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Field Name	Field Description	Rule
EXTERNAL_ID	Id	Manually assigned starts with letter B and follows 5 digit running number - example B-00001, B-00002.... When a new bucket is added, next available number need to be checked before assigning it manually to the new bucket
TEXT1	Name of Bucket	Buckets in the standard Portfolio are to be aligned with with the areas of Budget Accountability and are to be named accordingly.A prefix of  Parent 'GBU' is required at L3 to avoid any confusion with other hierarchies.
RELEASE_STATUS	Status	Locked and Default to "0002"(Active)
PORTFOLIO_ID	Portfolio Id	Locked and Default to "Syensqo"
Parent_ID	Parent Bucked Id	It is mandatory to nominate a Parent Bucket on creation of each Bucket, except for the L1 Bucket which is assigned to the Portfolio directly. This hierarchical assignment of Buckets defines the Portfolio structure.
CURRENCY	Currency	Locked and Default to (EUR)
PERIOD_TYPE	Fin Period Breakdown	Locked and Default to "12"(Annually) From /RPM/PERIOD_TYPE
UNIT	Capacity Unit	Locked and Default to (Day) From T006
CAP_PERIOD_TYPE	Cap Period Breakdown	Locked and Default to "12"(Annually) From /RPM/PERIOD_TYPE
BEGDA_FIN	Financial Planning Start	Locked and Default to "20251001"  (YYYYMMDD)
ENDDA_FIN	Financial Planning Finish	Locked and Default to "20390930"  (YYYYMMDD)
BEGDA_DEM	Capacity Planning Start	Locked and Default to "20251001"  (YYYYMMDD)
ENDDA_DEM	Capacity Planning Finish	Locked and Default to "20390930"  (YYYYMMDD)
BEGDA_CO	Current Transfer Start	Locked and Default to "20191001"  (YYYYMMDD)
ENDDA_CO	Current Transfer Finish	Locked and Default to "20390930"  (YYYYMMDD)
ZOWNER	Bucket Owner Position ID	Position ID of the Bucket Owner. At L3 represent owner who would qualify PPM items as relevant for prioritisation. At L2 represent owner who prioritise PPM items based on their ranking and other parameters AT L1 represent portfolio owner
ZAPPR	Bucket Approver Position ID	Position ID of the Bucket Approver. At L2 represent Approver who approves the budget allocation
ZPROFITCENTRE	Profit centre	Generic Profit centre of GBU which defines the bucket represents or belongs to the particular GBU.
ZFUNCTION	Function	Function at L3 Bucket used to group buckets of same function across all GBUs. Required at L3 Bucket, Blank at L1 and L2 buckets

Extraction Dependencies

List the steps that need to occur before extraction can commence

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 Syniti Migrate 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 Syniti Migrate
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 Description	Team Responsible
1	Obtain DCT Sign-off from Business	SyWay I2M Data Team
2	<Syniti Steps here>	SyWay I2M Data Team
3	Review and Validate Error and Preload Reports	SyWay I2M Data Team
4	Generate Load Files	SyWay I2M Data Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT		ZOWNER	Bucket Owner		/RPM/BUCKET_D	ZOWNERName	Position Description of the Bucket Owner	This field represent name of the Position ID. it will from table field HRP1000-STEXT where HRP1000-OBJID=ZONWER
2	DCT		ZAPPR	Bucket Owner		/RPM/BUCKET_D	ZAPPRName	Position Description of the Bucket Approver	This field represent name of the Position ID. it will from table field HRP1000-STEXT where HRP1000-OBJID=ZAPPR

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description
HRP1000	Infotype 1000 DB Table

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Profit centers has been created (CEPC)
2	Position table HRP1000 has been maintained (HRP1000)

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

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 Description	Team Responsible

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item

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

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object is in scope based on data design and any exception requested by business.

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log