| Status | |
|---|---|
| Owner | |
| 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).
| 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 |
/RPM/BUCKET_D | NAME | CGPL_TEXT1 | Bucket Name | CHAR | 40 | Mandatory |
/RPM/BUCKET_D | RELEASE_STATUS | /RPM/TV_RELEASE_STATUS | Status | CHAR | 5 | Mandatory |
/RPM/BUCKET_D | PORTFOLIO_ID | /RPM/TV_EXTID | Portfolio Id | CHAR | 24 | Mandatory |
/RPM/BUCKET_D | 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 | Technical detail for the data element is currently outstanding | Function | Technical detail for the data element is currently outstanding | Technical detail for the data element is currently outstanding | 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:
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if Syniti Migrate; 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 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.... |
NAME | 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. |
PARENTNAME | Parent Name | 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. |
ZOWNER | Bucket Owner Position ID | Position ID of the Bucket Owner. |
ZAPPR | Bucket Approver Position ID | Position ID of the Bucket Approver. |
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 |
| PORTFOLIO_ID | Portfolio Id | Display Only Default to "Syensqo" |
| LEVEL | Level | Display Automatically determined based on parent Level +1 |
| PARENT_ID | Parent Bucked Id | Display Calculated PARENT_ID |
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:
- 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 Syniti Migrate
- 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 | Load DCT using transformation rules | 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
Not all fields from DCT to be mapped to target fields.
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
1 | EXTERNAL_ID | Id | S/4 Hana | /RPM/BUCKET_D | EXTERNAL_ID | Id | Copy from source to target system | ||
2 | NAME | Name of Bucket | S/4 Hana | /RPM/BUCKET_D | NAME | Bucket Name | Copy from source to target system | ||
| 3 | RELEASE_STATUS | Status | S/4 Hana | /RPM/BUCKET_D | RELEASE_STATUS | Status | Default to "0002"(Active) | ||
| 4 | PORTFOLIO_ID | Portfolio Id | S/4 Hana | /RPM/BUCKET_D | PORTFOLIO_ID | Portfolio Id | Copy from source to target system | ||
| 5 | Parent_ID | Parent Bucked Id | S/4 Hana | /RPM/BUCKET_D | Parent_ID | Parent Bucked Id | Copy from source to target system | ||
| 6 | S/4 Hana | /RPM/BUCKET_D | CURRENCY | Currency | Default to (EUR) | ||||
| 7 | S/4 Hana | /RPM/BUCKET_D | PERIOD_TYPE | Fin Period Breakdown | Default to "12"(Annually) From /RPM/PERIOD_TYPE | ||||
| 8 | S/4 Hana | /RPM/BUCKET_D | UNIT | Capacity Unit | Default to (Day) From T006 | ||||
| 9 | S/4 Hana | /RPM/BUCKET_D | CAP_PERIOD_TYPE | Cap Period Breakdown | Default to "12"(Annually) From /RPM/PERIOD_TYPE | ||||
| 10 | S/4 Hana | /RPM/BUCKET_D | BEGDA_FIN | Financial Planning Start | Default to "20251001" (YYYYMMDD) | ||||
| 11 | S/4 Hana | /RPM/BUCKET_D | ENDDA_FIN | Financial Planning Finish | Default to "20390930" (YYYYMMDD) | ||||
| 12 | S/4 Hana | /RPM/BUCKET_D | BEGDA_DEM | Capacity Planning Start | Default to "20251001" (YYYYMMDD) | ||||
| 13 | S/4 Hana | /RPM/BUCKET_D | ENDDA_DEM | Capacity Planning Finish | Default to "20390930" (YYYYMMDD) | ||||
| 14 | S/4 Hana | /RPM/BUCKET_D | BEGDA_CO | Current Transfer Start | Default to "20191001" (YYYYMMDD) | ||||
| 15 | S/4 Hana | /RPM/BUCKET_D | ENDDA_CO | Current Transfer Finish | Default to "20390930" (YYYYMMDD) | ||||
| 16 | ZOWNER | Bucket Owner Position ID | S/4 Hana | /RPM/BUCKET_D | ZOWNER | Bucket Owner | Copy from source to target system | ||
| 17 | S/4 Hana | /RPM/BUCKET_D | ZOWNERNAME | Position Description of the Bucket Owner | Select HRP1000-STEXT where HRP1000-OBJID=ZONWER | ||||
| 18 | ZAPPR | Bucket Approver Position ID | S/4 Hana | /RPM/BUCKET_D | ZAPPR | Bucket Approver | Copy from source to target system | ||
| 19 | S/4 Hana | /RPM/BUCKET_D | ZAPPRNAME | Position Description of the Bucket Approver | Select HRP1000-STEXT where HRP1000-OBJID=ZAPPR | ||||
| 20 | ZPROFITCENTRE | Profit centre | S/4 Hana | /RPM/BUCKET_D | ZPROFITCENTRE | Profit centre | Copy from source to target system | ||
| 21 | ZFUNCTION | Function | S/4 Hana | /RPM/BUCKET_D | ZFUNCTION | Function | Copy from source to target system |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
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 |
|---|---|
Verify Record Count | SyWay I2M Data Team to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | SyWay I2M Data Team to verify that all fields below meet pass the 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 (DCT) data. |
Business
The following pre-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT 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 | Go to RPM_DX_BUCKET | SyWay I2M Data Team |
2 | Load 3 records for < > to validate if data is loaded successfully without errors | SyWay I2M Data Team |
3 | Load 3 records for < > to validate if data is loaded successfully without errors | SyWay I2M Data Team |
4 | Proceed with full load if steps 2 and 3 are validated | SyWay I2M Data Team |
5 | Validate few records loaded by accessing Portfolio Bucket Structure App | SyWay I2M Data Team |
6 | Generate post load report if step 5 is validated | SyWay I2M Data Team |
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 |
|---|---|
| 1021 | Portfolio |
| 1073 | Profit Centre |
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 |
|---|---|---|
| Invalid Data | Invalid Portfolio | Validate DCT default content |
| Invalid Data | Invalid Bucket ID | Correct upload data |
Post-Load Validation
Project Team
The following post-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
Verify Count | SyWay I2M Data Team to verify the record count created in target S/4 HANA by accessing post load reports 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 | Verify that the Bucket Hierarchy in target S/4 HANA were loaded correctly via Standard Portfolio Bucket display and table /RPM/V_BUCKET_DB |
Business
The following post-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
| Verify Count | Extract structure from Bucket dashboard in S/4 Hana |
Accuracy
| Task | Action |
|---|---|
| Verify Bucket Structure | Extract structure from Bucket dashboard in S/4 Hana |
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.