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:

    1. 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.
    2. Budgeted Operating projects (e.g. Budgeted Maintenance, Marketing, Demolition projects) open as at migration date with postings in the agreed migration time frame
    3. Closed Capital Projects with postings within the agreed timeframe.
    4. Closed Budgeted Operating projects with postings within the  agreed timeframe. 
    5. 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

    1. Project Definition in out of scope Company Codes
    2. Project Definitions in out of scope Plants.
    3. Project which has deletion indicator set
    4. Project marked as closed and not included in C, D and E above.
    5. 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 

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2Relevant PS ProjectsTBDS/4 HanaTBD
WP2Relevant PS ProjectsTBDS/4 HanaTBD
DCT

S/4 HanaTBD

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

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.   If standard upload is used some system generated fields must be maintained in the transformation.

TableFieldData ElementField DescriptionData TypeLengthRequirement
/RPM/ITEM_DEXTERNAL_ID/RPM/TV_EXTIDIDCHAR24System Generated
/RPM/ITEM_DPARENT_ID/RPM/TV_EXTIDParent Bucket IDCHAR24Mandatory
/RPM/ITEM_DPORTFOLIO_ID/RPM/TV_EXTIDPortfolio IDCHAR24Mandatory
/RPM/ITEM_DITEM_TYPE/RPM/TV_ITEM_IDItem TypeCHAR15Mandatory
CGPL_TEXTTEXT1CGPL_TEXT1NameCHAR40Mandatory
STXLCLUSTD (LTEXT for identification in Transformation))CLUSTDItem DescriptionCLUSTD512Conditional
/RPM/ITEM_DSTATUS/RPM/TV_STATUS_COMMONItem StatusCHAR5Mandatory
/RPM/ITEM_DPLANNED_STARTRPM_TV_PLAN_STARTPlanned StartDATS8Mandatory
/RPM/ITEM_DPLANNED_FINISHRPM_TV_PLAN_FINISHPlanned FinishDATS8Mandatory
/RPM/ITEM_DGEOGRAPHYRPM_TV_PROJECT_GEOGRAPHYCompany CodeCHAR4Mandatory
/RPM/ITEM_DCURRENCYRPM_TV_CURRENCYCURRENCYCUKY5System Generated
/RPM/ITEM_DUNITRPM_TV_UNITUnitUNIT3System Generated
/RPM/ITEM_DCAP_PERIODTYPE/RPM/TV_CAP_PERIOD_TYPECapacity Period BreakdownNUMC2System Generated
/RPM/ITEM_DPERIODTYPE/RPM/TV_PERIOD_TYPEFin Period BreakdownNUMC2System Generated
/RPM/ITEM_DINITIATIVE_IDINM_TV_EXTIDINITIATIVE IDCHAR24Conditional
/RPM/ITEM_DSYSPEND_RANGE
Spending RangeNUMC2System Generated
/RPM/ITEM_DSYGBU_MHIER
GBU Market HierarchyCHAR50Conditional
/RPM/ITEM_DSYCORP_HIER
Corporate HierarchyCHAR50Conditional
/RPM/ITEM_DSYINVST_REASON
Investment ReasonCHAR50Mandatory
/RPM/ITEM_DSYSUB_BUS_DRI
Sub Business DriverCHAR50System Generated
/RPM/ITEM_DSYMAIN_BUS_DRI
Main Business DriverCHAR50System Generated
/RPM/ITEM_DSYINVST_CAT 
Investment CategoryCHAR50System Generated
/RPM/ITEM_DSYCLUSTER/RPM/TV_EXTIDClusterCHAR24Conditional
/RPM/ITEM_DSYPROD_HIER
Product HierarchyCHAR50Conditional
/RPM/ITEM_DSYEXPO_CO
Export ControlNUMC2Mandatory
STXLZ04
Justification (Export Control)CLUST512Conditional
/RPM/ITEM_DSYNEED_KNOW
Need-to-knowCHAR3Mandatory
/RPM/ITEM_DSYPROJ_OWN
Project OwnerNUMC8Mandatory
/RPM/ITEM_DSYPFIN_CON
Project Financial ControllerNUMC8Mandatory
/RPM/ITEM_DSYSCOR_METH
Scoring MethodologyCHAR15System Generated
/RPM/ITEM_DSYST_RISK_MAG
Starting Risk MagnitudeNUMC2Conditional
/RPM/ITEM_DSYST_RISK_LIK
Starting Risk LikelihoodNUMC2Conditional
/RPM/ITEM_DSYRE_RISK_MAG
Residual Risk MagnitudeNUMC2Conditional
/RPM/ITEM_DSYRE_RISK_LIK
Residual Risk LikelihoodNUMC2Conditional
/RPM/ITEM_DSYRE_MAN_MAG
Regulatory Mandated MagnitudeNUMC2Conditional
/RPM/ITEM_DSYRE_MAN_LIK
Regulatory Mandated LikelihoodNUMC2Conditional
/RPM/ITEM_DSYRE_MAN_TIM
Regulatory Mandated Time Horizon (to start project)NUMC2Conditional
/RPM/ITEM_DSYCAP_DAT
Capitalization DateDATS8Conditional
/RPM/ITEM_DSYPRCTRPRCTRProfit CentreCHAR10Mandatory
/RPM/ITEM_DSYBUDG_PRO/RPM/TV_EXTIDBudget ProvisionCHAR24Conditional
/RPM/ITEM_DSYOPP_ID
Opportunity IDCHAR18Conditional
/RPM/ITEM_DSYARCHETY
ArchetypeNUMC2Conditional
/RPM/ITEM_DSYMUST_JUS
Must Do JustificationNUMC2Mandatory
/RPM/ITEM_DSYLEG_PRJIDPS_PSPIDLegacy Project IDCHAR24Conditional
/RPM/ITEM_DSYWERKSWERKS_DPlantCHAR4Conditional
/RPM/ITEM_DSYIDEAID
Idea IDCHAR7Conditional
/RPM/ITEM_DSY_ERDAT
Created OnDATS8System Generated
/RPM/ITEM_DSYSUBSIDY
SubsidyCHAR1Conditional
STXLZ03CLUSTDSubsidy RelevanceCLUSTD512Conditional
STXLZ01CLUSTDKey AssumptionsCLUSTD512Conditional
STXLZ02CLUSTDVariationsCLUSTD512Conditional
STXLZ05CLUSTDOther InformationCLUSTD512Conditional
STXKZ08CLUSTDLessons LearntCLUSTD512Conditional


Decision Point Table

TableFieldData ElementField DescriptionData TypeLengthRequirement
/RPM/DECISIONDECISION_ID/RPM/TV_EXTIDIDCHAR24Mandatory
/RPM/DECISIONITEM_ID/RPM/TV_EXTIDITEM_IDCHAR24Mandatory
CGPL_TEXTTEXT1
NAMECHAR40Mandatory
/RPM/DECISIONSTATUS/RPM/TV_STATUS_COMMONSTATUSCHAR5Conditional
/RPM/DECISIONPLAN_STARTRPM_TV_PLAN_START
Planned Start Date
DATS8Conditional
/RPM/DECISIONPLAN_FINISHRPM_TV_PLAN_FINISH
Planned Finish Date
DATS8Conditional
/RPM/DECISIONACTUAL_STARTRPM_TV_ACTUAL_STARTActual Start DateDATS8System Generated
/RPM/DECISIONACTUAL_FINISHRPM_TV_ACTUAL_FINISHActual Finish DateDATS8System Generated
/RPM/DECISIONSYVAR_REF
Variation ReferenceCHAR60Conditional


 Item Authorizations (Required only where Need-to-know = yes)

TableFieldData ElementField DescriptionData TypeLengthRequirement
ACO_USERITEM_ID/RPM/TV_EXTIDIDCHAR24Conditional
ACO_USERACTIVITYACO_ACTVTActivityCHAR10Conditional
ACO_USERUSERACO_USER_IDUserCHAR12Conditional

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

IDCriticalityError Message/Report DescriptionRuleOutputSource System


Conversion Process

The high-level process is represented by the diagram below:

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

image-2025-10-13_15-16-37.png



Data Privacy and Sensitivity

Some projects are considered Need to Know and data is to be restricted to named users only.


Extraction

  1. Extract data from a source into Syniti Migrate. There are 2 possibilities:

    1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
      1. Perform full data extraction from relevant tables in the source system(s).
      2. Perform extraction through the application layer.
      3. Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
    2. 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.

Extraction Run Sheet

Req #Requirement DescriptionTeam Responsible
1Extract data from source system based on relevancy ruleSyWay Data Team


Selection Screen


Selection Ref ScreenParameter NameSelection TypeRequirementValue 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

Field NameField DescriptionRule
SNROItem 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


GBULegacy GBU

Tooltip

GBU from Legacy SAP System.
Displayed for Context Only


Internal Control 

Display from Prep report - PROJ-ZZGBU

BULegacy Business Unit

Tooltip

Business Unit from Legacy SAP System.
Displayed for Context Only

Internal Control 

Display from Prep report - PROJ-ZZBU

PARENT_IDParent 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_FAMILYLegacy WBS Family

Tooltip

WBS Family from Legacy System.
Displayed for Context only


Internal Controls

Display from Prep Report - PROJ-ZZFAMILY for PF2 or Calculated from PRPS-ZZ_FAMIL for WP2

ITEM_TYPE_ECCCalculated 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_TYPEItem 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.

The selection of the 

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

TEXT1Name

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

LTEXTItem 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

STATUSItem 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_STARTPlanned 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_FINNISHPlanned 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

IZWEKLegacy 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_DESCLegacy 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_REASONInvestment 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

GEOGRAPHYCompany Code

Tooltip

The Company Code from the Project Definition in Legacy System
This is display only


Internal Controls

Display from PREP Report - PROJ-VBUKR

CurrencyCurrency

Tooltip

he Currency form project definition in Legacy System

This is display only


Internal Controls

Display from PREP Report - PROJ-PWHIE

INITIATIVE_IDINITIATIVE 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_MHIERGBU 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_HIERCorporate 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_GROUPProject 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

SYCLUSTERCluster

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_HIERProduct 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_COExport 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

Z04Justification (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

SYEXPO_CONeed-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_OWNProject 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.

ASTNRLegacy Applicant No

Tooltip

Project Applicant from the Project Definition for Legacy SAP system

Displayed for Context only


Internal Controls

From PREP report - PROJ-ASTNR

ASTNALegacy 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_CONProject 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_MAGStarting 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
0011:B1 Equipment maintenance
0014:B4 Turnarounds
0019:F1 Comm. needs-bus risk rdctn
0022:A1 Health/Safety-best practice
0025:A3 Security - best practices
0028:A5 Compliance- Future regulatn
0032:F3C Climate  / Other
0033:F4A Nature / Water
0034:F4B Nature / Other
0039:R4 Equip. Maintenance/Replcmnt
0040:R5 Facilities/site maintenance
0043:R8 IAM & regulatory


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_LIKStarting 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_MAGResidual 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_LIKResidual 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_MAGRegulatory 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
0023:A1C Health/Safety - Compliance
0024:A2 Environment  - Compliance
0026:A3C Security - Compliance
0035:F5 SoC/SVHC replacement - ASA
0038:R3 HSE
0049:I6 Cybersecurity & Compliance


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_LIKRegulatory 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_TIMRegulatory 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_DATCapitalization Date

Tooltip

Stores the capitalization date for the purpose of "Depreciation forecast".

This date is mandatory for the Capital Projects Item types.  
Z001:Industrial with Qualification
Z002:Industrial w/out Qualification
Z003:Industrial 2 Phases
Z008:IT Full Lifecycle Project
Z009:IT Small Project
Z011:Turnaround Projects

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

SYPRCTRProfit 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_PROBudget 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 Z014 - Budget Provision

SYOPP_IDOpportunity ID

Tooltip

Stores the CRM opportunity ID where applicable.

This is an optional field.

SYARCHETYArchetype

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_JUSMust 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


SYWERKSPlant

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.

SYIDEAIDIdea ID

Tooltip

Field to store the Idea number where this is known.

This is an optional field for migration

SYSUBSIDYSubsidy

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

Z03Subsidy 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.

Z01Key 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

Z02Variations

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

Z05Other 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

Z08Lessons 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_DPCPTActive 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 NameField DescriptionRule
SNROItem Serial Number

This field is display only and is filled with a sequential number when user adds a item record

PARENT_IDParent 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_TYPEType

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.

The selection of the 

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

TEXT1Name

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

LTEXTItem Description

Tooltip

Long Description, this field is used to provide a concise description of the PPM Item. 

Entered where information is available

STATUSItem 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_STARTPlanned 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_FINNISHPlanned 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

CATEGORYInvestment 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

GEOGRAPHYCompany 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_IDINITIATIVE 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_MHIERGBU 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_HIERCorporate 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

SYCLUSTERCluster

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_HIERProduct 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_COExport 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

Z04Justification (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_KNOWNeed-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_OWNProject 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_CONProject 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_MAGStarting 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
0011:B1 Equipment maintenance
0014:B4 Turnarounds
0019:F1 Comm. needs-bus risk rdctn
0022:A1 Health/Safety-best practice
0025:A3 Security - best practices
0028:A5 Compliance- Future regulatn
0032:F3C Climate  / Other
0033:F4A Nature / Water
0034:F4B Nature / Other
0039:R4 Equip. Maintenance/Replcmnt
0040:R5 Facilities/site maintenance
0043:R8 IAM & regulatory


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_LIKStarting 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_MAGResidual 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_LIKResidual 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_MAGRegulatory 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
0023:A1C Health/Safety - Compliance
0024:A2 Environment  - Compliance
0026:A3C Security - Compliance
0035:F5 SoC/SVHC replacement - ASA
0038:R3 HSE
0049:I6 Cybersecurity & Compliance


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_LIKRegulatory 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_TIMRegulatory 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_DATCapitalization Date

Tooltip

Stores the capitalization date for the purpose of "Depreciation forecast".

This date is mandatory for the Capital Projects Item types.  
Z001:Industrial with Qualification
Z002:Industrial w/out Qualification
Z003:Industrial 2 Phases
Z008:IT Full Lifecycle Project
Z009:IT Small Project
Z011:Turnaround Projects

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

SYPRCTRProfit 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_PROBudget 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 Z014 - Budget Provision

SYOPP_IDOpportunity ID

Tooltip

Stores the CRM opportunity ID where applicable.

This is an optional field.

SYARCHETYArchetype

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_JUSMust 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


SYWERKSPlant

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.

SYIDEAIDIdea ID

Tooltip

Field to store the Idea number where this is known.

This is an optional field for migration

SYSUBSIDYSubsidy

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

Z03Subsidy 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.

Z01Key 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

Z02Variations

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

Z05Other 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

Z08Lessons 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_DPCPTActive 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 NameField DescriptionRule
SNROItem Serial Number

Unique Identifier Item serial numbers

It is a dropdown of the Item numbers maintained in the main DCT

DECISION_IDDecision 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

NAMEDecision Point Description

Name of the decision point, part of the customisation and can't be changed.

This is a display only field

PLAN_STARTDecision Point Planned Start DateThis field stores the plan start date of a decision point for the items where there is SG tracking required
PLAN_FINISHDecision Point Planned End DateThis field stores the plan finish date of a decision point where SG tacking is required
ACTUAL_STARTDecision Point Actual Start DateThis field stores the actual start date of a decision point derived from the initiation date of respective stage gate approval.
ACTUAL_FINISHDecision Point Actual End DateThis field stores the actual finish date of a decision point derived from the approved date of respective stage gate approval.
SYVAR_REFVariation ReferenceThis field stores the identifier and short description of Variation required to variation budget approval


Authorization - For "Need-to-know" projects, named users will be added manually.

Field NameField DescriptionRule
SNROItem 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_IDSAP 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

List the steps that need to occur before extraction can commence

Item #Step DescriptionTeam 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:

  1. Perform value mapping and data transformation rules.
    1. Legacy values are mapped to the to-be values (this could include a default value)
    2. Values are transformed according to the rules defined in Syniti Migrate
  2. 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 DescriptionTeam 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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCT
PARENT_IDParent Bucket IDS/4 Hana/RPM/ITEM_DPARENT_IDParent Bucket IDManually copy from Non ECC source
2



S/4 Hana/RPM/ITEM_DPORTFOLIO_IDPortfolio ID

Global Default "SYENSQO"

3WP2


S/4 Hana/RPM/ITEM_DITEM_TYPEType

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


4PF2PROJ

S/4 Hana/RPM/ITEM_DITEM_TYPEType

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

5DCT
ITEM_TYPETypeS/4 Hana/RPM/ITEM_DITEM_TYPETypeManually copy from Non ECC source
6WP2/PF2PROJPOST1Project DescriptionS/4 HanaCGPL_TEXTTEXT1Name

Copy source to target

7DCT
TEXT1NameS/4 HanaCGPL_TEXTTEXT1NameManually copy from Non ECC source
8WP2/PF2STXLLTEXTLong DescriptionS/4 HanaSTXLLTEXTDescriptionCopy source to target
9DCT
LTEXTItem DescriptionS/4 HanaSTXLLTEXTDescriptionManually copy from Non ECC source
10DCT
STATUSItem StatusS/4 Hana/RPM/ITEM_DSTATUSItem StatusManually copy from Non ECC source
11WP2/PF2PROJPLFAZProject planned start dateS/4 Hana/RPM/ITEM_DPLANNED_STARTPlanned StartCopy from source, format YYYYMMDD
12DCT
PLANNED_STARTPlanned StartS/4 Hana/RPM/ITEM_DPLANNED_STARTPlanned StartManually copy from Non ECC source
13WP2/PF2PROJPLSEZProject planned finish dateS/4 Hana/RPM/ITEM_DPLANNED_FINISHPlanned Finish

Copy from source, format YYYYMMDD

14DCT
PLANNED_FINISHPlanned FinishS/4 Hana/RPM/ITEM_DPLANNED_FINISHPlanned FinishManually copy from Non ECC source
15

DCT


SYINVST_REASONInvestment ReasonS/4 Hana/RPM/ITEM_DSYINVST_REASONInvestment Reason Manually copy from Non ECC source
16



S/4 Hana/RPM/ITEM_DSYSUB_BUS_DRISub Business Driver

Value Mapping: Investment Reason

Based on the SYINVST_REASON field

17



S/4 Hana/RPM/ITEM_DSYMAIN_BUS_DRIMain Business Driver

Value Mapping: Investment Reason

Based on theSYINVST_REASON field

18



S/4 Hana/RPM/ITEM_DSYINVST_CAT Investment Category

Value Mapping: Investment Reason

Based on theSYINVST_REASON field

19WP2/PF2PROJVBUKRCompany codeS/4 Hana/RPM/ITEM_DGEOGRAPHY
Company CodeValue Mapping: Old to New Company Code
20DCT
GEOGRAPHYCompany codeS/4 Hana/RPM/ITEM_DGEOGRAPHYCompany CodeManually copy from Non ECC source
21WP2/PF2PROJPWHIEWBS currencyS/4 Hana/RPM/ITEM_DCURRENCYCURRENCY

Copy from Source

22DCT
CurrencyCurrencyS/4 Hana/RPM/ITEM_DCURRENCYCURRENCY

If Legacy Project ID field is empty then

Value Mapping: Currency From Company Code
Company Code Currency from T001-WAERS where BUKRS = Target Geography

23



S/4 Hana/RPM/ITEM_DUNITUnitDefault to "TAG"(Day)
24



S/4 Hana/RPM/ITEM_DCAP_PERIODTYPECapacity Period BreakdownDefault to "12"(Annually)
25



S/4 Hana/RPM/ITEM_DPERIODTYPEFin Period BreakdownDefault to "12"(Annually)
26DCT
INITIATIVE_IDINITIATIVE IDS/4 Hana/RPM/ITEM_DINITIATIVE_IDINITIATIVE IDManually copy from Non ECC source
28DCT
SYGBU_MHIERGBU Market HierarchyS/4 Hana/RPM/ITEM_DSYGBU_MHIERGBU Market HierarchyManually copy from Non ECC source
30DCT
SYCORP_HIERCorporate HierarchyS/4 Hana/RPM/ITEM_DSYCORP_HIERCorporate HierarchyManually copy from Non ECC source
31DCT
SYCLUSTERClusterS/4 Hana/RPM/ITEM_DSYCLUSTERClusterManually copy from Non ECC source
32DCT
SYPROD_HIERProduct HierarchyS/4 Hana/RPM/ITEM_DSYPROD_HIERProduct HierarchyManually copy from Non ECC source
33DCT
SYEXPO_COExport controlS/4 Hana/RPM/ITEM_DSYEXPO_COExport ControlManually copy from Non ECC source
34DCT
JustificationJustification (Export Control)S/4 HanaSTXLZ04Justification (Export Control)Manually copy from Non ECC source
35DCT
SYNEED_KNOWNeed-to-knowS/4 Hana/RPM/ITEM_DSYNEED_KNOWNeed-to-knowManually copy from Non ECC source
36WP2/PF2PROJZZ_POSITPosition of the person responsibleS/4 Hana/RPM/ITEM_DSYPROJ_OWNProject OwnerValue Mapping: Old Position ID  to New Position ID
37DCT
SYPROJ_OWNProject OwnerS/4 Hana/RPM/ITEM_DSYPROJ_OWNProject OwnerManually copy from Non ECC source
39DCT
SYPFIN_CONProject Financial Controller Position IDS/4 Hana/RPM/ITEM_DSYPFIN_CONProject Financial Controller Position IDManually copy from Non ECC source
41



S/4 Hana/RPM/ITEM_DSYSCOR_METHScoring Methodology

Value Mapping: Investment Reason

Based on the SYINVST_REASON field

42DCT
SYST_RISK_MAGStarting risk MagnitudeS/4 Hana/RPM/ITEM_DSYST_RISK_MAGStarting risk MagnitudeManually copy from Non ECC source
43DCT
SYST_RISK_LIKStarting risk LikelihoodS/4 Hana/RPM/ITEM_DSYST_RISK_LIKStarting risk LikelihoodManually copy from Non ECC source
44DCT
SYRE_RISK_MAGResidual risk MagnitudeS/4 Hana/RPM/ITEM_DSYRE_RISK_MAGResidual risk MagnitudeManually copy from Non ECC source
45DCT
SYRE_RISK_LIKResidual risk LikelihoodS/4 Hana/RPM/ITEM_DSYRE_RISK_LIKResidual risk LikelihoodManually copy from Non ECC source
46DCT
SYRE_MAN_MAGRegulatory Mandated MagnitudeS/4 Hana/RPM/ITEM_DSYRE_MAN_MAGRegulatory Mandated MagnitudeManually copy from Non ECC source
47DCT
SYRE_MAN_LIKRegulatory Mandated LikelihoodS/4 Hana/RPM/ITEM_DSYRE_MAN_LIKRegulatory Mandated LikelihoodManually copy from Non ECC source
48DCT
SYRE_MAN_TIMRegulatory Mandated Time Horizon (to start project)S/4 Hana/RPM/ITEM_DSYRE_MAN_TIMRegulatory Mandated Time Horizon (to start project)Manually copy from Non ECC source
49DCT
SYCAP_DATCapitalization DateS/4 Hana/RPM/ITEM_DSYCAP_DATCapitalization DateManually copy from Non ECC source
50WP2/PF2PROJPRCTRProfit CenterS/4 Hana/RPM/ITEM_DSYPRCTRProfit CentreValue Mapping:  Profit Center Old to New
51DCT
SYPRCTRProfit CentreS/4 Hana/RPM/ITEM_DSYPRCTRProfit CentreManually copy from Non ECC source
54DCT
SYBUDG_PROBudget ProvisionS/4 Hana/RPM/ITEM_DSYBUDG_PROBudget ProvisionManually copy from Non ECC source
55DCT
SYOPP_IDOpportunity IDS/4 Hana/RPM/ITEM_DSYOPP_IDOpportunity IDManually copy from Non ECC source
56DCT
SYARCHETYArchetypeS/4 Hana/RPM/ITEM_DSYARCHETYArchetypeManually copy from Non ECC source
57DCT
SYMUST_JUSMust Do JustificationS/4 Hana/RPM/ITEM_DSYMUST_JUSMust Do JustificationManually copy from Non ECC source
58WP2/PF2PROJPSPIDIDS/4 Hana/RPM/ITEM_DSYLEG_PRJIDLegacy 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
SNROSerial NumberS/4 Hana/RPM/ITEM_DSYLEG_PRJIDLegacy 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
59WP2/PF2PROJWERKSPlant S/4 Hana/RPM/ITEM_DSYWERKSPlantValue Mapping: Old Plant to New
60DCT
SYWERKSPlantS/4 Hana/RPM/ITEM_DSYWERKSPlantManually copy from Non ECC source
61DCT
SYIDEAIDIdea IDS/4 Hana/RPM/ITEM_DSYIDEAIDIdea IDManually copy from Non ECC source
62DCT
SYSUBSIDYSubsidyS/4 Hana/RPM/ITEM_DSYSUBSIDYSubsidyManually copy from Non ECC source
63DCT
Sub_RelevanceSubsidy RelevanceS/4 HanaSTXLZ03Subsidy RelevanceManually copy from Non ECC source
64DCT
Key_AssumpKey AssumptionsS/4 HanaSTXLZ01Key AssumptionsManually copy from Non ECC source
65DCT
VariationsVariationsS/4 HanaSTXLZ02VariationsManually copy from Non ECC source
66DCT
OtherOther InformationS/4 HanaSTXLZ05Other InformationManually copy from Non ECC source

DCT
LessonsLessons LearntS/4 HanaSTXLZ08Lessons LearntManually 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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
66



S/4 HanaUpload program CREATE_CPROJECTCreate ProjectIf 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
67S/4


S/4 HanaUpload program CPRO_TEMPLATEProject Template to be used

If CREATE_CPROJECT is active then field must be set.

Select PS_TEMPLATE from  /RPM/PSPTIT_MAP using ITEM_TYPE

68S/4


S/4 HanaUpload program PS_LOGSYSTEMLogical 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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1



S/4 Hana/RPM/DECISION ITEMItem ID
2



S/4 Hana/RPM/DECISIONDECISION_IDDecision Point ID

The List of decision points for each item is based on the item type as per 

3



S/4 Hana/RPM/DECISIONNAMEDecision Point Name

Decision Point Name from RPM/PHASE_T using ITEM_TYPE and DECISION_ID

4



S/4 Hana/RPM/DECISIONSTATUSDecision 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 

5DCTDecision PointPLAN_STARTDecision Point Planned Start DateS/4 Hana/RPM/DECISIONPLAN_STARTDecision Point Planned Start Date

Manually copy from Non ECC source

6DCTDecision PointPLAN_FINISHDecision Point Planned End DateS/4 Hana/RPM/DECISIONPLAN_FINISHDecision Point Planned End Date

Manually copy from Non ECC source

7DCTDecision PointACTUAL_STARTDecision Point Actual Start DateS/4 Hana/RPM/DECISIONACTUAL_STARTDecision Point Actual Start Date

Manually copy from Non ECC source

8DCTDecision PointACTUAL_FINISHDecision Point Actual End DateS/4 Hana/RPM/DECISIONACTUAL_FINISHDecision Point Actual End Date

Manually copy from Non ECC source

9DCTDecision PointSYVAR_REFVariation ReferenceS/4 Hana/RPM/DECISIONSYVAR_REFVariation Reference

Manually copy from Non ECC source

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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTAuthorizationSNROItem Serial NumberS/4 HanaACO_USERITEM_IDObject IDManually copy from Non ECC source
2



S/4 HanaACO_USERACTIVITYActivity

Default to activity "READ"

3DCTAuthorizationUSER_IDSAP User NameS/4 HanaACO_USERUSERUser ID

Manually copy from Non ECC source

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above
Mapping Table NameMapping Table Description
Company CodeValue Mapping: Old to New Company Code
T001Value Mapping: Currency From Company Code
HRP1000

Value Mapping: Position Name from Position

Value Mapping: Old Position ID  to New Position ID

PlantValue Mapping: Old Plant to New
Profit CenterValue 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 DescriptionTeam Responsible

1

Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool.

Data Team 


Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

TaskAction
Verify Record CountSyWay 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

TaskAction

Conversion Accuracy

SyWay I2M Data Team to verify that all fields below meet pass the checks:

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
  4. Text Length Checks

Review Error Reports

Review and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source (DCT) data.


Business

The following pre-load validations will be performed by the business.

Completeness

TaskAction

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

TaskAction

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:

  1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
  2. 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 DescriptionTeam Responsible
1Load using transaction RPM_DX_ITEMSyWay Data Team
2Load 3 records for < > to validate if data is loaded successfully without errorsSyWay Data Team
3Load 3 records for < > to validate if data is loaded successfully without errorsSyWay Data Team
4Proceed with full load if steps 2 and 3 are validatedSyWay Data Team
5Validate few records loaded by accessing Portfolio Item AppSyWay Data Team
6Validate few records loaded by accessing PS Project AppSyWay 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

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

Key Configuration requirement

Item #Configuration Item
1Override Default Global Settings  (Master Switches  0002   Switched off - Item will have manual ID)
2Define Currency Units
3Item Types
4Item Type Status
5Configure Fields for Mass Import
6Category
7Sub-Category
8Technology Type
9Group
10Area
11Object Link
12Plant
13DFM Object Links
14Map Item Types to PS Project

Conversion Objects

Object #Preceding Object Conversion Approach
1113Portfolio Bucket Hierarchy

1073

Profit Centre

1019

Template Projects

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error TypeError DescriptionAction Taken

Invalid Data

Invalid Portfolio

Validate DCT content

Invalid Data

Invalid Bucket ID (Parent ID does not exist)

Validate DCT content

Invalid DataInvalid Item TypeValidate Transformation rules and DCT values
Invalid DataInvalid datesValidate format of the date fields.
Invalid DataMore that one Item per GBU/Company Code/Plant for Capital Lease Item TypeRemove Duplicate values from DCT
Invalid DataMore that one Item per GBU/Company Code/Plant for Direct Asset Purchase Item TypeRemove Duplicate values from DCT
Invalid DataMore that one Item per GBU/Company Code/Plant for Capital Spares Item TypeRemove Duplicate values from DCT


Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

TaskAction

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

TaskAction

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

The following post-load validations will be performed by the business.

Completeness

TaskAction
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

TaskAction
Verify AccuracyExtract 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.

Any additional key assumptions.


See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log