| Status | Revision under Review |
|---|---|
| Owner | |
| Stakeholders |
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 and Opex) within Syensqo’s portfolio. In SyWay, PPM Items are created under the lowest level bucket.
Conversion Scope
The scope of this document covers the approach for converting applicable active Projects to Portfolio Items 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 DCT will contain transformed data from source system for Capital and Budget Managed Operating PS Project Definitions in scope for migration, extensive enrichment will be necessary to produce properly formatted data load sheets for S/4 HANA.
Relevancy Criteria
The data from legacy system includes:
- Capital projects (e.g. Industrial, Facility, IT and R&I) open as at migration date with postings in the last 3 years or has AUC balance.
- Budgeted Operating projects (e.g. Budgeted Maintenance, Marketing, Demolition projects) open as at migration date with postings in the last 3 years.
- Closed Capital Projects with postings within the agreed timeframe.
- Closed Budgeted Operating projects with postings within the agreed timeframe.
- Specifically also included are IT and R&I Projects (open as at migration date and (closed projects with postings the agreed timeframe) with postings in the last 3 years
The data from legacy system excludes
- Project Definition in out of scope Company Codes
- Project Definitions in out of scope Plants.
- Project which has deletion indicator set
- Project marked as closed and not included in C, D and E above.
- Non Budgeted maintenance orders.
Also exclude, Operating Expense projects without budget, including the following proposed project profile in S/4:
a. Open Project for Statistical Expenses - replaced by project definitions with profile ZPS0003 - Statistical Expense.
b. Open Recharge Projects - replaced by project definitions with profile ZPS0004 - Intercompany Recharges.
c. Open Project definitions with profile ZPS0005 - Provisional Projects.
The migration for these excluded Operating Expense project without budget is dealt with in CNV-1024 Project Definition
Additionally, there may be Items included in the DCT which does not have any existing Project Systems objects. as well as
Direct Asset purchases for which an Item is created for GBU/Company Code/Plant combination
Capital Spare for which an item is created for GBU/Company Code/Plant combination
Capital Lease for which an item is created for GBU/Company Code/Plant combination
Cluster Item
Budget Provision Item
List of source systems and approximate number of records
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Relevant Open PS Projects | S/4 Hana | TBD | |
| WP2 | Relevant Open PS Projects | S/4 Hana | TBD | |
| DCT | S/4 Hana | TBD |
Item is to be migrated into a single instance of S/4 Hana only with the determination of which instance dependent on the company code maintained in the area field of the item. Area will be maintained based upon the converted Company Code of the legacy Project Definition.
The PS Project definition with WBS element hierarchy (Level 1 & 2) is automatically created from the approved PPM item once stage-gate 1 is approved., the PS project structure is based on the configuration of PPM item type to a PS template project (created as per CVN-1019 Template Projects) with the Decision Flow Management settings in the SAP system. As per CNV-1019 Template Project - SyWay Project - Syensqo - Wiki knowledge base. The creation will be triggered for items that have legacy projects and items created for Capital Spares, Capital Purchases and Capital Leases.
Relevancy Logic:
Table PROJ
Field "Company Code" in scope.
Field project profile not excluded.
Result: Object numbers of Project that are in company codes in scope.
Table JEST:
Field "Object number" = Key in the object numbers of Project
Field "Status Inactive" = blank, Then filter object number that has status I0046 (Closed)(Closed projects will further be checked for postings in the agreed timeframe)
Result closed projects.
Table PRPS
Field PSPHI For closed projects numbers, Result WBS numbers for
Table RPSCO / COSP:
Field "Object number" = Key in the object numbers of WBS
Field "Fiscal Year" = the agreed timeframe.
Result = Object numbers that have cost in current year.
These WBS needs to be migrated.
For operating project which are not IT and R&I additional check is done for budget
Table BPGE
Using object number from PRPS (both open and closed)
If any WBS object has a record then project is seen to have a budget and is included.
Additional Information
Multi-language Requirement
All item names and texts will be maintained in a single language as entered, with no requirement for translation.
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 |
|---|---|---|---|---|---|---|
| /RPM/ITEM_D | EXTERNAL_ID | /RPM/TV_EXTID | ID | CHAR | 24 | System Generated |
| /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 | System Generated |
| /RPM/ITEM_D | CAP_PERIODTYPE | /RPM/TV_CAP_PERIOD_TYPE | Capacity Period Breakdown | NUMC | 2 | System Generated |
| /RPM/ITEM_D | PERIODTYPE | /RPM/TV_PERIOD_TYPE | Fin Period Breakdown | NUMC | 2 | System Generated |
| /RPM/ITEM_D | INITIATIVE_ID | INM_TV_EXTID | INITIATIVE ID | CHAR | 24 | Conditional |
| /RPM/ITEM_D | ZXX1 | Investment Category | NUMC | 2 | Mandatory | |
| /RPM/ITEM_D | ZXX2 | Spending Range | NUMC | 2 | Mandatory | |
| /RPM/ITEM_D | ZXX3 | Business Unit/ Domain | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX4 | End User Market | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX5 | Market Driver | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX6 | Cluster | NUMC | 2 | 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 | Conditional | |
| /RPM/ITEM_D | ZXX10 | Export Control | NUMC | 2 | 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 | NUMC | 2 | 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 | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX19 | Starting Risk Likelihood | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX20 | Residual Risk Magnitude | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX21 | Residual Risk Likelihood | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX22 | Regulatory Mandated Magnitude | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX23 | Regulatory Mandated Likelihood | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX24 | Regulatory Mandated Time Horizon (to start project) | NUMC | 2 | 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 | NUMC | 2 | Mandatory | |
| /RPM/ITEM_D | ZXX29 | Budget Provision | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX30 | Opportunity ID | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXX31 | Archetype | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX32 | Must Do Justification | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX33 | PS_PSPID | Legacy Project ID | CHAR | 24 | Conditional |
| /RPM/ITEM_D | ZXX34 | WERKS_D | Plant | CHAR | 4 | Mandatory |
| /RPM/ITEM_D | ZXX35 | Idea ID | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXECJ | Justification (Export Control) | CHAR | 60 | Conditional | |
| /RPM/ITEM_D | ZXX36 | Subsidy Relevant | CHAR | 1 | Conditional | |
| /RPM/DECISION | DECISION_ID | /RPM/TV_EXTID | ID | CHAR | 48 | Mandatory |
| /RPM/DECISION | STATUS | /RPM/TV_STATUS_COMMON | STATUS | CHAR | 5 | Conditional |
Relationship between /RPM/ITEM_D and CGPL_TEXT is the field /RPM/ITEM_D-GUID
Data Cleansing
.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| 1 | Medium | Projects with no actuals / Commitment | If the projects do not have any actual or commitments in the past year, and is not used in for account assignment on open maintenance order set the project to status CLSD (CJ20N) | Old project which can be closed | SAP ECC |
| 2 | Medium | Internal Orders with no actuals / Commitments | If the internal order do not have any actual or commitments in the past year, and is not used in for account assignment on open maintenance order set the project to status CLSD | Old Internal order which can be closed | SAP ECC |
Conversion Process
The high-level process is represented by the diagram below:
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 as reference point to identify the records that are applicable for the data construction in the DCT.
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
Extraction Run Sheet
| Req # | Requirement Description | Team Responsible |
|---|---|---|
| 1 | Extract data from source system based on relevancy rule | SyWay Data Team |
Selection Screen
| 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 Portfolio Item data with exception of some fields which require transformation as mentioned in the transformation rule.
Note: All rules specified below should be documented as a tooltip in the DC Page.
Portfolio Item DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| Portfolio_ID | Portfolio ID | Unique Identifier for Syensqo Portfolio ID |
| 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 It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| 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. It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| TEXT1 | Name | 40 character description of the PPM Item It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| 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. It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| PLANNED_START | Planned Start | Baseline start date of the item/ project used for planning within the portfolio/ bucket. It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| INITIATIVE_ID | INITIATIVE ID | Internal ID of Initiative where Item must be linked to Initiative |
| ZXX2 | Spending Range | The Capex spending range used for reporting the project size. Dropdown values from /SYQ/T_SPND_RNGE It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| ZXX3 | Business Unit/ Domain | Business Unit/ Domain field is an organizational unit within GBU/ Function which owns the project. Dropdown values from /SYQ/T_BU_DMN |
| ZXX4 | End User Market | Classification of the industrial end users based upon type of industry e.g. aerospace, automative etc. Dropdown values from /SYQ/T_END_USR_MKT |
| 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 | To identify if the project is applicable for regulatory governance, a dropdown list will appear with values. This is a dropdown field from /SYQ/T_EXPORT_CNTL |
| ZXECJ | Justification (Export Control) | Justification to be provided when Export Control is applicable. |
| ZXX11 | Need-to-know | This field indicates confidential projects. Access will be restricted if selection is "Yes" It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| ZXX13 | EU Taxonomy | EU Taxonomy is mandatory field for IS projects. This is a dropdown field from /SYQ/T_EU_TXNMY |
| ZXX14 | Person Responsible | 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. It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| ZXX16 | Project Financial Controller | 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. It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| ZXX18 | Starting Risk Magnitude | This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction This is a dropdown field /SYQ/T_RISK_MAGNITUDE |
| ZXX19 | Starting Risk Likelihood | This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction This is a dropdown field /SYQ/T_RISK_LKLHD |
| ZXX20 | Residual Risk Magnitude | This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction This is a dropdown field from /SYQ/T_RISK_MAGNITUDE |
| ZXX21 | Residual Risk Likelihood | This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction This is a dropdown field from /SYQ/T_RISK_LKLHD |
| ZXX22 | Regulatory Mandated Magnitude | This field is mandatory if dropdown value of the "Category" field = Regulatory compliance This is a dropdown field from /SYQ/T_REG_MAGNITUDE |
| ZXX23 | Regulatory Mandated Likelihood | This field is mandatory if dropdown value of the "Category" field = Regulatory compliance This is a dropdown field from /SYQ/T_REG_LKLHD |
| ZXX24 | Regulatory Mandated Time Horizon (to start project) | This field is mandatory if dropdown value of the "Category" field = Regulatory compliance This is a dropdown field from /SYQ/T_REG_TIME_HORIZON |
| ZXX25 | Capitalization Date | For ongoing Capex projects SyWay carries out "Depreciation forecast", this date is mandatory for the "Capital Projects" Item types. |
| 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. It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| ZXX27 | WeGo ID | Wego ID. Relevant for the R&I projects only. |
| 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" This is a dropdown field from /SYQ/T_INV_REASON It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| 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. This is an optional field. |
| ZXX31 | Archetype | This field represent Archetype of the R&I PPM item. N/A for IS & IT PPM Items. This is a dropdown field from /SYQ/T_ARCHETYPE |
| ZXX32 | Must Do Justification | If financial analysis required, then this field is mandatory. Required if Category is- |
| 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. It is a Required Field: Preload Check to be done to confirm that this field is filled the Data Collection Template |
| ZXX35 | Idea ID | Field to store the Idea number where known. This is an optional field. |
| ZXX36 | Subsidy Relevant | Use this checkbox if the project is eligible for government or institutional subsidies. |
| Instance | Instance | Instance where the project definition is to be loaded. |
| ACT_DPCPT | Active Decision Point | Indicates the active decision point for the item. Drop down field from /RPM/ITEM_PHASE based on selected ITEM_TYPE |
In conjunction with DCT business user will be provided with Person Responsible / Applicant list for reference.
Extraction Dependencies
| 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 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 | WP2 | PROJ | PSPID | ID | S/4 Hana | /RPM/ITEM_D | Legacy Project ID | Legacy Project ID (For existing records this is the key for related DCT values) For additional Items not from source this will be empty. | Copy From Source |
| 2 | WP2 | S/4 Hana | /RPM/ITEM_D | ITEM_TYPE | Type | Apply first successful rule If PROJ-PSPID start with RR* then capture in DCT. If any WBS elements PRPS-USER0 starts with IT then Z009 IF PROJ-ZINV = B4 Then Z011 IF PROJ-ZINV = B1, H1, or H2 Then Z013 IF PROJ-PSPID 4&5 Character of Project ID is /J: Then Z001 If PROJ-PSPID 4&5 Character of Project ID is /M: then Z002 f PROJ-PSPID 4&5 Character of Project ID is /C: then Z003 If no WBS elements is Capital, PRPS-IMPRF="" then Item type PRPS-Z010 | |||
| 3 | WP2 | PROJ | TEXT1 | Project Description | S/4 Hana | CGPL_TEXT | TEXT1 | Name | Copy source to target |
| 4 | WP2 | STXL | LTEXT | Long Description | S/4 Hana | STXL | LTEXT | Description | Copy source to target |
| 5 | WP2 | PROJ | SPROG | Forecast start date of project definition | S/4 Hana | /RPM/ITEM_D | FORECAST_START | Forecasted Start | Copy from source, format YYYYMMDD |
| 6 | WP2 | PROJ | EPROG | Forecast finish date for project definition | S/4 Hana | /RPM/ITEM_D | FORECAST_FINISH | Forecasted Finish | Copy from source, format YYYYMMDD |
| 7 | WP2 | PROJ | PLFAZ | Project planned start date | S/4 Hana | /RPM/ITEM_D | PLANNED_START | Planned Start | Copy from source, format YYYYMMDD |
| 8 | WP2 | PROJ | PLSEZ | Project planned finish date | S/4 Hana | /RPM/ITEM_D | PLANNED_FINISH | Planned Finish | Copy from source, format YYYYMMDD |
| 9 | WP2 | PROJ | VBUKR | Company code for the project | S/4 Hana | /RPM/ITEM_D | GEOGRAPHY | Area | Value Mapping: Old to New Company Code |
| 10 | WP2 | PROJ | PWHIE | WBS currency (project definition) | S/4 Hana | /RPM/ITEM_D | CURRENCY | CURRENCY | Copy from Source |
| 11 | WP2 | PROJ | PRCTR | Profit Center | S/4 Hana | /RPM/ITEM_D | ZXX26 | Profit Centre | Value Mapping: Profit Center Old to New |
| 12 | WP2 | PROJ | WERKS | Plant | S/4 Hana | /RPM/ITEM_D | ZXX34 | Plant | Value Mapping: Old Plant to New |
| 13 | WP2 | PROJ | ZZ_POSIT | Position of the person responsible | S/4 Hana | /RPM/ITEM_D | ZXX14 | Person responsible Position ID | Value Mapping: Old Position ID to New Position ID |
| 14 | WP2 | PRPS | ZZ_WEGO_ID | WEGO ID | S/4 Hana | /RPM/ITEM_D | ZXX27 | Wego ID | If all WBS Elements for the PSPID record has the same WEGO Number only. |
| 15 | PF2 | PROJ | PSPID | ID | S/4 Hana | /RPM/ITEM_D | Legacy Project ID | Legacy Project ID (For existing records this is the key for related DCT values) For additional Items not from source this will be empty. | Copy From Source |
| 16 | PF2 | PROJ | S/4 Hana | /RPM/ITEM_D | ITEM_TYPE | Type | Apply first successful rule only If PROJ-PSPID start with R-then capture in DCT. Investment Reason = H0 then Z009 IF PROJ-ZINV = B4 Then Z011 IF PROJ-ZINV = B1, B5, H1, or H2 Then Z013 IF PROJ-PSPID 4&5 Character of Project ID is /J: Then Z001 If PROJ-PSPID 4&5 Character of Project ID is /M: then Z002 f PROJ-PSPID 4&5 Character of Project ID is /C: then Z003 If no WBS elements is Capital, PRPS-IMPRF="" then Item type PRPS-Z010 | ||
| 17 | PF2 | PROJ | TEXT1 | Project Description | S/4 Hana | CGPL_TEXT | TEXT1 | Name | Copy source to target |
| 18 | PF2 | STXL | LTEXT | Long Description | S/4 Hana | STXL | LTEXT | Description | Copy source to target |
| 19 | PF2 | PROJ | SPROG | Forecast start date of project definition | S/4 Hana | /RPM/ITEM_D | FORECAST_START | Forecasted Start | Copy from source, format YYYYMMDD |
| 20 | PF2 | PROJ | EPROG | Forecast finish date for project definition | S/4 Hana | /RPM/ITEM_D | FORECAST_FINISH | Forecasted Finish | Copy from source, format YYYYMMDD |
| 21 | PF2 | PROJ | PLFAZ | Project planned start date | S/4 Hana | /RPM/ITEM_D | PLANNED_START | Planned Start | Copy from source, format YYYYMMDD |
| 22 | PF2 | PROJ | PLSEZ | Project planned finish date | S/4 Hana | /RPM/ITEM_D | PLANNED_FINISH | Planned Finish | Copy from source, format YYYYMMDD |
| 23 | PF2 | PROJ | VBUKR | Company code for the project | S/4 Hana | /RPM/ITEM_D | GEOGRAPHY | Area | Value Mapping: Old to New Company Code |
| 24 | PF2 | PROJ | PWHIE | WBS currency (project definition) | S/4 Hana | /RPM/ITEM_D | CURRENCY | Currency | Copy from Source |
| 25 | PF2 | PROJ | PRCTR | Profit Center | S/4 Hana | /RPM/ITEM_D | ZXX26 | Profit Centre | Value Mapping: Profit Center Old to New |
| 26 | PF2 | PROJ | WERKS | Plant | S/4 Hana | /RPM/ITEM_D | ZXX34 | Plant | Value Mapping: Old Plant to New |
| 27 | PF2 | PROJ | ZZ_POSIT | Position of the person responsible | S/4 Hana | /RPM/ITEM_D | ZXX14 | Person responsible Position ID | Value Mapping: Old Position ID to New Position ID |
| 28 | PF2 | PRPS | ZZ_WEGO_ID | WEGO ID | S/4 Hana | /RPM/ITEM_D | ZXX27 | Wego ID | If all WBS Elements for the PSPID record has the same WEGO Number only |
| 29 | S/4 Hana | /RPM/ITEM_D | EXTERNAL_ID | ID | System Generated | ||||
| 30 | DCT | PARENT_ID | Parent Bucket ID | S/4 Hana | /RPM/ITEM_D | PARENT_ID | Parent Bucket ID | Copy from source to target system | |
| 31 | DCT | Portfolio_ID | Portfolio ID | S/4 Hana | /RPM/ITEM_D | PORTFOLIO_ID | Portfolio ID | Copy from source to target system | |
| 32 | DCT | ITEM_TYPE | Type | S/4 Hana | /RPM/ITEM_D | ITEM_TYPE | Type | Copy from source to target system | |
| 33 | DCT | TEXT1 | Name | S/4 Hana | CGPL_TEXT | TEXT1 | Name | Copy from source to target system | |
| 34 | DCT | LTEXT | Item Description | S/4 Hana | STXL | LTEXT | CLUSTD | Copy from source to target system | |
| 35 | DCT | STATUS | Item Status | S/4 Hana | /RPM/ITEM_D | STATUS | Item Status | Copy from source to target system | |
| 36 | DCT | PLANNED_START | Planned Start | S/4 Hana | /RPM/ITEM_D | PLANNED_START | Planned Start | Copy from source to target system | |
| 37 | DCT | PLANNED_FINISH | Planned Finish | S/4 Hana | /RPM/ITEM_D | PLANNED_FINISH | Planned Finish | Copy from source to target system | |
| 38 | DCT | FORECAST_START | Forecasted Start | S/4 Hana | /RPM/ITEM_D | FORECAST_START | Forecasted Start | Copy from source to target system | |
| 39 | DCT | FORECAST_FINISH | Forecasted Finish | S/4 Hana | /RPM/ITEM_D | FORECAST_FINISH | Forecasted Finish | Copy from source to target system | |
| 40 | DCT | CATEGORY | Category | S/4 Hana | /RPM/ITEM_D | CATEGORY | Category | Copy from source to target system | |
| 41 | DCT | SUBCATEGORY | Subcategory | S/4 Hana | /RPM/ITEM_D | SUBCATEGORY | Subcategory | Copy from source to target system | |
| 42 | DCT | GEOGRAPHY | Area | S/4 Hana | /RPM/ITEM_D | GEOGRAPHY | Area | Copy from source to target system | |
| 44 | DCT | Currency | Currency | S/4 Hana | /RPM/ITEM_D | CURRENCY | CURRENCY | If Legacy Project ID field is empty then Value Mapping: Currency From Company Code | |
| 45 | S/4 Hana | /RPM/ITEM_D | UNIT | Unit | Default to "TAG"(Day) | ||||
| 46 | S/4 Hana | /RPM/ITEM_D | CAP_PERIODTYPE | Capacity Period Breakdown | Default to "12"(Annually) | ||||
| 47 | S/4 Hana | /RPM/ITEM_D | PERIODTYPE | Fin Period Breakdown | Default to "12"(Annually) | ||||
| 48 | DCT | INITIATIVE_ID | INITIATIVE ID | S/4 Hana | /RPM/ITEM_D | INITIATIVE_ID | INITIATIVE ID | Copy from source to target system | |
| 49 | S/4 Hana | /RPM/ITEM_D | ZXX1 | Investment category | This is determined based on the values maintained in Investment Reason | ||||
| 50 | DCT | ZXX2 | Spending Range | S/4 Hana | /RPM/ITEM_D | ZXX2 | Spending Range | Copy from source to target system | |
| 51 | DCT | ZXX3 | Business Unit/ Domain | S/4 Hana | /RPM/ITEM_D | ZXX3 | Business Unit/ Domain | Copy from source to target system | |
| 52 | DCT | ZXX4 | End User market | S/4 Hana | /RPM/ITEM_D | ZXX4 | End User market | Copy from source to target system | |
| 53 | DCT | ZXX5 | Market driver | S/4 Hana | /RPM/ITEM_D | ZXX5 | Market driver | Copy from source to target system | |
| 54 | DCT | ZXX6 | Cluster | S/4 Hana | /RPM/ITEM_D | ZXX6 | Cluster | Copy from source to target system | |
| 55 | DCT | ZXX7 | GBU product family | S/4 Hana | /RPM/ITEM_D | ZXX7 | GBU product family | Copy from source to target system | |
| 56 | DCT | ZXX8 | GBU product category | S/4 Hana | /RPM/ITEM_D | ZXX8 | GBU product category | Copy from source to target system | |
| 57 | DCT | ZXX9 | Product (s) | S/4 Hana | /RPM/ITEM_D | ZXX9 | Product (s) | Copy from source to target system | |
| 58 | DCT | ZXX10 | Export control relevant | S/4 Hana | /RPM/ITEM_D | ZXX10 | Export control relevant | Copy from source to target system | |
| 59 | DCT | ZXX11 | Need-to-know | S/4 Hana | /RPM/ITEM_D | ZXX11 | Need-to-know | Copy from source to target system | |
| 61 | DCT | ZXX13 | EU taxonomy | S/4 Hana | /RPM/ITEM_D | ZXX13 | EU taxonomy | Copy from source to target system | |
| 62 | DCT | ZXX14 | Person responsible Position ID | S/4 Hana | /RPM/ITEM_D | ZXX14 | Person responsible Position ID | Copy from source to target system | |
| 63 | 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 | ||||
| 64 | DCT | ZXX16 | Project Financial Controller Position ID | S/4 Hana | /RPM/ITEM_D | ZXX16 | Project Financial Controller Position ID | Copy from source to target system | |
| 65 | S/4 Hana | /RPM/ITEM_D | ZXX17 | Project Financial Controller Position Name | Value Mapping: Position Name from Position Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001 | ||||
| 66 | DCT | ZXX18 | Starting risk Magnitude | S/4 Hana | /RPM/ITEM_D | ZXX18 | Starting risk Magnitude | Copy from source to target system | |
| 67 | DCT | ZXX19 | Starting risk Likelihood | S/4 Hana | /RPM/ITEM_D | ZXX19 | Starting risk Likelihood | Copy from source to target system | |
| 68 | DCT | ZXX20 | Residual risk Magnitude | S/4 Hana | /RPM/ITEM_D | ZXX20 | Residual risk Magnitude | Copy from source to target system | |
| 69 | DCT | ZXX21 | Residual risk Likelihood | S/4 Hana | /RPM/ITEM_D | ZXX21 | Residual risk Likelihood | Copy from source to target system | |
| 70 | DCT | ZXX22 | Regulatory Mandated Magnitude | S/4 Hana | /RPM/ITEM_D | ZXX22 | Regulatory Mandated Magnitude | Copy from source to target system | |
| 71 | DCT | ZXX23 | Regulatory Mandated Likelihood | S/4 Hana | /RPM/ITEM_D | ZXX23 | Regulatory Mandated Likelihood | Copy from source to target system | |
| 72 | DCT | ZXX24 | Regulatory Mandated Time Horizon (to start project) | S/4 Hana | /RPM/ITEM_D | ZXX24 | Regulatory Mandated Time Horizon (to start project) | Copy from source to target system | |
| 73 | DCT | ZXX25 | Capitalization Date | S/4 Hana | /RPM/ITEM_D | ZXX25 | Capitalization Date | Copy from source to target system | |
| 74 | DCT | ZXX26 | Profit Centre | S/4 Hana | /RPM/ITEM_D | ZXX26 | Profit Centre | Copy from source to target system | |
| 76 | DCT | ZXX27 | WeGo ID | S/4 Hana | /RPM/ITEM_D | ZXX27 | WeGo ID | Copy from source to target system | |
| 77 | DCT | ZXX28 | Investment Reason | S/4 Hana | /RPM/ITEM_D | ZXX28 | Investment Reason | Copy from source to target system | |
| 78 | DCT | ZXX29 | Budget Provision | S/4 Hana | /RPM/ITEM_D | ZXX29 | Budget Provision | Copy from source to target system | |
| 79 | DCT | ZXX30 | Opportunity ID | S/4 Hana | /RPM/ITEM_D | ZXX30 | Opportunity ID | Copy from source to target system | |
| 80 | DCT | ZXX31 | Archetype | S/4 Hana | /RPM/ITEM_D | ZXX31 | Archetype | Copy from source to target system | |
| 81 | DCT | ZXX32 | Must Do Justification | S/4 Hana | /RPM/ITEM_D | ZXX32 | Must Do Justification | Copy from source to target system | |
| 83 | DCT | ZXX34 | Plant | S/4 Hana | /RPM/ITEM_D | ZXX34 | Plant | Copy from source to target system | |
| 84 | DCT | ZXECJ | Justification (Export Control) | S/4 Hana | /RPM/ITEM_D | ZXECJ | Justification (Export Control) | Copy from source to target system | |
| 85 | DCT | ZXX35 | Idea ID | S/4 Hana | /RPM/ITEM_D | ZXX35 | Idea ID | Copy from source to target system | |
| 86 | DCT | ZXX36 | Subsidy Relevant | S/4 Hana | /RPM/ITEM_D | ZXX36 | Subsidy Relevant | Copy from source to target system |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
The Standard template for the upload of Item that can be used for the upload of Items, this includes ability to upload of custom fields, into S/4 Hana: Item Load File.xlsx - Google Sheets
In addition to the fields mapped to the target fields the following is required for the automatic creation of the PS projects if the standard upload program is used
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | S/4 Hana | Upload program | CREATE_CPROJECT | Create Project | If the Legacy ID exists or if Item Type is Capital Lease, Direct Asset Purchase or Capital Spares, then field is X else it remains blank | ||||
| 2 | S/4 | S/4 Hana | Upload program | CPRO_TEMPLATE | Project Template to be used | If CREATE_CPROJECT is active then field must be set. Select PS_TEMPLATE from /RPM/PSPTIT_MAP using ITEM_TYPE | |||
| 3 | S/4 | S/4 Hana | Upload program | PS_LOGSYSTEM | Logical System | If CREATE_CPROJECT is active then field must be set. Select OBL_TYPE from /RPM/PSPTIT_MAP using ITEM_TYPE |
Decision Point
For items types with multiple decision points the active decision point must be updated as part of the item create. If using the standard upload program the active decision point can only be set by changing the statuses of the preceding decision points to end state and the active decision point to start state.
The expectation is that there will be multiple records for each loaded item.
Determination of Preceding decision point
Preceding decision point determined /RPM/ITEM_PHASE-PHASE_ID for ITEM_TYPE.
Determination Decision Point Status
Decision point start status /RPM/DP_STATUS-START_STATUS = X for ITEM_TYPE and PHASE_ID
Decision point start status /RPM/DP_STATUS-END_STATUS = X for ITEM_TYPE and PHASE_ID
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| S/4 Hana | /RPM/DECISION | ITEM | Item ID | ||||||
| S/4 Hana | /RPM/DECISION | DECISION_ID | Decision Point ID | A record for each Preceding decision point and one for the active decision point. | |||||
| S/4 Hana | /RPM/DECISION | NAME | Decision Point Name | Decision Point Name from RPM/PHASE_T using ITEM_TYPE and DECISION_ID | |||||
| S/4 Hana | /RPM/DECISION | STATUS | Decision Point Status | Decision point start status for preceding decision points /RPM/DP_STATUS-END_STATUS = X for ITEM_TYPE and PHASE_ID Decision point start status for active decision point /RPM/DP_STATUS-START_STATUS = X for ITEM_TYPE and PHASE_ID |
Transformation Mapping
| 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 Value Mapping: Old Position ID to New Position ID |
| Plant | Value Mapping: Old Plant to New |
| Profit Center | Value Mapping: Profit Center Old to New |
| Investment Reason | Value Mapping: Investment Reason 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
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 | Load using transaction RPM_DX_ITEM | SyWay Data Team |
| 2 | Load 3 records for < > to validate if data is loaded successfully without errors | SyWay Data Team |
| 3 | Load 3 records for < > to validate if data is loaded successfully without errors | SyWay Data Team |
| 4 | Proceed with full load if steps 2 and 3 are validated | SyWay Data Team |
| 5 | Validate few records loaded by accessing Portfolio Item App | SyWay Data Team |
| 6 | Validate few records loaded by accessing PS Project App | SyWay Data Team |
| 7 | Generate post load report if step 5 is validated | SyWay Data Team |
| 8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
Load Phase and Dependencies
Configuration
Key Configuration requirement
| Item # | Configuration Item |
|---|---|
| 1 | Override Default Global Settings (Master Switches 0002 Switched off - Item will have manual ID) |
| 2 | Define Currency Units |
| 3 | Item Types |
| 4 | Item Type Status |
| 5 | Configure Fields for Mass Import |
| 6 | Category |
| 7 | Sub-Category |
| 8 | Area |
| 9 | Object Link |
| 10 | Plant |
| 11 | DFM Object Links |
| 12 | Map Item Types to PS Project |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1113 | Portfolio Bucket Hierarchy |
| 1023 | Portfolio Initiative |
1073 | Profit Centre |
1019 | Template Projects |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Invalid Data | Invalid Portfolio | Validate DCT content |
Invalid Data | Invalid Bucket ID (Parent ID does not exist) | Validate DCT content |
| Invalid Data | Invalid Item Type | Validate Transformation rules and DCT values |
| Invalid Data | Invalid dates | Validate format of the date fields. |
| Invalid Data | More that one Item per GBU/Company Code/Plant for Capital Lease Item Type | Remove Duplicate values from DCT |
| Invalid Data | More that one Item per GBU/Company Code/Plant for Direct Asset Purchase Item Type | Remove Duplicate values from DCT |
| Invalid Data | More that one Item per GBU/Company Code/Plant for Capital Spares Item Type | Remove Duplicate values from DCT |
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 Item in target S/4 HANA were loaded correctly via Standard Portfolio Item display and table /RPM/ITEM_D |
Conversion Accuracy | Verify that the Project Definition in target were created correctly as per project template |
Conversion Accuracy | Verify that the WBS Structure in target were created correctly as per project template |
Business
Completeness
| Task | Action |
|---|---|
| Verify Count | Extract Item details from Item App in S/4 Hana |
| Verify Count | Extract Project Definitions from Project Definitions App in S/4 Hana, to be same as Item count |
Accuracy
| Task | Action |
|---|---|
| Verify Accuracy | Extract Item details from Item App in S/4 Hana and compare |
| Extract Project details from Project in S/4 Hana and compare to expected. |
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.
