| Status | Revision in Progress |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Portfolio Initiatives in S/4 HANA.
This is a completely new object for Syensqo.
Portfolio Initiatives represents a Programme in EPPM. A Portfolio Initiative is group of related projects (Portfolio Items) potentially belonging to different Portfolio Buckets for reporting purposes.
Initiative Decision Point represents the stage gates for a EPPM Programme. Although the decision point will be automatically created on creation of the Initiatives no action is required for the Initiative decision points from a data conversion perspective.
Conversion Scope
The scope of this document covers the approach for converting active Portfolio Initiatives from Legacy Source Systems into S/4HANA following the Portfolio Initiatives Master Data Design Standard.
This is a completely new object for Syensqo with the data being provided in a clean status with no requirement for exclusion of any records.
No action is required for the Initiative decision points from a data migration perspective.
The expected volume of data is ????
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
DCT | All Records | ? | S/4HANA | ? |
Additional Information
Multi-language Requirement
Initiative names and texts will be maintained in a single language (however they are entered); translations will not be possible.
Document Management
Not Applicable
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| INM_INITIATIVE | EXTERNAL_ID | INM_TV_EXTID | Initiative ID | CHAR | 24 | Mandatory |
| INM_INITIATIVE | STAT | STAT | System status | CHAR | 5 | Mandatory |
| INM_INITIATIVE | PORTFOLIO_ID | /RPM/TV_EXTID | Portfolio ID | CHAR | 24 | Mandatory |
| INM_INITIATIVE | BUCKET_ID | /RPM/TV_EXTID | Parent Bucket ID | CHAR | 24 | Mandatory |
| INM_INITIATIVE | ITEM_TYPE | /RPM/TV_ITEM_ID | Initiative Type | CHAR | 24 | Mandatory |
| INM_INITIATIVE | NAME | CGPL_TEXT1 | Initiative Name | CHAR | 40 | Mandatory |
| INM_INITIATIVE | CURRENCY | RPM_TV_CURRENCY | Currency key | CUKY | 5 | Mandatory |
| INM_INITIATIVE | PLANNED_START | RPM_TV_PLAN_START | Planned Start | DATS | 8 | Optional |
| INM_INITIATIVE | PLANNED_FINISH | RPM_TV_PLAN_FINISH | Planned Finish | DATS | 8 | Optional |
| INM_INITIATIVE | CAP_PERIODTYPE | /RPM/TV_CAP_PERIOD_TYPE | Capacity Period Breakdown | NUMC | 2 | Mandatory |
| INM_INITIATIVE | UNIT | RPM_TV_UNIT | Unit | CHAR | 3 | Mandatory |
| INM_INITIATIVE | PERIODTYPE | /RPM/TV_PERIOD_TYPE | Financial Period Breakdown | NUMC | 2 | Mandatory |
| INM_INITIATIVE | ZX001 | HROBJID | Program Manager | NUMC | 8 | Mandatory |
| INM_INITIATIVE | ZX002 | STEXT | Program Manager Position Name | STEXT | 40 | Mandatory |
| INM_INITIATIVE | ZX003 | SOBID | Program Manager ID | CHAR | 45 | Mandatory |
| INM_INITIATIVE | ZX004 | STEXT | Program Manager Name | STEXT | 40 | Mandatory |
| INM_INITIATIVE | LTEXT | STXL-CLUSTD | Initiative Description | CLUSTD | Optional |
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 . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . 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 . 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 |
|---|---|---|
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 |
|---|---|---|
| EXTERNAL_ID | Initiative ID | Unique Identifier for the Initiative, system generated number. (IN-XXXXXX) |
| STAT | System status | Represent the system status of an initiative. Default Status is set upon creation of PPM Initiative. It can be modified by the Program Manager at any point during the Initiative's lifecycle. |
| PORTFOLIO_ID | Portfolio ID | Locked and Defaulted "Syensqo" |
| BUCKET_ID | Parent Bucket ID | Unique Identifier for the initiative's parent Bucket. In SyWay it is the ID of the L3 bucket where item is assigned |
| NAME | Initiative Name | Name of the Initiative. |
| PLANNED_START | Planned Start | Optional Format (YYYYMMDD) |
| PLANNED_FINISH | Planned Finish | Optional Format (YYYYMMDD) |
| ZX001 | Program Manager | This field represent Position of the Program Manager and is mandatory for all Initiatives to determine the responsibility |
| LTEXT | Initiative Description | Conditional for initiatives where additional program information is required |
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.
- Legacy values are mapped to the to-be values (this could include a default value)
- 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 |
|---|---|---|
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
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EXTERNAL_ID | Initiative ID | S/4 Hana | INM_INITIATIVE | EXTERNAL_ID | Initiative ID | Copy from source to target system | |
| 2 | DCT | STAT | System status | S/4 Hana | INM_INITIATIVE | STAT | System status | Copy from source to target system | |
| 3 | DCT | PORTFOLIO_ID | Portfolio ID | S/4 Hana | INM_INITIATIVE | PORTFOLIO_ID | Portfolio ID | Copy from source to target system | |
| 4 | DCT | BUCKET ID | Parent Bucket ID | S/4 Hana | INM_INITIATIVE | BUCKET_ID | Parent Bucket ID | Copy from source to target system | |
| 5 | DCT | S/4 Hana | INM_INITIATIVE | ITEM_TYPE | Initiative Type | Default "Z001" | |||
| 6 | DCT | NAME | Initiative Name | S/4 Hana | INM_INITIATIVE | NAME | Initiative Name | Copy from source to target system | |
| 7 | DCT | S/4 Hana | INM_INITIATIVE | CURRENCY | Currency key | Default "EUR" | |||
| 8 | DCT | PLANNED_START | Planned Start | S/4 Hana | INM_INITIATIVE | PLANNED_START | Planned Start | Copy from source to target system | |
| 9 | DCT | PLANNED_FINISH | Planned Finish | S/4 Hana | INM_INITIATIVE | PLANNED_FINISH | Planned Finish | Copy from source to target system | |
| 10 | S/4 Hana | INM_INITIATIVE | CAP_PERIODTYPE | Capacity Period Breakdown | Default to "12"(Annually) | ||||
| 11 | S/4 Hana | INM_INITIATIVE | UNIT | Unit | Default to "TAG"(Day) | ||||
| 12 | S/4 Hana | INM_INITIATIVE | PERIODTYPE | Financial Period Breakdown | Default to "12"(Annually) | ||||
| 13 | DCT | ZX001 | Program Manager | S/4 Hana | INM_INITIATIVE | ZX001 | Program Manager | Copy from source to target system | |
| 14 | S/4 Hana | INM_INITIATIVE | ZX002 | Program Manager Position Name | Value Mapping: Position Name from Position Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001 | ||||
| 15 | S/4 Hana | INM_INITIATIVE | ZX003 | Program Manager ID | Value Mapping: Personal ID from Position Mapped from table field HRP1001-SOBID where HRP1001-SCLAS=P, OTYPE=S & OBJID=ZX001 | ||||
| 16 | S/4 Hana | INM_INITIATIVE | ZX004 | Program Manager Name | Value Mapping: Personal Name from Position Mapped from table field HRP1000-STEXT where HRP1000-OBJID=ZX003 | ||||
| 17 | DCT | LTEXT | Initiative Description | S/4 Hana | INM_INITIATIVE | LTEXT | Initiative Description | Copy from source to target system |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
HRP1000 | Infotype 1000 DB Table |
| HRP1001 | Infotype 1001 DB Table |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Position table HRP1000 has been maintained (HRP1000) | |
| 2 | Position table HRP1001 has been maintained (HRP1001) | |
Pre-Load Validation
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
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_INITIATIVE | 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 Initiative App | SyWay I2M Data Team |
6 | Generate post load report if step 5 is validated | SyWay I2M Data Team |
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
| 1 | Initiative Type (/RPM/ITEM_TYPE) |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1113 | Portfolio Bucket Hierarchy |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Invalid Data | Invalid Portfolio | Validate DCT default content |
Invalid Data | Invalid Bucket ID | Validate DCT default content |
Post-Load Validation
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 Portfolio Initiatives in target S/4 HANA were loaded correctly via Initiative Dashboard App display and table V_INM_INIT_DB in S/4 HANA |
Business
Completeness
| Task | Action |
|---|---|
Verify Count | Extract Initiative details from Initiative dashboard App in S/4 HANA |
Accuracy
| Task | Action |
|---|---|
| Verify Accuracy | Extract Initiative details from Initiative dashboard App 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.
- Portfolio Initiatives is in scope based on data design and any exception requested by business.