| Status | In Progress |
|---|---|
| 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 approach for the maintenance of master data supporting the Project scoring methodology. This master data comprises fixed parameters used in the scoring calculations.
Project scoring uses structured scoring models to evaluate and prioritize projects based on predefined criteria like strategic alignment, risk.
Conversion Scope
The scope of this document covers the approach applicable to Project Scoring parameters and drop-down lists supporting PPM bucket/item custom fields which are created in S/4 HANA following the Project Scoring and Other dropdowns Master Data Design Standard.
The drop-down lists define the allowable values to be entered in the relevant custom fields on a PPM Item or Bucket. The scoring master data controls the parameters input to the scoring calculations (performed on PPM Items in SAC). These parameters are centrally maintained.
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 | S/4HANA | TBD |
Migration load to be done to ROW instance with replication to other S/4 Hana instances (China and CUI) done by batch job as per business process. To be included in cut-over strategy document.
Additional Information
Multi-language Requirement
Portfolio scoring attributes will be maintained in English Language only.
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 |
|---|---|---|---|---|---|---|
| /SYQ/T_BU_DMN | BU_DMN_CD | Business Unit/Domain Code | NUMC | 2 | Mandatory | |
| /SYQ/T_BU_DMN | BU_DMN_DESC | Business Unit/Domain Description | CHAR | 40 | Mandatory | |
| /SYQ/T_BU_DMN | ACTIVE | Active | Checkbox | Conditional |
Data Cleansing
Data cleansing not applicable, as data object Project Scoring and Other dropdowns will be collected specifically for data migration.
Collection will be done manually in the Data Collection Template.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| Not applicable |
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
Not applicableExtraction
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 |
|---|---|---|
| 1 | Ensure DCT is collected | Data Team |
| 2 | Perform preliminary completeness check, data quality check. | Data Team |
| 3 | Raise issues as defects if Req # 1 to 2 are not met | Data Team |
| 4 | Repeat Req # 1 to 3 if required | Data Team |
Selection Screen
Not Applicable| 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 Project Scoring and Other dropdowns data with exception of some fields which require transformation as mentioned in the transformation rule.Project Scoring and Other dropdowns DCT Rules.
| Field Name | Field Description | Rule |
|---|---|---|
| BU_DMN_CD | Business Unit/Domain Code | Unique code assigned to table entry |
| BU_DMN_DESC | Business Unit/Domain Description | Business Unit or Domain - a reporting attribute assigned to PPM Items; an organizational unit within GBU/ Function which owns the project. |
| ACTIVE | Active | Active Flag - if set, the record does not appear in the drop-down list for the field |
Extraction Dependencies
No Dependencies for Extract
| 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 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 | Data Team |
2 | Execute and Load and perform Transformation | Data Team |
3 | Monitor the transformation progress and ensure performance and completion is within allowed timeframe | Data team |
4 | Review and Validate Error and Preload Reports | Data Team |
5 | Generate data load count. | Data team |
6 | Generate Load Files | Data Team |
7 | Log errors as defects, if any and address resolutions. Close defects. | Data team |
| 8 | Re-transform and re-validate the Pre-load reports if necessary. | Data team |
| 9 | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
| 10 | Analyze and resolve any pre-load defects logged by business. | Data team |
| 11 | Repeat steps 7 to 10 if necessary | Data team |
| 12 | Proceed to pre-load validations | 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 | BU_DMN_CD | Business Unit/Domain Code | S/4 Hana | /SYQ/T_BU_DMN | BU_DMN_CD | Business Unit/Domain Code | Copy from source to target system | |
| 2 | DCT | BU_DMN_DESC | Business Unit/Domain Description | S/4 Hana | /SYQ/T_BU_DMN | BU_DMN_DESC | Business Unit/Domain Description | Copy from source to target system | |
| 3 | DCT | ACTIVE | Active | S/4 Hana | /SYQ/T_BU_DMN | ACTIVE | Active | 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 |
|---|---|
| Not applicable |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
Not applicable |
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
- Migration load to be done to ROW instance with replication to other S/4 Hana instances via interface (API) to the China and CUI instance. To be included in cut-over strategy document.
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Load using transaction custom upload / custom fiori app | Data Team |
2 | Load 3 records for < > to validate if data is loaded successfully without errors | Data Team |
3 | Load 3 records for < > to validate if data is loaded successfully without errors | Data Team |
4 | Proceed with full load if steps 2 and 3 are validated | Data Team |
5 | Validate few records loaded by accessing Portfolio Bucket Structure App | Data Team |
6 | Generate post load report if step 5 is validated | Data Team |
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
| 1 | Custom table /SYQ/T_BU_DMN with fields BU_DMN_CD, BU_DMN_DESC, ACTIVE |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| Not applicable |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
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 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 tables in target S/4 HANA were loaded correctly via SE16 download |
Business
Completeness
| Task | Action |
|---|---|
| Verify Count | Extract data in S/4 Hana via fiori tile and verify the count |
Accuracy
| Task | Action |
|---|---|
| Verify Count | Extract data in S/4 Hana via fiori tile and verify the count |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- Project Scoring and Other dropdowns is in scope based on data design and any exception requested by business.
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.