| Status |
| |
|---|---|---|
| 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 agreed migration time frame or has AUC balance.
- Budgeted Operating projects (e.g. Budgeted Maintenance, Marketing, Demolition projects) open as at migration date with postings in the agreed migration time frame
- 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 agreed migration time frame
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 Projects.
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 PS Projects | TBD | S/4 Hana | TBD |
| WP2 | Relevant PS Projects | TBD | 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.
For items the following scenarios with the PS Project definition with WBS element hierarchy is automatically created on loading of the PPM item be created for the.
- Migration relevant project
- Item type Capital Spares,
- Item type Capital Leases
- Item type Capital Purchases
Identification Logic
Capital project is a project that has any WBS elements with a Investment Profile. PRPS-IMPRF
Budgeted Opex is any other project that has any WBS elements with budget. WBS has entry in BPGE for value type 41
IT Project is a project that has a WBS element one of the following criteria
- in WP2 user field 1 starting with IT PRPS-USR00
- in PF2 user field 2 starts with IT PRPS-USR01
- has a WBS element Family is SBS IS
R&I Project is a project meeting one of the following criteria,
- in PF2 Project ID starts with R- PROJ-PSPID
- in WP2 Project ID starts with RR PROJ-PSPID
- has a WBS element with WEGO ID field filled PRPS-ZZ_WEGO_ID
- has a WBS element family indicated as R&I or R&I Others
Industrial projects
- Capital project is a project that has any WBS elements with a Investment Profile. PRPS-IMPRF
- Budgeted Opex is any other project that has any WBS elements with budget. WBS has entry in BPGE for value type 41
- has a WBS element family indicated as GEC, Regular,RegAffairs or Others
Facilities Projects
- Capital project is a project that has any WBS elements with a Investment Profile. PRPS-IMPRF
- Budgeted Opex is any other project that has any WBS elements with budget. WBS has entry in BPGE for value type 41
- has a WBS element family indicated as Facilities
Projects with Status closed.
Table JEST:
Field "Object number" = Key in the object numbers of Project
Field "Status Inactive" = blank,
Field Status = I0046 (Closed)
If status Closed is active further check for postings in the agreed timeframe)
Get All WBS elements
Table PRPS
Field PSPHI For closed projects numbers, Result WBS numbers for closed projects.
Check for postings
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 agreed timeframe.
If count is greater than 0 then the project needs to be migrated.
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. If standard upload is used some system generated fields must be maintained in the transformation.
<CR359 - Custom Field name changes>
| 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 | PORTFOLIO_ID | /RPM/TV_EXTID | Portfolio ID | CHAR | 24 | Mandatory |
| /RPM/ITEM_D | ITEM_TYPE | /RPM/TV_ITEM_ID | Item Type | CHAR | 15 | Mandatory |
| CGPL_TEXT | TEXT1 | CGPL_TEXT1 | Name | CHAR | 40 | Mandatory |
| STXL | CLUSTD (LTEXT for identification in Transformation)) | CLUSTD | Item Description | CLUSTD | 512 | 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 | GEOGRAPHY | RPM_TV_PROJECT_GEOGRAPHY | Company Code | CHAR | 4 | Mandatory |
| /RPM/ITEM_D | CURRENCY | RPM_TV_CURRENCY | CURRENCY | CUKY | 5 | System Generated |
| /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 | SYSPEND_RANGE | Spending Range | NUMC | 2 | System Generated | |
| /RPM/ITEM_D | SYGBU_MHIER | GBU Market Hierarchy | CHAR | 50 | Conditional | |
| /RPM/ITEM_D | SYCORP_HIER | Corporate Hierarchy | CHAR | 50 | Conditional | |
| /RPM/ITEM_D | SYINVST_REASON | Investment Reason | CHAR | 50 | Mandatory | |
| /RPM/ITEM_D | SYSUB_BUS_DRI | Sub Business Driver | CHAR | 50 | System Generated | |
| /RPM/ITEM_D | SYMAIN_BUS_DRI | Main Business Driver | CHAR | 50 | System Generated | |
| /RPM/ITEM_D | SYINVST_CAT | Investment Category | CHAR | 50 | System Generated | |
| /RPM/ITEM_D | SYCLUSTER | /RPM/TV_EXTID | Cluster | CHAR | 24 | Conditional |
| /RPM/ITEM_D | SYPROD_HIER | Product Hierarchy | CHAR | 50 | Conditional | |
| /RPM/ITEM_D | SYEXPO_CO | Export Control | NUMC | 2 | Mandatory | |
| STXL | Z04 | Justification (Export Control) | CLUST | 512 | Conditional | |
| /RPM/ITEM_D | SYNEED_KNOW | Need-to-know | CHAR | 3 | Mandatory | |
| /RPM/ITEM_D | SYPROJ_OWN | Project Owner | NUMC | 8 | Mandatory | |
| /RPM/ITEM_D | SYPFIN_CON | Project Financial Controller | NUMC | 8 | Mandatory | |
| /RPM/ITEM_D | SYSCOR_METH | Scoring Methodology | CHAR | 15 | System Generated | |
| /RPM/ITEM_D | SYST_RISK_MAG | Starting Risk Magnitude | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | SYST_RISK_LIK | Starting Risk Likelihood | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | SYRE_RISK_MAG | Residual Risk Magnitude | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | SYRE_RISK_LIK | Residual Risk Likelihood | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | SYRE_MAN_MAG | Regulatory Mandated Magnitude | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | SYRE_MAN_LIK | Regulatory Mandated Likelihood | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | SYRE_MAN_TIM | Regulatory Mandated Time Horizon (to start project) | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | SYCAP_DAT | Capitalization Date | DATS | 8 | Conditional | |
| /RPM/ITEM_D | SYPRCTR | PRCTR | Profit Centre | CHAR | 10 | Mandatory |
| /RPM/ITEM_D | SYBUDG_PRO | /RPM/TV_EXTID | Budget Provision | CHAR | 24 | Conditional |
| /RPM/ITEM_D | SYOPP_ID | Opportunity ID | CHAR | 18 | Conditional | |
| /RPM/ITEM_D | SYARCHETY | Archetype | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | SYMUST_JUS | Must Do Justification | NUMC | 2 | Mandatory | |
| /RPM/ITEM_D | SYLEG_PRJID | PS_PSPID | Legacy Project ID | CHAR | 24 | Conditional |
| /RPM/ITEM_D | SYWERKS | WERKS_D | Plant | CHAR | 4 | Conditional |
| /RPM/ITEM_D | SYIDEAID | Idea ID | CHAR | 7 | Conditional | |
| /RPM/ITEM_D | SY_ERDAT | Created On | DATS | 8 | System Generated | |
| /RPM/ITEM_D | SYSUBSIDY | Subsidy | CHAR | 1 | Conditional | |
| STXL | Z03 | CLUSTD | Subsidy Relevance | CLUSTD | 512 | Conditional |
| STXL | Z01 | CLUSTD | Key Assumptions | CLUSTD | 512 | Conditional |
| STXL | Z02 | CLUSTD | Variations | CLUSTD | 512 | Conditional |
| STXL | Z05 | CLUSTD | Other Information | CLUSTD | 512 | Conditional |
| STXK | Z08 | CLUSTD | Lessons Learnt | CLUSTD | 512 | Conditional |
Decision Point Table
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| /RPM/DECISION | DECISION_ID | /RPM/TV_EXTID | ID | CHAR | 24 | Mandatory |
| /RPM/DECISION | ITEM_ID | /RPM/TV_EXTID | ITEM_ID | CHAR | 24 | Mandatory |
| CGPL_TEXT | TEXT1 | NAME | CHAR | 40 | Mandatory | |
| /RPM/DECISION | STATUS | /RPM/TV_STATUS_COMMON | STATUS | CHAR | 5 | Conditional |
| /RPM/DECISION | PLAN_START | RPM_TV_PLAN_START | Planned Start Date | DATS | 8 | Conditional |
| /RPM/DECISION | PLAN_FINISH | RPM_TV_PLAN_FINISH | Planned Finish Date | DATS | 8 | Conditional |
| /RPM/DECISION | ACTUAL_START | RPM_TV_ACTUAL_START | Actual Start Date | DATS | 8 | System Generated |
| /RPM/DECISION | ACTUAL_FINISH | RPM_TV_ACTUAL_FINISH | Actual Finish Date | DATS | 8 | System Generated |
| /RPM/DECISION | SYVAR_REF | Variation Reference | CHAR | 60 | Conditional |
<CR359 - Custom Field name changes END>
Item Authorizations (Required only where Need-to-know = yes)
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| ACO_USER | ITEM_ID | /RPM/TV_EXTID | ID | CHAR | 24 | Conditional |
| ACO_USER | ACTIVITY | ACO_ACTVT | Activity | CHAR | 10 | Conditional |
| ACO_USER | USER | ACO_USER_ID | User | CHAR | 12 | Conditional |
Relationship between /RPM/ITEM_D and CGPL_TEXT is the field /RPM/ITEM_D-GUID one to one.
Relationship between /RPM/ITEM_D and /RPM/DECISION is the field /RPM/ITEM_D-GUID one item to many decision points.
Relationship between /RPM/ITEM_D and ACO_USER is the field /RPM/ITEM_D-GUID one item to optional many users.
Data Cleansing
This is a completely new object based on Projects and WBS information. All cleansing requirements dealt with in CNV-1024 Project Definition and CNV-1026 WBS - CAPEX, OPEX, Statistical
| 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
Some projects are considered Need to Know and data is to be restricted to named users only.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.
2 Groups of DCT's have been identified. This is to deal with
Portfolio Item SAP Legacy (for projects with SAP Legacy data)
DCT Rules
<CR359 - Custom Field name changes>
| Field Name | Field Description | Rule | ||
|---|---|---|---|---|
| SNRO | Item ID | Tooltip The Project number from the legacy SAP system. This number will be replaced by the new automatically generated Item ID. The number will remain available in the legacy project ID field on the item. Internal Controls Display from Prep Report - PROJ-PSPID | ||
| GBU | Legacy GBU | Tooltip GBU from Legacy SAP System. Internal Control Display from Prep report - PROJ-ZZGBU | ||
| BU | Legacy Business Unit | Tooltip Business Unit from Legacy SAP System. Internal Control Display from Prep report - PROJ-ZZBU | ||
| PARENT_ID | Parent Bucket ID | Tooltip Unique Identifier for the Item's parent Bucket. In SyWay it is the ID of the L3 bucket where item is assigned The bucket represents the GBU and Function This is a Required Field Internal Controls Dropdown list from the Buckets maintained in CNV_1113 Portfolio Bucket Hierarchy It is a Required Field. | ||
| WBS_FAMILY | Legacy WBS Family | Tooltip WBS Family from Legacy System. Internal Controls Display from Prep Report - PROJ-ZZFAMILY for PF2 or Calculated from PRPS-ZZ_FAMIL for WP2 | ||
| ITEM_TYPE_ECC | Calculated Item Type | Tooltip The suggested item type based on mapping rules. This suggested item type will be used if Item Type is not selected Internal Controls Display from Prep Report - Based on Transformation Rules. | ||
| ITEM_TYPE | Item Type | Tooltip Item types define the structure and behaviour of the portfolio item. In SyWay item types will be based on the function and number of phases of the project. This is a required field when the Calculated Item type is blank. Internal Controls Refer configuration table field /RPM/ITEM_TYPE- ITEM_TYPE for allowed values. It is a Required Field if No Calculated Item Type: Preload Check to be done to confirm that this field is filled in the Data Collection Template | ||
| TEXT1 | Name | Tooltip Short description of the PPM Item No Update Required Internal Controls PrepReport - PROJ-POST1 It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template | ||
| LTEXT | Item Description | Tooltip Long Description, this field is used to provide a concise description of the PPM Item. Entered where information is available Internal Controls Long text from Project Definition | ||
| STATUS | Item Status | Tooltip Represents status of an item. For ongoing projects the status is expected as Z002:Approved Internal Controls 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 in the Data Collection Template | ||
| PLANNED_START | Planned Start | Tooltip Baseline start date of the item/ project used for planning within the portfolio/ bucket. Pre-Populated with Legacy System Project Planned Start Date This is a required field Format (YYYYMMDD) Internal Controls Display from PREP Report - PROJ-PLFAZ It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template | ||
| PLANNED_FINNISH | Planned Finish | Tooltip Baseline End date of the item/ project used for planning within the portfolio/ bucket. Pre-Populated with Legacy System Project Planned End Date This is a required field Format (YYYYMMDD) Internal Controls Display from PREP Report - PROJ-PLSEZ It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template | ||
| IZWEK | Legacy Investment Reason | Tooltip The Investment Reason from the Project defiintion in Legacy SAP System Displayed for Context Only Internal Controls Display from PREP Report - PROJ-ZZ_IZWEK | ||
| IZWEK_DESC | Legacy Investment Reason Description | Tooltip The Investment Reason Description from the Project defintion in Legacy System. Displayed for Context Only Internal Controls Display from PREP Report - Description of Investment | ||
| SYINVST_REASON | Investment Reason | Tooltip In Syway, Investment Reason is level-3 category of investment. This is a required field Internal Controls It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template | ||
| GEOGRAPHY | Company Code | Tooltip The Company Code from the Project Definition in Legacy System Internal Controls Display from PREP Report - PROJ-VBUKR | ||
| Currency | Currency | Tooltip he Currency form project definition in Legacy System This is display only Internal Controls Display from PREP Report - PROJ-PWHIE | ||
| INITIATIVE_ID | INITIATIVE ID | Tooltip Internal ID of Initiative where Item must be linked to Initiative Internal Controls Dropdown list from the Initiatives maintained in CNV_1023 Portfolio Initiatives This is an optional field | ||
| SYGBU_MHIER | GBU Market Hierarchy | Tooltip GBU Market Hierarchy is a GBU-led Market segmentation, applied to both customer and product combination. Any level of the Global Hierarchy can be selected. Applicable and mandatory for PPM Items linked to Buckets with function R&I or IS Internal Controls Values from Global Hierarchy. Mandatory when PPM Item is linked to a bucket with Functions R&I & IS Preload Check to be done to confirm that this field is filled in the Data Collection Template when required | ||
| SYCORP_HIER | Corporate Hierarchy | Tooltip Corporate-led Market segmentation used for reporting. Any level of the Global Hierarchy can be selected. Applicable to all PPM Item types but not mandatory Internal Controls Values from Global Hierarchy. Preload Check to be done to confirm that this field is filled the Data Collection Template when required | ||
| PRJ_GROUP | Project Group | Tooltip Project Group from Project Definition in legacy system Displayed as Context for Cluster and Budget Provision Internal Controls Display from PREP Report - PROJ-ZZGROUP SYCLUSTER | Cluster | Tooltip 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. Internal Controls Selection of Items maintained in with item type Z016 - Cluster |
| SYPROD_HIER | Product Hierarchy | Tooltip Reference to the product hiearchy node ( at any level) required for reporting, Field can be maintained for PPM Items linked to Buckets with IS, R&I, Commercial and Strategy functions. Internal Controls Refer table HRRP_NODE- NODEVALUE where HRRP_NODE- NODETYPE = N and HRYTYPE = MD01" | ||
| SYEXPO_CO | Export Control | Tooltip To identify if the PPM item is applicable for export control governance. Mandatory for all PPM Items. Internal Controls This is a dropdown field from /SYQ/T_EXPORT_CNTL This is a required field: Preload Check to be done to confirm that this field is filled in the Data Collection Template | ||
| Z04 | Justification (Export Control) | Tooltip This field captures the justification for the relevance of export control. Not required if Export Control is "Non Determined" option is selected. Internal Controls This is required field except if SYEXPO_CO "Non Determined": Preload Check to be done to confirm that this field is filled in the Data Collection Template | ||
| SYNEED_KNOW | Need-to-know | Tooltip This field indicates confidential projects. Access will be restricted to named user maintained by Project owner if selection is "Yes Internal Controls Options are Yes or No It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template | ||
| SYPROJ_OWN | Project Owner | Tooltip This field stores the Position of the Project Owner for the PPM Item and is mandatory for all SyWay business functions. Pre-populated with Project Responsible person Position from Legacy SAP System This is a required field Internal Controls From PREP report - PROJ-ZZ_POSIT Refer configuration table field TCJ04-PS_VERNR for field validation. Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. | ||
| ASTNR | Legacy Applicant No | Tooltip Project Applicant from the Project Definition for Legacy SAP system Displayed for Context only Internal Controls From PREP report - PROJ-ASTNR | ||
| ASTNA | Legacy Applicant Name | Tooltip Project Applicant from the Project Definition for Legacy SAP system Displayed for Context only Internal Controls From PREP report - PROJ-ASTNA | ||
| SYPFIN_CON | Project Financial Controller | Tooltip This field stores Position of the Project Financial Controller of a project. This is a required field Internal Controls 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 in the Data Collection Template | ||
| SYST_RISK_MAG | Starting Risk Magnitude | Tooltip For the Risk managed project - this field define the risk magnitude at the start of project. This field is required to be maintained if Scoring Methodology = Risk Investment Reasons flagged as Risk Internal Controls This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field /SYQ/T_RISK_MAGNITUDE Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. | ||
| SYST_RISK_LIK | Starting Risk Likelihood | Tooltip For the Risk managed project - this field define the risk likelihood at the start of project. This field is required to be maintained if Scoring Methodology = Risk Internal Controls This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field /SYQ/T_RISK_LKLHD Preload Check to be done to confirm that this field is filled the Data Collection Template when required | ||
| SYRE_RISK_MAG | Residual Risk Magnitude | Tooltip For the Risk managed project - this field define the risk magnitude at the start of project. This field is required to be maintained if Scoring Methodology = Risk Internal Controls This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field from /SYQ/T_RISK_MAGNITUDE Preload Check to be done to confirm that this field is filled the Data Collection Template when required | ||
| SYRE_RISK_LIK | Residual Risk Likelihood | Tooltip For the Risk managed ongoing approved project - this field defines remaining risk likelihood. This field is required to be maintained if Scoring Methodology = Risk Internal Controls This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field from /SYQ/T_RISK_LKLHD Preload Check to be done to confirm that this field is filled the Data Collection Template when required | ||
| SYRE_MAN_MAG | Regulatory Mandated Magnitude | Tooltip IImpact of regulatory compliance on project delivery. This field is required to be maintained if Scoring Methodology = Regulatory Investment Reason flagged as Regulatory Internal Controls This field is required to be maintained if Scoring Methodology = Regulatory This is a dropdown field from /SYQ/T_REG_MAGNITUDE Preload Check to be done to confirm that this field is filled the Data Collection Template when required | ||
| SYRE_MAN_LIK | Regulatory Mandated Likelihood | Tooltip Probability of impact due to regulatory compliance. This field is required to be maintained if Scoring Methodology = Regulatory Internal Controls This field is required to be maintained if Scoring Methodology = Regulatory This is a dropdown field from /SYQ/T_REG_LKLHD Preload Check to be done to confirm that this field is filled the Data Collection Template when required | ||
| SYRE_MAN_TIM | Regulatory Mandated Time Horizon (to start project) | Tooltip Regulatory defined deadline by which a project must commence. This field is required to be maintained if Scoring Methodology = Regulatory Internal Controls This field is required to be maintained if Scoring Methodology = Regulatory This is a dropdown field from /SYQ/T_REG_TIME_HORIZON Preload Check to be done to confirm that this field is filled the Data Collection Template when required | ||
| SYCAP_DAT | Capitalization Date | Tooltip Stores the capitalization date for the purpose of "Depreciation forecast". This date is mandatory for the Capital Projects Item types. Format (YYYYMMDD) Internal Controls This date is mandatory for the Capital Projects Item types. Item Types are Z001,Z002, Z003, Z008, Z009, Z011 Preload Check to be done to confirm that this field is filled the Data Collection Template when required | ||
| SYPRCTR | Profit Center | Tooltip Profit Centre represents the GBU/Plant where the project is performed., Profit centre on PPM item will be validated with the PC on the Parent Bucket to check they belong to the same group. This will ensure PPM items are created under correct GBU bucket. If plant is maintained then Profit Center is derived from it. Pre-populated with Profit Center from the Project Definition No Update Required Internal Controls From Prep Report - PROJ-PRCTR Refer master table field CEPC-PRCTR for Profit center list. the Data Collection Template, It is required only if Plant is not filled: Preload Check to be done to confirm that this field is filled, and is aligned with the PC on the Parent Bucket, first character of the Profit centers must match | ||
| SYBUDG_PRO | Budget Provision | Tooltip Used to group those PPM Items where the budget is drawn from the Budget provision Item. Internal Controls Selection of Items maintained in with item type Z015 - Budget Provision | ||
| SYOPP_ID | Opportunity ID | Tooltip Stores the CRM opportunity ID where applicable. This is an optional field. | ||
| SYARCHETY | Archetype | Tooltip This field represents the classification of the R&I projects as different archetypes. Not applicable for Items linked to Buckets with IS, IT & Facility/ Others functions. Internal Controls This is a dropdown field from /SYQ/T_ARCHETYPE Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. | ||
| SYMUST_JUS | Must Do Justification | Tooltip This field provides input to the ranking of items in the priortization dashboard and is relevant across all PPM item types. Internal Controls This is a dropdown field from /SYQ/T_MUST_DO This is a required field | ||
| SYWERKS | Plant | Tooltip Plant represent a site of the PPM Item. Plant is maintained when available. Pre-populated with Plant from the Project Definition No Update Required Internal Control From Prep Report - PROJ-WERKS Preload validation that plant exist, T001W and is maintained for the Company Code This is an optional field. | ||
| SYIDEAID | Idea ID | Tooltip Field to store the Idea number where this is known. This is an optional field for migration | ||
| SYSUBSIDY | Subsidy | Tooltip Use this field if the project is eligible for government or institutional subsidies. This is an optional field for migration Internal Control This is a true / false field | ||
| Z03 | Subsidy Relevance | Tooltip This field is used to provide a concise description of the Subsidy Relevance. (This is a long text field) Required If Subsidy field is selected. Internal Control Required If Subsidy field is selected. | ||
| Z01 | Key Assumptions | Tooltip This field is used to provide key Assumptions related to projects. (This is a long text field) Conditional for Items where assumptions are to be maintained, This is an optional field for migration | ||
| Z02 | Variations | Tooltip This field is used to provide details about key project variations. (This is a long text field) Conditional for Items where assumptions are to be maintained, This is an optional field for migration | ||
| Z05 | Other Information | Tooltip This field is used to provide additional details about project. (This is a long text field) This is an optional field for migration | ||
| Z08 | Lessons Learnt | Tooltip Long-text description, this field is used to record the project insights and key takeaways of a project This is an optional field for migration | ||
| ACT_DPCPT | Active Decision Point | Tooltip Indicates the currently active Decision Point (Stage Gate) for the item. Relevant for the following item types Z001 Industrial with Qualification Z002 Industrial w/out Qualification Z004 New Product Introduction Z005 Product & Process Improvement Z008 IT Full Lifecycle Project Z017 New Application Development To be maintained when item is not in initial phase Internal Control Drop down field from /RPM/ITEM_PHASE based on selected ITEM_TYPE |
Portfolio ITEM Construct (Used for projects without SAP Legacy Project)
DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| SNRO | Item Serial Number | This field is display only and is filled with a sequential number when user adds a item record |
| PARENT_ID | Parent Bucket ID | Tooltip Unique Identifier for the Item's parent Bucket. In SyWay it is the ID of the L3 bucket where item is assigned The bucket represents the GBU and Function This is a Required Field Internal Controls Dropdown list from the Buckets maintained in CNV_1113 Portfolio Bucket Hierarchy It is a Required Field. |
| ITEM_TYPE | Type | Tooltip Item types define the structure and behaviour of the portfolio item. In SyWay item types will be based on the function and number of phases of the project. This is a required field Internal Controls Refer configuration table field /RPM/ITEM_TYPE- ITEM_TYPE for allowed values. It is a Required Field |
| TEXT1 | Name | Tooltip Short description of the PPM Item Internal Controls It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| LTEXT | Item Description | Tooltip Long Description, this field is used to provide a concise description of the PPM Item. Entered where information is available |
| STATUS | Item Status | Tooltip Represents status of an item For ongoing projects the status is expected as Z002:Approved Internal Controls 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 in the Data Collection Template |
| PLANNED_START | Planned Start | Tooltip Baseline start date of the item/ project used for planning within the portfolio/ bucket. This is a required field Format (YYYYMMDD) Internal Controls It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| PLANNED_FINNISH | Planned Finish | Tooltip Baseline End date of the item/ project used for planning within the portfolio/ bucket. This is a required field Format (YYYYMMDD) Internal Controls It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| CATEGORY | Investment Reason | Tooltip In Syway, Investment Reason is level-3 category of investment. This is a required field Internal Controls It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| GEOGRAPHY | Company Code | Tooltip In SyWay, this field Represents Company code; the legal entity in which the Syway Project will be executed. Internal Controls Refer configuration table field V_DPR_AREA- AREA for the allowed values. It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| INITIATIVE_ID | INITIATIVE ID | Tooltip Internal ID of Initiative where Item must be linked to Initiative Internal Controls Dropdown list from the Initiatives maintained in CNV_1023 Portfolio Initiatives This is an optional field |
| SYGBU_MHIER | GBU Market Hierarchy | Tooltip GBU Market Hierarchy is a GBU-led Market segmentation, applied to both customer and product combination. Any level of the Global Hierarchy can be selected. Applicable and mandatory for PPM Items linked to Buckets with function R&I or IS Internal Controls Values from Global Hierarchy. Mandatory when PPM Item is linked to a bucket with Functions R&I & IS Preload Check to be done to confirm that this field is filled in the Data Collection Template when required |
| SYCORP_HIER | Corporate Hierarchy | Tooltip Corporate-led Market segmentation used for reporting. Any level of the Global Hierarchy can be selected. Applicable to all PPM Item types but not mandatory Internal Controls Values from Global Hierarchy. Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| SYCLUSTER | Cluster | Tooltip 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. Internal Controls Selection of Items maintained in with item type Z016 - Cluster |
| SYPROD_HIER | Product Hierarchy | Tooltip Reference to the product hierarchy node ( at any level) required for reporting, Field can be maintained for PPM Items linked to Buckets with IS, R&I, Commercial and Strategy functions. Internal Controls Refer table HRRP_NODE- NODEVALUE where HRRP_NODE- NODETYPE = N and HRYTYPE = MD01" |
| SYEXPO_CO | Export Control | Tooltip To identify if the PPM item is applicable for export control governance. Mandatory for all PPM Items. Internal Controls This is a dropdown field from /SYQ/T_EXPORT_CNTL This is a required field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| Z04 | Justification (Export Control) | Tooltip This field captures the justification for the relevance of export control. Not required if Export Control is "Non Determined" option is selected. Internal Controls This is required field except if SYEXPO_CO "Non Determined": Preload Check to be done to confirm that this field |
| SYNEED_KNOW | Need-to-know | Tooltip This field indicates confidential projects. Access will be restricted to named user maintained by Project owner if selection is "Yes Internal Controls Options are Yes or No It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| SYPROJ_OWN | Project Owner | Tooltip This field stores the Position of the Project Owner for the PPM Item and is mandatory for all SyWay business functions. This is a required field Internal Controls From PREP report - PROJ-ZZ_POSIT Refer configuration table field TCJ04-PS_VERNR for field validation. Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. |
| SYPFIN_CON | Project Financial Controller | Tooltip This field stores Position of the Project Financial Controller of a project. This is a required field Internal Controls 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 in the Data Collection Template |
| SYST_RISK_MAG | Starting Risk Magnitude | Tooltip For the Risk managed project - this field define the risk magnitude at the start of project. This field is required to be maintained if Scoring Methodology = Risk Investment Reasons flagged as Risk Internal Controls This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field /SYQ/T_RISK_MAGNITUDE Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. |
| SYST_RISK_LIK | Starting Risk Likelihood | Tooltip For the Risk managed project - this field define the risk likelihood at the start of project. This field is required to be maintained if Scoring Methodology = Risk Internal Controls This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field /SYQ/T_RISK_LKLHD Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| SYRE_RISK_MAG | Residual Risk Magnitude | Tooltip For the Risk managed project - this field define the risk magnitude at the start of project. This field is required to be maintained if Scoring Methodology = Risk Internal Controls This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field from /SYQ/T_RISK_MAGNITUDE Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| SYRE_RISK_LIK | Residual Risk Likelihood | Tooltip For the Risk managed ongoing approved project - this field defines remaining risk likelihood. This field is required to be maintained if Scoring Methodology = Risk Internal Controls This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field from /SYQ/T_RISK_LKLHD Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| SYRE_MAN_MAG | Regulatory Mandated Magnitude | Tooltip IImpact of regulatory compliance on project delivery. This field is required to be maintained if Scoring Methodology = Regulatory Investment Reason flagged as Regulatory Internal Controls This field is required to be maintained if Scoring Methodology = Regulatory This is a dropdown field from /SYQ/T_REG_MAGNITUDE Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| SYRE_MAN_LIK | Regulatory Mandated Likelihood | Tooltip Probability of impact due to regulatory compliance. This field is required to be maintained if Scoring Methodology = Regulatory Internal Controls This field is required to be maintained if Scoring Methodology = Regulatory This is a dropdown field from /SYQ/T_REG_LKLHD Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| SYRE_MAN_TIM | Regulatory Mandated Time Horizon (to start project) | Tooltip Regulatory defined deadline by which a project must commence. This field is required to be maintained if Scoring Methodology = Regulatory Internal Controls This field is required to be maintained if Scoring Methodology = Regulatory This is a dropdown field from /SYQ/T_REG_TIME_HORIZON Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| SYCAP_DAT | Capitalization Date | Tooltip Stores the capitalization date for the purpose of "Depreciation forecast". This date is mandatory for the Capital Projects Item types. Format (YYYYMMDD) Internal Controls This date is mandatory for the Capital Projects Item types. Item Types are Z001,Z002, Z003, Z008, Z009, Z011 Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| SYPRCTR | Profit Center | Tooltip Profit Centre represents the GBU/Plant where the project is performed., Profit centre on PPM item will be validated with the PC on the Parent Bucket to check they belong to the same group. This will ensure PPM items are created under correct GBU bucket. If plant is maintained then Profit Center is derived from it. Required if the Plant field is not filled. Internal Controls Refer master table field CEPC-PRCTR for Profit center list. the Data Collection Template, It is required only if Plant is not filled: Preload Check to be done to confirm that this field is filled, and is aligned with the PC on the Parent Bucket, first character of the Profit centers must match |
| SYBUDG_PRO | Budget Provision | Tooltip Used to group those PPM Items where the budget is drawn from the Budget provision Item. Internal Controls Selection of Items maintained in with item type Z015 - Budget Provision |
| SYOPP_ID | Opportunity ID | Tooltip Stores the CRM opportunity ID where applicable. This is an optional field. |
| SYARCHETY | Archetype | Tooltip This field represents the classification of the R&I projects as different archetypes. Not applicable for Items linked to Buckets with IS, IT & Facility/ Others functions. Internal Controls This is a dropdown field from /SYQ/T_ARCHETYPE Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. |
| SYMUST_JUS | Must Do Justification | Tooltip This field provides input to the ranking of items in the prioritization dashboard and is relevant across all PPM item types. Internal Controls This is a dropdown field from /SYQ/T_MUST_DO This is a required field |
| SYWERKS | Plant | Tooltip Plant represent a site of the PPM Item. Plant is maintained when available. Plants are restricted by Company Code Internal Control Preload validation that plant exist, T001W and is maintained for the Company Code This is an optional field. |
| SYIDEAID | Idea ID | Tooltip Field to store the Idea number where this is known. This is an optional field for migration |
| SYSUBSIDY | Subsidy | Tooltip Use this field if the project is eligible for government or institutional subsidies. This is an optional field for migration Internal Control This is a true / false field |
| Z03 | Subsidy Relevance | Tooltip This field is used to provide a concise description of the Subsidy Relevance. (This is a long text field) Required If Subsidy field is selected. Internal Control Required If Subsidy field is selected. |
| Z01 | Key Assumptions | Tooltip This field is used to provide key Assumptions related to projects. (This is a long text field) Conditional for Items where assumptions are to be maintained, This is an optional field for migration |
| Z02 | Variations | Tooltip This field is used to provide details about key project variations. (This is a long text field) Conditional for Items where assumptions are to be maintained, This is an optional field for migration |
| Z05 | Other Information | Tooltip This field is used to provide additional details about project. (This is a long text field) This is an optional field for migration |
| Z08 | Lessons Learnt | Tooltip Long-text description, this field is used to record the project insights and key takeaways of a project This is an optional field for migration |
| ACT_DPCPT | Active Decision Point | Tooltip Indicates the currently active Decision Point (Stage Gate) for the item. Relevant for the following item types Z001 Industrial with Qualification Z002 Industrial w/out Qualification Z004 New Product Introduction Z005 Product & Process Improvement Z008 IT Full Lifecycle Project Z017 New Application Development To be maintained when item is not in initial phase Internal Control Drop down field from /RPM/ITEM_PHASE based on selected ITEM_TYPE |
Decision Point. The list of decision points for an item is based on configuration table /RPM/ITEM_PHASE-PHASE_ID for ITEM_TYPE, when item is added to this DCT the full list of decision points for the item type must be added to the DCT.
| Field Name | Field Description | Rule |
|---|---|---|
| SNRO | Item Serial Number | Unique Identifier Item serial numbers It is a dropdown of the Item numbers maintained in the main DCT |
| DECISION_ID | Decision Point ID | Once the User selects the Item number the full list of Decision points relevant to the Item type is to be displayed. System generated Parent ID of the Decision Point This is a display only field |
| NAME | Decision Point Description | Name of the decision point, part of the customisation and can't be changed. This is a display only field |
| PLAN_START | Decision Point Planned Start Date | This field stores the plan start date of a decision point for the items where there is SG tracking required |
| PLAN_FINISH | Decision Point Planned End Date | This field stores the plan finish date of a decision point where SG tacking is required |
| ACTUAL_START | Decision Point Actual Start Date | This field stores the actual start date of a decision point derived from the initiation date of respective stage gate approval. |
| ACTUAL_FINISH | Decision Point Actual End Date | This field stores the actual finish date of a decision point derived from the approved date of respective stage gate approval. |
| SYVAR_REF | Variation Reference | This field stores the identifier and short description of Variation required to variation budget approval |
<CR359 - Custom Field name changes END>
Authorization - For "Need-to-know" projects, named users will be added manually.
| Field Name | Field Description | Rule |
|---|---|---|
| SNRO | Item Serial Number | Unique Identifier Item serial numbers It is a dropdown of the Item numbers maintained in the main DCT and marked as Need to Know. |
| USER_ID | SAP User Name | Named user who should have read access to the Need to Know Item |
In conjunction with DCT business user will be provided with Person Responsible / Applicant list for reference.
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|
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
<CR359 - Custom Field name changes>
Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
1 | DCT | PARENT_ID | Parent Bucket ID | S/4 Hana | /RPM/ITEM_D | PARENT_ID | Parent Bucket ID | Manually copy from Non ECC source | |
2 | S/4 Hana | /RPM/ITEM_D | PORTFOLIO_ID | Portfolio ID | Global Default "SYENSQO" | ||||
3 | 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-ZZ_IZWEK = B4 Then Z011 IF PROJ-ZZ_IZWEK = 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 | |||
4 | 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-ZZ_IZWEK = B4 Then Z011 IF PROJ-ZZ_IZWEK = 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 | ||
5 | DCT | ITEM_TYPE | Type | S/4 Hana | /RPM/ITEM_D | ITEM_TYPE | Type | Manually copy from Non ECC source | |
6 | WP2/PF2 | PROJ | POST1 | Project Description | S/4 Hana | CGPL_TEXT | TEXT1 | Name | Copy source to target |
7 | DCT | TEXT1 | Name | S/4 Hana | CGPL_TEXT | TEXT1 | Name | Manually copy from Non ECC source | |
8 | WP2/PF2 | STXL | LTEXT | Long Description | S/4 Hana | STXL | LTEXT | Description | Copy source to target |
9 | DCT | LTEXT | Item Description | S/4 Hana | STXL | LTEXT | Description | Manually copy from Non ECC source | |
10 | DCT | STATUS | Item Status | S/4 Hana | /RPM/ITEM_D | STATUS | Item Status | Manually copy from Non ECC source | |
11 | WP2/PF2 | PROJ | PLFAZ | Project planned start date | S/4 Hana | /RPM/ITEM_D | PLANNED_START | Planned Start | Copy from source, format YYYYMMDD |
12 | DCT | PLANNED_START | Planned Start | S/4 Hana | /RPM/ITEM_D | PLANNED_START | Planned Start | Manually copy from Non ECC source | |
13 | WP2/PF2 | PROJ | PLSEZ | Project planned finish date | S/4 Hana | /RPM/ITEM_D | PLANNED_FINISH | Planned Finish | Copy from source, format YYYYMMDD |
14 | DCT | PLANNED_FINISH | Planned Finish | S/4 Hana | /RPM/ITEM_D | PLANNED_FINISH | Planned Finish | Manually copy from Non ECC source | |
15 | DCT | SYINVST_REASON | Investment Reason | S/4 Hana | /RPM/ITEM_D | SYINVST_REASON | Investment Reason | Manually copy from Non ECC source | |
16 | S/4 Hana | /RPM/ITEM_D | SYSUB_BUS_DRI | Sub Business Driver | Value Mapping: Investment Reason Based on the SYINVST_REASON field | ||||
17 | S/4 Hana | /RPM/ITEM_D | SYMAIN_BUS_DRI | Main Business Driver | Value Mapping: Investment Reason Based on theSYINVST_REASON field | ||||
18 | S/4 Hana | /RPM/ITEM_D | SYINVST_CAT | Investment Category | Value Mapping: Investment Reason Based on theSYINVST_REASON field | ||||
19 | WP2/PF2 | PROJ | VBUKR | Company code | S/4 Hana | /RPM/ITEM_D | GEOGRAPHY | Company Code | Value Mapping: Old to New Company Code |
20 | DCT | GEOGRAPHY | Company code | S/4 Hana | /RPM/ITEM_D | GEOGRAPHY | Company Code | Manually copy from Non ECC source | |
21 | WP2/PF2 | PROJ | PWHIE | WBS currency | S/4 Hana | /RPM/ITEM_D | CURRENCY | CURRENCY | Copy from Source |
22 | 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 | |
23 | S/4 Hana | /RPM/ITEM_D | UNIT | Unit | Default to "TAG"(Day) | ||||
24 | S/4 Hana | /RPM/ITEM_D | CAP_PERIODTYPE | Capacity Period Breakdown | Default to "12"(Annually) | ||||
25 | S/4 Hana | /RPM/ITEM_D | PERIODTYPE | Fin Period Breakdown | Default to "12"(Annually) | ||||
26 | DCT | INITIATIVE_ID | INITIATIVE ID | S/4 Hana | /RPM/ITEM_D | INITIATIVE_ID | INITIATIVE ID | Manually copy from Non ECC source | |
28 | DCT | SYGBU_MHIER | GBU Market Hierarchy | S/4 Hana | /RPM/ITEM_D | SYGBU_MHIER | GBU Market Hierarchy | Manually copy from Non ECC source | |
30 | DCT | SYCORP_HIER | Corporate Hierarchy | S/4 Hana | /RPM/ITEM_D | SYCORP_HIER | Corporate Hierarchy | Manually copy from Non ECC source | |
31 | DCT | SYCLUSTER | Cluster | S/4 Hana | /RPM/ITEM_D | SYCLUSTER | Cluster | Manually copy from Non ECC source | |
32 | DCT | SYPROD_HIER | Product Hierarchy | S/4 Hana | /RPM/ITEM_D | SYPROD_HIER | Product Hierarchy | Manually copy from Non ECC source | |
33 | DCT | SYEXPO_CO | Export control | S/4 Hana | /RPM/ITEM_D | SYEXPO_CO | Export Control | Manually copy from Non ECC source | |
34 | DCT | Justification | Justification (Export Control) | S/4 Hana | STXL | Z04 | Justification (Export Control) | Manually copy from Non ECC source | |
35 | DCT | SYNEED_KNOW | Need-to-know | S/4 Hana | /RPM/ITEM_D | SYNEED_KNOW | Need-to-know | Manually copy from Non ECC source | |
36 | WP2/PF2 | PROJ | ZZ_POSIT | Position of the person responsible | S/4 Hana | /RPM/ITEM_D | SYPROJ_OWN | Project Owner | Value Mapping: Old Position ID to New Position ID |
37 | DCT | SYPROJ_OWN | Project Owner | S/4 Hana | /RPM/ITEM_D | SYPROJ_OWN | Project Owner | Manually copy from Non ECC source | |
39 | DCT | SYPFIN_CON | Project Financial Controller Position ID | S/4 Hana | /RPM/ITEM_D | SYPFIN_CON | Project Financial Controller Position ID | Manually copy from Non ECC source | |
41 | S/4 Hana | /RPM/ITEM_D | SYSCOR_METH | Scoring Methodology | Value Mapping: Investment Reason Based on the SYINVST_REASON field | ||||
42 | DCT | SYST_RISK_MAG | Starting risk Magnitude | S/4 Hana | /RPM/ITEM_D | SYST_RISK_MAG | Starting risk Magnitude | Manually copy from Non ECC source | |
43 | DCT | SYST_RISK_LIK | Starting risk Likelihood | S/4 Hana | /RPM/ITEM_D | SYST_RISK_LIK | Starting risk Likelihood | Manually copy from Non ECC source | |
44 | DCT | SYRE_RISK_MAG | Residual risk Magnitude | S/4 Hana | /RPM/ITEM_D | SYRE_RISK_MAG | Residual risk Magnitude | Manually copy from Non ECC source | |
45 | DCT | SYRE_RISK_LIK | Residual risk Likelihood | S/4 Hana | /RPM/ITEM_D | SYRE_RISK_LIK | Residual risk Likelihood | Manually copy from Non ECC source | |
46 | DCT | SYRE_MAN_MAG | Regulatory Mandated Magnitude | S/4 Hana | /RPM/ITEM_D | SYRE_MAN_MAG | Regulatory Mandated Magnitude | Manually copy from Non ECC source | |
47 | DCT | SYRE_MAN_LIK | Regulatory Mandated Likelihood | S/4 Hana | /RPM/ITEM_D | SYRE_MAN_LIK | Regulatory Mandated Likelihood | Manually copy from Non ECC source | |
48 | DCT | SYRE_MAN_TIM | Regulatory Mandated Time Horizon (to start project) | S/4 Hana | /RPM/ITEM_D | SYRE_MAN_TIM | Regulatory Mandated Time Horizon (to start project) | Manually copy from Non ECC source | |
49 | DCT | SYCAP_DAT | Capitalization Date | S/4 Hana | /RPM/ITEM_D | SYCAP_DAT | Capitalization Date | Manually copy from Non ECC source | |
50 | WP2/PF2 | PROJ | PRCTR | Profit Center | S/4 Hana | /RPM/ITEM_D | SYPRCTR | Profit Centre | Value Mapping: Profit Center Old to New |
51 | DCT | SYPRCTR | Profit Centre | S/4 Hana | /RPM/ITEM_D | SYPRCTR | Profit Centre | Manually copy from Non ECC source | |
54 | DCT | SYBUDG_PRO | Budget Provision | S/4 Hana | /RPM/ITEM_D | SYBUDG_PRO | Budget Provision | Manually copy from Non ECC source | |
55 | DCT | SYOPP_ID | Opportunity ID | S/4 Hana | /RPM/ITEM_D | SYOPP_ID | Opportunity ID | Manually copy from Non ECC source | |
56 | DCT | SYARCHETY | Archetype | S/4 Hana | /RPM/ITEM_D | SYARCHETY | Archetype | Manually copy from Non ECC source | |
57 | DCT | SYMUST_JUS | Must Do Justification | S/4 Hana | /RPM/ITEM_D | SYMUST_JUS | Must Do Justification | Manually copy from Non ECC source | |
58 | WP2/PF2 | PROJ | PSPID | ID | S/4 Hana | /RPM/ITEM_D | SYLEG_PRJID | 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 |
DCT | SNRO | Serial Number | S/4 Hana | /RPM/ITEM_D | SYLEG_PRJID | Legacy Project ID (For existing records this is the key for related DCT values) For additional Items not from source this will be empty. | Manually copy From Non ECC Source | ||
59 | WP2/PF2 | PROJ | WERKS | Plant | S/4 Hana | /RPM/ITEM_D | SYWERKS | Plant | Value Mapping: Old Plant to New |
60 | DCT | SYWERKS | Plant | S/4 Hana | /RPM/ITEM_D | SYWERKS | Plant | Manually copy from Non ECC source | |
61 | DCT | SYIDEAID | Idea ID | S/4 Hana | /RPM/ITEM_D | SYIDEAID | Idea ID | Manually copy from Non ECC source | |
62 | DCT | SYSUBSIDY | Subsidy | S/4 Hana | /RPM/ITEM_D | SYSUBSIDY | Subsidy | Manually copy from Non ECC source | |
63 | DCT | Sub_Relevance | Subsidy Relevance | S/4 Hana | STXL | Z03 | Subsidy Relevance | Manually copy from Non ECC source | |
64 | DCT | Key_Assump | Key Assumptions | S/4 Hana | STXL | Z01 | Key Assumptions | Manually copy from Non ECC source | |
65 | DCT | Variations | Variations | S/4 Hana | STXL | Z02 | Variations | Manually copy from Non ECC source | |
66 | DCT | Other | Other Information | S/4 Hana | STXL | Z05 | Other Information | Manually copy from Non ECC source | |
DCT | Lessons | Lessons Learnt | S/4 Hana | STXL | Z08 | Lessons Learnt | Manually copy from Non ECC source |
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 |
|---|---|---|---|---|---|---|---|---|---|
66 | 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 | ||||
67 | 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 | |||
68 | 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 this is done using the Item Decision Point work sheet.
If using the standard upload program Decision Point sheet 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.
In addition users may have maintained Decision point dates in the DCT, these updated dates are to be included in the requirement
The expectation is that there will be multiple records for each loaded item.
/RPM/ITEM_PHASE-PHASE_ID for ITEM_TYPE.
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 |
|---|---|---|---|---|---|---|---|---|---|
1 | S/4 Hana | /RPM/DECISION | ITEM | Item ID | |||||
2 | S/4 Hana | /RPM/DECISION | DECISION_ID | Decision Point ID | The List of decision points for each item is based on the item type as per | ||||
3 | S/4 Hana | /RPM/DECISION | NAME | Decision Point Name | Decision Point Name from RPM/PHASE_T using ITEM_TYPE and DECISION_ID | ||||
4 | 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 | ||||
5 | DCT | Decision Point | PLAN_START | Decision Point Planned Start Date | S/4 Hana | /RPM/DECISION | PLAN_START | Decision Point Planned Start Date | Manually copy from Non ECC source |
6 | DCT | Decision Point | PLAN_FINISH | Decision Point Planned End Date | S/4 Hana | /RPM/DECISION | PLAN_FINISH | Decision Point Planned End Date | Manually copy from Non ECC source |
7 | DCT | Decision Point | ACTUAL_START | Decision Point Actual Start Date | S/4 Hana | /RPM/DECISION | ACTUAL_START | Decision Point Actual Start Date | Manually copy from Non ECC source |
8 | DCT | Decision Point | ACTUAL_FINISH | Decision Point Actual End Date | S/4 Hana | /RPM/DECISION | ACTUAL_FINISH | Decision Point Actual End Date | Manually copy from Non ECC source |
9 | DCT | Decision Point | SYVAR_REF | Variation Reference | S/4 Hana | /RPM/DECISION | SYVAR_REF | Variation Reference | Manually copy from Non ECC source |
<CR359 - Custom Field name changes END>
Authorization
For items with Need to know flag set the authorization to display the item is restricted to named users only. If using the standard upload this is done using the Item Authorization work sheet.
Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
1 | DCT | Authorization | SNRO | Item Serial Number | S/4 Hana | ACO_USER | ITEM_ID | Object ID | Manually copy from Non ECC source |
2 | S/4 Hana | ACO_USER | ACTIVITY | Activity | Default to activity "READ" | ||||
3 | DCT | Authorization | USER_ID | SAP User Name | S/4 Hana | ACO_USER | USER | User ID | Manually copy from Non ECC source |
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 to Other fields. Investment Reason, Main Business Driver, Sub Business Driver, Investment Category, Scoring Methodology |
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 | Technology Type |
| 9 | Group |
| 10 | Area |
| 11 | Object Link |
| 12 | Plant |
| 13 | DFM Object Links |
| 14 | Map Item Types to PS Project |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1113 | Portfolio Bucket Hierarchy |
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 and that the project status has been set to released using transaction CN41n |
Conversion Accuracy | Verify that the WBS Structure in target were created correctly as per project template WBS status has been set to released using transaction CN41n |
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 results |
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.
- Item types to be maintained by business where it cannot be determined based on transformation rules, this includes R&I where split between the new item types not possible.
Change log
| Change History | ||
|---|---|---|
|
