| 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 Item in S/4 HANA.
PPM Item: A PPM Item is a proxy of project in PPM which is used to plan, evaluate, and monitor Spend (capex/Opex) within Syensqo’s portfolio. In SyWay, PPM Item is created under the 3rd level bucket (functions) under GBU Bucket.
Portfolio items does not exist in the current ECC environments but will be created for all relevant PS Projects through data enrichment process as well as new Items specifically included through the DCT.
Conversion Scope
The scope of this document covers the approach for converting active Portfolio Item from Legacy Source Systems into S/4HANA following the Portfolio Item Master Data Design Standard.
This is a completely new object for Syensqo with the data being sourced using a DCT (Data Collection Template), the template will be prepopulated with relevant information from Capital and Budget Managed Operating PS Projects in scope for migration.
The detail of Project definition migration scope is dealt with in CNV-1024 Project Definition
Projects from the legacy system to be used for the basis of the system include projects from PF2 and WP2.
The data from legacy system includes:
- Capital projects open as at migration date.
- Budgeted Operating projects open as at migration date.
- Closed Capital Projects with postings within the agreed timeframe.
- Closed Budgeted Operating Projects with postings within the agreed timeframe.
The data from legacy system excludes:
- Project definitions with profile ZPS0003 - Statistical Expense
- Project definitions with profile ZPS0004 - Recharge Projects
- Project definitions with profile ZPS0005 - Provisional Projects
Additionally, there may be Items included in the DCT which does not have any existing Project Systems objects.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Relevant Open PS Projects | S/4 Hana | ||
| WP2 | Relevant Open PS Projects | S/4 Hana | ||
| DCT | ||||
Additional Information
Multi-language Requirement
Item names and texts will be maintained in a single language (however they are entered); translations not required.
Document Management
N/A
Legal Requirement
Summarize Legal Requirement/s, if any
Special Requirements
Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).
If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.
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/ITEM_D | EXTERNAL_ID | /RPM/TV_EXTID | ID | CHAR | 24 | Mandatory |
| /RPM/ITEM_D | PARENT_ID | /RPM/TV_EXTID | Parent Bucket ID | CHAR | 24 | Mandatory |
| /RPM/ITEM_D | PARENT_GUID | Bucket GUID | System Generated | |||
| /RPM/ITEM_D | PORTFOLIO_GUID | System Generated | ||||
| /RPM/ITEM_D | PORTFOLIO_ID | /RPM/TV_EXTID | Portfolio ID | CHAR | 24 | Mandatory |
| /RPM/ITEM_D | ITEM_TYPE | /RPM/TV_ITEM_ID | Type | CHAR | 15 | Mandatory |
| CGPL_TEXT | TEXT1 | CGPL_TEXT1 | Name | CHAR | 40 | Mandatory |
| STXL | LTEXT | CLUSTD | Item Description | CLUSTD | Conditional | |
| /RPM/ITEM_D | STATUS | /RPM/TV_STATUS_COMMON | Item Status | CHAR | 5 | Mandatory |
| /RPM/ITEM_D | PLANNED_START | RPM_TV_PLAN_START | Planned Start | DATS | 8 | Mandatory |
| /RPM/ITEM_D | PLANNED_FINISH | RPM_TV_PLAN_FINISH | Planned Finish | DATS | 8 | Mandatory |
| /RPM/ITEM_D | FORECAST_START | RPM_TV_FORECAST_START | Forecasted Start | DATS | 8 | Conditional |
| /RPM/ITEM_D | FORECAST_FINISH | RPM_TV_FORECAST_FINISH | Forecasted Finish | DATS | 8 | Conditional |
| /RPM/ITEM_D | CATEGORY | RPM_PROJECT_CATEGORY | Category | NUMC | 4 | Mandatory |
| /RPM/ITEM_D | SUBCATEGORY | RPM_PROJ_SUBCATEGORY | Subcategory | NUMC | 4 | Mandatory |
| /RPM/ITEM_D | GEOGRAPHY | RPM_TV_PROJECT_GEOGRAPHY | Area | CHAR | 4 | Mandatory |
| /RPM/ITEM_D | ESCALATION | RPM_TV_ESCALATION | Escalation | CHAR | 1 | Conditional |
| /RPM/ITEM_D | CURRENCY | RPM_TV_CURRENCY | CURRENCY | CUKY | 5 | Mandatory |
| /RPM/ITEM_D | UNIT | RPM_TV_UNIT | Unit | UNIT | 3 | Mandatory |
| /RPM/ITEM_D | CAP_PERIODTYPE | /RPM/TV_CAP_PERIOD_TYPE | Capacity Period Breakdown | NUMC | 2 | Mandatory |
| /RPM/ITEM_D | PERIODTYPE | /RPM/TV_PERIOD_TYPE | Fin Period Breakdown | NUMC | 2 | Mandatory |
| /RPM/ITEM_D | INITIATIVE_ID | INM_TV_EXTID | INITIATIVE ID | CHAR | 24 | Conditional |
| /RPM/ITEM_D | ZXX1 | Investment Category | CHAR | 4 | Mandatory | |
| /RPM/ITEM_D | ZXX2 | Spending Range | CHAR | 4 | Mandatory | |
| /RPM/ITEM_D | ZXX3 | Business Unit/ Domain | CHAR | 40 | Mandatory | |
| /RPM/ITEM_D | ZXX4 | End User Market | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXX5 | Market Driver | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXX6 | Cluster | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXX7 | GBU Product Family | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXX8 | GBU Product Category | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXX9 | Product (s) | CHAR | 40 | Mandatory | |
| /RPM/ITEM_D | ZXX10 | Export Control | NUMC | 3 | Mandatory | |
| /RPM/ITEM_D | ZXX11 | Need-to-know | CHAR | 1 | Mandatory | |
| /RPM/ITEM_D | ZXX12 | Sustainability Score | NUMC | 3 | Mandatory | |
| /RPM/ITEM_D | ZXX13 | EU Taxonomy | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX14 | HROBJID | Person Responsible | NUMC | 8 | Mandatory |
| /RPM/ITEM_D | ZXX15 | STEXT | Person Responsible | STEXT | 40 | System Generated |
| /RPM/ITEM_D | ZXX16 | HROBJID | Project Financial Controller | NUMC | 8 | Mandatory |
| /RPM/ITEM_D | ZXX17 | STEXT | Project Financial Controller | STEXT | 40 | System Generated |
| /RPM/ITEM_D | ZXX18 | Starting Risk Magnitude | CHAR | 4 | Conditional | |
| /RPM/ITEM_D | ZXX19 | Starting Risk Likelihood | CHAR | 4 | Conditional | |
| /RPM/ITEM_D | ZXX20 | Residual Risk Magnitude | CHAR | 4 | Conditional | |
| /RPM/ITEM_D | ZXX21 | Residual Risk Likelihood | CHAR | 4 | Conditional | |
| /RPM/ITEM_D | ZXX22 | Regulatory Mandated Magnitude | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX23 | Regulatory Mandated Likelihood | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX24 | Regulatory Mandated Time Horizon (to start project) | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX25 | Capitalization Date | DATS | 8 | Conditional | |
| /RPM/ITEM_D | ZXX26 | PRCTR | Profit Centre | CHAR | 10 | Mandatory |
| /RPM/ITEM_D | ZXX27 | WeGo ID | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX28 | Investment Reason | Mandatory | |||
| /RPM/ITEM_D | ZXX29 | Budget Provision | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX30 | Opportunity ID | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXX31 | Archetype | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX32 | Must Do Justification | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX33 | PS_PSPID | Legacy Project ID | CHAR | 24 | Conditional |
| /RPM/ITEM_D | ZXX34 | WERKS_D | Plant | CHAR | 4 | Conditional |
| /RPM/ITEM_D | ZXX35 | Idea ID | CHAR | 40 | Conditional |
Relationship between /RPM/ITEM_D and CGPL_TEXT is the field /RPM/ITEM_D-GUID
Data Cleansing
Consider inputs from 1024 - Project Definition (CAPEX, OPEX)
Clean enriched data will be provided by business in DCT.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
Conversion Process
The high-level process is represented by the diagram below:
Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object
Data Privacy and Sensitivity
Some projects are considered Need to Know and data is to be restricted.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 |
|---|---|---|
| 1 | Extract from DTC | Syniti |
Selection Screen
N/A| 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 Portfolio Item.data with exception of some fields which require transformation as mentioned in the transformation rule.
Portfolio Item DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| EXTERNAL_ID | ID | Unique Identifier for the Item, system generated number. In SyWay, the prefix "A" indicates a Capex item/project, "E" denotes Opex, and "R" represents R&I. For China instance a new number range will be defined. |
| PARENT_ID | Parent Bucket ID | Unique Identifier for the Item's parent Bucket. In SyWay it is the ID of the L3 bucket where item is assigned |
| PORTFOLIO_ID | Portfolio ID | Unique Identifier for the Item's portfolio, system generated number. |
| ITEM_TYPE | Type | Item types define the structure and behavior of the portfolio item. In Syway item types will be based on the function and number of phases of the project. Refer configuration table field /RPM/ITEM_TYPE- ITEM_TYPE for allowed values. |
| TEXT1 | Name | 40 character description of the PPM Item |
| LTEXT | Item Description | Long-text Description, this field is used to provide a concise description of the PPM Item. Conditional for projects where additional project scope information is required |
| STATUS | Item Status | Represents status of an item (from Customizing). Refer configuration table field /RPM/ITEM_STATUS- STATUS against ITEM_TYPE for the allowed values of the selected Item Type. |
| PLANNED_START | Planned Start | Baseline start date of the item/ project used for planning within the portfolio/ bucket. |
| PLANNED_FINISH | Planned Finish | Expected Delivery Date. Baseline finish date of the item/ project used for planning within the portfolio/ bucket. |
| FORECAST_START | Forecasted Start | A forecast start date is predictive date when an item/project is likely to begin. In the Syway design, if this field is available in Operational Project Management tool (outside SAP) then required to be maintained. |
| FORECAST_FINISH | Forecasted Finish | A forecast finish date is predictive date when an item/project is likely to complete. In the Syway design, if this field is available in Operational Project Management tool (outside SAP) then required to be maintained. |
| CATEGORY | Category | In Syway, "Category" represents the business driver. It is a dropdown field with customizable values. Refer configuration table field RPM_PROJ_CAT- CATEGORY for the allowed values. |
| SUBCATEGORY | Subcategory | In Syway, "Sub Category" represents the rationale behind the investment/expense for the item/project. This is a dropdown field whose values are configurable and depend on the selected "Category". Refer configuration table field RPM_PROJ_SUBCAT- SUBCATEGORY against the selected field RPM_PROJ_SUBCAT- CATEGORY. |
| GEOGRAPHY | Area | Represents Company code; the legal entity in which the Syway Project will be executed. Refer configuration table field V_DPR_AREA- AREA for the allowed values. |
| ESCALATION | Escalation | Checkbox; Selection indicates if PPM item is qualified for the Prioritization process. For R&I it will be managed at cluster level PPM Item |
| INITIATIVE_ID | INITIATIVE ID | Internal ID of Initiative where Item must be linked to Initiative |
| ZXX1 | Investment category | In SyWay, investment category is a mandatory field to define the drivers for the project Growth/ Sustenance |
| ZXX2 | Spending Range | The Capex spending range used for reporting the project size i.e. XS, S, M, L & XL. |
| ZXX3 | Business Unit/ Domain | Business Unit/ Domain field is an organizational unit within GBU/ Function which owns the project. |
| ZXX4 | End User market | Classification of the industrial end users based upon type of industry e.g. aerospace, automative etc. |
| ZXX5 | Market driver | Market driver in SyWay is factor that influence demand/ growth/ success of the project. |
| ZXX6 | Cluster | In SyWay, Used to group items together for reporting where a budget allocation is made at an aggregated level, and actuals are collected against individual related items. |
| ZXX7 | GBU product family | GBU Product Family relevant for the project. When Item Type is related to either IS or R&I project then either of GBU product family, GBU product category or Product is required. |
| ZXX8 | GBU product category | GBU Product Category relevant for the project. When Item Type is related to either IS or R&I project then either of GBU product family, GBU product category or Product is required. |
| ZXX9 | Product (s) | Product relevant for the project. When Item Type is related to either IS or R&I project then either of GBU product family, GBU product category or Product is required. |
| ZXX10 | Export control relevant | A questionnaire to identify if the project is applicable for regulatory governance, will be used to derive value for this field. 100 = Relevant for Export Control, 0= not relevant. |
| ZXX11 | Need-to-know | This field indicates confidential projects. Access will be restricted if selection is "Yes" |
| ZXX12 | Overall Sustainability Score | This field is used to determine whether the project is subject to environmental compliance requirements. Questionnaire will be assigned to this field. |
| ZXX13 | EU taxonomy | EU Taxonomy is mandatory field for IS projects |
| ZXX14 | Person responsible Position ID | This field represent Position of the Person Responsible for WBS elements (Project Manager) and is mandatory for all SyWay business functions. Manually selected from the drop-down list. Refer configuration table field TCJ04-PS_VERNR for field validation. |
| ZXX16 | Project Financial Controller Position ID | This field represent Position of the Project Financial Controller for a project and is mandatory for all SyWay business functions. Manually selected from the drop-down list. Refer configuration table field TCJ05-ASTNR for field validation. |
| ZXX18 | Starting Risk Magnitude | This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction |
| ZXX19 | Starting Risk Likelihood | This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction |
| ZXX20 | Residual Risk Magnitude | This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction |
| ZXX21 | Residual Risk Likelihood | This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction |
| ZXX22 | Regulatory Mandated Magnitude | This field is mandatory if dropdown value of the "Category" field = Regulatory compliance |
| ZXX23 | Regulatory Mandated Likelihood | This field is mandatory if dropdown value of the "Category" field = Regulatory compliance |
| ZXX24 | Regulatory Mandated Time Horizon (to start project) | This field is mandatory if dropdown value of the "Category" field = Regulatory compliance |
| ZXX25 | Capitalization Date | For ongoing Capex projects SyWay carries out "Depreciation forecast", this date is mandatory for the "Capital Projects" Item types. Item Types are Z001,Z002, Z003, Z008, Z009, Z011 |
| ZXX26 | Profit Centre | Profit centre is required on PPM Item to create Project in SAP PS automatically. Refer master table field CEPC-PRCTR for Profit center list. |
| ZXX27 | WeGo ID | System calculated score for prioritization and ranking |
| ZXX28 | Investment Reason | In Syway, "Investment Reason" represent the detailed investment/ expense reason. This is a dropdown field and depend on the selected "Sub Category" |
| ZXX29 | Budget Provision | "Budget Provision" Item Type exists as a distinct category. Additionally, a custom field named "Budget Provision" will be available in other CAPEX item types. This field will feature a dropdown containing Budget Provision PPM items for selection. |
| ZXX30 | Opportunity ID | If IS or R&I PPM item is created with reference to a CRM Opportunity, the corresponding Opportunity ID will be entered. |
| ZXX31 | Archetype | This field represent Archetype of the R&I PPM item. N/A for IS & IT PPM Items. Refer configuration table field RPM_PROJ_TYPE- PTYPE against the selected field RPM_PROJ_TYPE- CATEGORY. |
| ZXX32 | Must Do Justification | If financial analysis required, then this field is mandatory. Required where any of the following values are selected in the "Category" field of the PPM Item- 1. New growth - Capacity expansion 2. Existing growth - Capacity improvement 3. Asset Management |
| ZXX33 | Legacy Project ID | Legacy Project ID refers to the project identifier used in the previous SAP system before migration to the current S/4 HANA platform. It will be mandatory for the cutover projects only. |
| ZXX34 | Plant | Plant represent a site of the PPM Item. Mandatory for all PPM Items. |
| ZXX35 | Idea ID | Field to store the Idea number where known. |
Extraction Dependencies
List the steps that need to occur before extraction can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure DCT is collected for Item | Data Team |
2 | Perform preliminary completeness 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 |
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 | Analyse 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 | EXTERNAL_ID | ID | S/4 Hana | /RPM/ITEM_D | EXTERNAL_ID | ID | Copy from source to target system | |
| 2 | DCT | PARENT_ID | Parent Bucket ID | S/4 Hana | /RPM/ITEM_D | PARENT_ID | Parent Bucket ID | Copy from source to target system | |
| 3 | DCT | PORTFOLIO_ID | Portfolio ID | S/4 Hana | /RPM/ITEM_D | PORTFOLIO_ID | Portfolio ID | Copy from source to target system | |
| 4 | DCT | ITEM_TYPE | Type | S/4 Hana | /RPM/ITEM_D | ITEM_TYPE | Type | Copy from source to target system | |
| 5 | DCT | TEXT1 | Name | S/4 Hana | /RPM/ITEM_D | TEXT1 | Name | Copy from source to target system | |
| 6 | DCT | LTEXT | Item Description | S/4 Hana | /RPM/ITEM_D | LTEXT | Item Description | Copy from source to target system | |
| 7 | DCT | STATUS | Item Status | S/4 Hana | /RPM/ITEM_D | STATUS | Item Status | Copy from source to target system | |
| 8 | DCT | PLANNED_START | Planned Start | S/4 Hana | /RPM/ITEM_D | PLANNED_START | Planned Start | Copy from source to target system | |
| 9 | DCT | PLANNED_FINISH | Planned Finish | S/4 Hana | /RPM/ITEM_D | PLANNED_FINISH | Planned Finish | Copy from source to target system | |
| 10 | DCT | FORECAST_START | Forecasted Start | S/4 Hana | /RPM/ITEM_D | FORECAST_START | Forecasted Start | Copy from source to target system | |
| 11 | DCT | FORECAST_FINISH | Forecasted Finish | S/4 Hana | /RPM/ITEM_D | FORECAST_FINISH | Forecasted Finish | Copy from source to target system | |
| 12 | DCT | CATEGORY | Category | S/4 Hana | /RPM/ITEM_D | CATEGORY | Category | Copy from source to target system | |
| 13 | DCT | SUBCATEGORY | Subcategory | S/4 Hana | /RPM/ITEM_D | SUBCATEGORY | Subcategory | Copy from source to target system | |
| 14 | DCT | GEOGRAPHY | Area | S/4 Hana | /RPM/ITEM_D | GEOGRAPHY | Area | Value Mapping: Old to New Company Code | |
| 15 | DCT | NPV | Net Present Value (manual) | S/4 Hana | /RPM/ITEM_D | NPV | Net Present Value (manual) | Copy from source to target system | |
| 16 | DCT | PROBC | Probability Commercial Success | S/4 Hana | /RPM/ITEM_D | PROBC | Probability Commercial Success | Copy from source to target system | |
| 17 | DCT | PROBT | Probability Technical Success | S/4 Hana | /RPM/ITEM_D | PROBT | Probability Technical Success | Copy from source to target system | |
| 18 | DCT | ESCALATION | Escalation | S/4 Hana | /RPM/ITEM_D | ESCALATION | Escalation | Copy from source to target system | |
| 19 | S/4 Hana | /RPM/ITEM_D | CURRENCY | CURRENCY | Value Mapping: Currency From Company Code Company Code Currency from T001-WAERS where BUKRS = Target Geography | ||||
| 20 | S/4 Hana | /RPM/ITEM_D | UNIT | Unit | Default to "TAG"(Day) | ||||
| 21 | S/4 Hana | /RPM/ITEM_D | CAP_PERIODTYPE | Capacity Period Breakdown | Default to "12"(Annually) | ||||
| 22 | S/4 Hana | /RPM/ITEM_D | PERIODTYPE | Fin Period Breakdown | Default to "12"(Annually) | ||||
| 23 | DCT | INITIATIVE_ID | INITIATIVE ID | S/4 Hana | /RPM/ITEM_D | INITIATIVE_ID | INITIATIVE ID | Copy from source to target system | |
| 24 | DCT | ZXX1 | Investment category | S/4 Hana | /RPM/ITEM_D | ZXX1 | Investment category | Copy from source to target system | |
| 25 | DCT | ZXX2 | Spending Range | S/4 Hana | /RPM/ITEM_D | ZXX2 | Spending Range | Copy from source to target system | |
| 26 | DCT | ZXX3 | Business Unit/ Domain | S/4 Hana | /RPM/ITEM_D | ZXX3 | Business Unit/ Domain | Copy from source to target system | |
| 27 | DCT | ZXX4 | End User market | S/4 Hana | /RPM/ITEM_D | ZXX4 | End User market | Copy from source to target system | |
| 28 | DCT | ZXX5 | Market driver | S/4 Hana | /RPM/ITEM_D | ZXX5 | Market driver | Copy from source to target system | |
| 29 | DCT | ZXX6 | Cluster | S/4 Hana | /RPM/ITEM_D | ZXX6 | Cluster | Copy from source to target system | |
| 30 | DCT | ZXX7 | GBU product family | S/4 Hana | /RPM/ITEM_D | ZXX7 | GBU product family | Copy from source to target system | |
| 31 | DCT | ZXX8 | GBU product category | S/4 Hana | /RPM/ITEM_D | ZXX8 | GBU product category | Copy from source to target system | |
| 32 | DCT | ZXX9 | Product (s) | S/4 Hana | /RPM/ITEM_D | ZXX9 | Product (s) | Copy from source to target system | |
| 33 | DCT | ZXX10 | Export control relevant | S/4 Hana | /RPM/ITEM_D | ZXX10 | Export control relevant | Copy from source to target system | |
| 34 | DCT | ZXX11 | Need-to-know | S/4 Hana | /RPM/ITEM_D | ZXX11 | Need-to-know | Copy from source to target system | |
| 35 | DCT | ZXX12 | Overall Sustainability Score | S/4 Hana | /RPM/ITEM_D | ZXX12 | Overall Sustainability Score | Copy from source to target system | |
| 36 | DCT | ZXX13 | EU taxonomy | S/4 Hana | /RPM/ITEM_D | ZXX13 | EU taxonomy | Copy from source to target system | |
| 37 | DCT | ZXX14 | Person responsible Position ID | S/4 Hana | /RPM/ITEM_D | ZXX14 | Person responsible Position ID | Copy from source to target system | |
| 38 | S/4 Hana | /RPM/ITEM_D | ZXX15 | Person Responsible Position Name | Value Mapping: Position Name from Position Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001 | ||||
| 41 | DCT | ZXX18 | Project Financial Controller Position ID | S/4 Hana | /RPM/ITEM_D | ZXX18 | Project Financial Controller Position ID | Copy from source to target system | |
| 42 | S/4 Hana | /RPM/ITEM_D | ZXX19 | Project Financial Controller Position Name | Value Mapping: Position Name from Position Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001 | ||||
| 45 | DCT | ZXX23 | Year of Maturity | S/4 Hana | /RPM/ITEM_D | ZXX23 | Year of Maturity | Copy from source to target system | |
| 46 | DCT | ZXX24 | Sales at Maturity | S/4 Hana | /RPM/ITEM_D | ZXX24 | Sales at Maturity | Copy from source to target system | |
| 47 | DCT | ZXX25 | EBIDTA at Maturity | S/4 Hana | /RPM/ITEM_D | ZXX25 | EBIDTA at Maturity | Copy from source to target system | |
| 48 | DCT | ZXX26 | Starting risk Magnitude | S/4 Hana | /RPM/ITEM_D | ZXX26 | Starting risk Magnitude | Copy from source to target system | |
| 49 | DCT | ZXX27 | Starting risk Likelihood | S/4 Hana | /RPM/ITEM_D | ZXX27 | Starting risk Likelihood | Copy from source to target system | |
| 50 | DCT | ZXX28 | Residual risk Magnitude | S/4 Hana | /RPM/ITEM_D | ZXX28 | Residual risk Magnitude | Copy from source to target system | |
| 51 | DCT | ZXX29 | Residual risk Likelihood | S/4 Hana | /RPM/ITEM_D | ZXX29 | Residual risk Likelihood | Copy from source to target system | |
| 53 | DCT | ZXX32 | Regulatory Mandated Magnitude | S/4 Hana | /RPM/ITEM_D | ZXX32 | Regulatory Mandated Magnitude | Copy from source to target system | |
| 54 | DCT | ZXX33 | Regulatory Mandated Likelihood | S/4 Hana | /RPM/ITEM_D | ZXX33 | Regulatory Mandated Likelihood | Copy from source to target system | |
| 55 | DCT | ZXX34 | Regulatory Mandated Time Horizon (to start project) | S/4 Hana | /RPM/ITEM_D | ZXX34 | Regulatory Mandated Time Horizon (to start project) | Copy from source to target system | |
| 56 | DCT | ZXX35 | Capitalization Date | S/4 Hana | /RPM/ITEM_D | ZXX35 | Capitalization Date | Copy from source to target system | |
| 57 | DCT | ZXX36 | Profit Centre | S/4 Hana | /RPM/ITEM_D | ZXX36 | Profit Centre | Copy from source to target system | |
| 58 | DCT | ZXX37 | Project Equivalent Score | S/4 Hana | /RPM/ITEM_D | ZXX37 | Project Equivalent Score | Copy from source to target system | |
| 59 | DCT | ZXX38 | Internal Rate of Return in % (man.) | S/4 Hana | /RPM/ITEM_D | ZXX38 | Internal Rate of Return in % (man.) | Copy from source to target system | |
| 60 | DCT | ZXX39 | Discounted Payback Period in years | S/4 Hana | /RPM/ITEM_D | ZXX39 | Discounted Payback Period in years | Copy from source to target system | |
| 61 | DCT | ZXX40 | Risk Adjusted NPV | S/4 Hana | /RPM/ITEM_D | ZXX40 | Risk Adjusted NPV | Copy from source to target system | |
| 62 | DCT | ZXX41 | WeGo ID | S/4 Hana | /RPM/ITEM_D | ZXX41 | WeGo ID | Copy from source to target system | |
| 64 | DCT | ZXX43 | Investment Reason | S/4 Hana | /RPM/ITEM_D | ZXX43 | Investment Reason | Copy from source to target system | |
| 65 | DCT | ZXX44 | Budget Provision | S/4 Hana | /RPM/ITEM_D | ZXX44 | Budget Provision | Copy from source to target system | |
| 66 | DCT | ZXX45 | Opportunity ID | S/4 Hana | /RPM/ITEM_D | ZXX45 | Opportunity ID | Copy from source to target system | |
| 67 | DCT | ZXX46 | Archetype | S/4 Hana | /RPM/ITEM_D | ZXX46 | Archetype | Copy from source to target system | |
| 68 | DCT | ZXX47 | Must Do Justification | S/4 Hana | /RPM/ITEM_D | ZXX47 | Must Do Justification | Copy from source to target system | |
| 69 | DCT | ZXX48 | Legacy Project ID | S/4 Hana | /RPM/ITEM_D | ZXX48 | Legacy Project ID | Copy from source to target system | |
| 70 | DCT | ZXX49 | Plant | S/4 Hana | /RPM/ITEM_D | ZXX49 | Plant | Copy from source to target system |
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| Mapping Table Name | Mapping Table Description |
|---|---|
| Company Code | Value Mapping: Old to New Company Code |
| T001 | Value Mapping: Currency From Company Code |
| HRP1000 | Value Mapping: Position Name from Position |
| Plant | Value Mapping: Old Plant to New |
| Profit Center | Value Mapping: Profit Center Old to New |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool. | Data Team |
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_ITEM | 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
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 |
|---|---|
| 1 | Override Default Global Settings (Master Switches 0002 Switched off - Item will have manual ID) |
| 2 | Define Currency Units |
| 3 | Define Period Types |
| 4 | Define Capacity Units |
| 5 | Configure Fields for Mass Import |
| Item Types - /RPM/ITEM_TYPE- ITEM_TYPE | |
| Item Type Status - /RPM/ITEM_STATUS- STATUS | |
| Category - RPM_PROJ_CAT- CATEGORY | |
| Sub-Category RPM_PROJ_SUBCAT- SUBCATEGORY | |
| Area - DPR_AREA | |
| Project Type - RPM_PROJ_TYPE | |
| Plant - T001W | |
| Responsible Person - TCJ04 | |
| Applicant - TCJ05 | |
| Priority Group | |
| Investment category | |
| Spending Range | |
| Business Unit/ Domain | |
| End User market | |
| GBU product family | |
| GBU product category | |
| Product (s) | |
| Investment Reason | |
| Archetype |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1113 | Portfolio Bucket Hierarchy |
| 1023 | Portfolio Initiative |
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 (Parent ID does not exist) | Correct upload data |
| Invalid Data | Invalid Item Type | Correct upload |
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 Item display and table /RPM/ITEM_D |
Business
The following post-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
| Verify Count | Extract Item details from Item App in S/4 Hana |
Accuracy
| Task | Action |
|---|---|
| Verify Accuracy | Extract Item details from Item App in S/4 Hana and compare |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- Portfolio Item 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.