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.

  • 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-IZWEK

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-IZWEK
  • 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-IZWEK
  • 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.

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_IDTypeCHAR15Mandatory
CGPL_TEXTTEXT1CGPL_TEXT1NameCHAR40Mandatory
STXLCLUSTD (LTEXT for identification in Transformation))CLUSTDItem DescriptionCLUSTD
Conditional
/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_DCATEGORYRPM_PROJECT_CATEGORYInvestment ReasonNUMC4Mandatory
/RPM/ITEM_DSUBCATEGORYRPM_PROJ_SUBCATEGORYSub Business DriverNUMC4Mandatory
/RPM/ITEM_DTTYPE

RPM_PROJECTTYPE

Main Business DriverNUMC4Mandatory
/RPM/ITEM_DPTYPERPM_PROJECT_TECHTYPEInvestment CategoryNUMC4Mandatory
/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_DZXX2
Spending RangeNUMC2Mandatory
/RPM/ITEM_DZXX3
GBU Market HierarchyNUMC2Conditional
/RPM/ITEM_DZXX4
End User MarketNUMC2Conditional
/RPM/ITEM_DZXX5
Corporate HierarchyNUMC2Conditional
/RPM/ITEM_DZXX6
ClusterNUMC2Conditional
/RPM/ITEM_DZXX7
Product HierarchyCHAR40Conditional
/RPM/ITEM_DZXX10
Export ControlNUMC2Mandatory
STXLCLUSTD (Justification for identification in Transformation)
Justification (Export Control)CLUST
Conditional
/RPM/ITEM_DZXX11
Need-to-knowCHAR1Mandatory
/RPM/ITEM_DZXX14HROBJIDProject OwnerNUMC8Mandatory
/RPM/ITEM_DZXX15STEXTProject OwnerSTEXT40Mandatory
/RPM/ITEM_DZXX16HROBJIDProject Financial ControllerNUMC8Mandatory
/RPM/ITEM_DZXX17STEXTProject Financial ControllerSTEXT40Mandatory
/RPM/ITEM_DZXX37
Scoring Methodology

System Generated
/RPM/ITEM_DZXX18
Starting Risk MagnitudeNUMC2Conditional
/RPM/ITEM_DZXX19
Starting Risk LikelihoodNUMC2Conditional
/RPM/ITEM_DZXX20
Residual Risk MagnitudeNUMC2Conditional
/RPM/ITEM_DZXX21
Residual Risk LikelihoodNUMC2Conditional
/RPM/ITEM_DZXX22
Regulatory Mandated MagnitudeNUMC2Conditional
/RPM/ITEM_DZXX23
Regulatory Mandated LikelihoodNUMC2Conditional
/RPM/ITEM_DZXX24
Regulatory Mandated Time Horizon (to start project)NUMC2Conditional
/RPM/ITEM_DZXX25
Capitalization DateDATS8Conditional
/RPM/ITEM_DZXX26PRCTRProfit CentreCHAR10Mandatory
/RPM/ITEM_DZXX27
WeGo IDCHAR10Conditional
/RPM/ITEM_DZXX29
Budget ProvisionCHAR10Conditional
/RPM/ITEM_DZXX30
Opportunity IDCHAR40Conditional
/RPM/ITEM_DZXX31
ArchetypeNUMC2Conditional
/RPM/ITEM_DZXX32
Must Do JustificationNUMC2Mandatory
/RPM/ITEM_DZXX33PS_PSPIDLegacy Project IDCHAR24Conditional
/RPM/ITEM_DZXX34WERKS_DPlantCHAR4Mandatory
/RPM/ITEM_DZXX35
Idea IDCHAR40Conditional
/RPM/ITEM_DZXX36
SubsidyCHAR1Conditional
STXLCLUSTD (Sub_Relevance for identification in Transformation)CLUSTDSubsidy RelevanceCLUSTD
Conditional
STXLCLUSTD (Key_Assump for identification in Transformation)CLUSTDKey AssumptionsCLUSTD
Conditional
STXLCLUSTD (Variation for identification in Transformation))CLUSTDVariationsCLUSTD
Conditional
STXLCLUSTD (Other for identification in Transformation))CLUSTDOther InformationCLUSTD
Conditional


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/DECISIONZXXX01
Variation Reference

Conditional


 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:

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.

Portfolio Item 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

Unique Identifier for the Item's parent Bucket. In SyWay it is the ID of the L3 bucket where item is assigned.

Dropdown list from the Buckets maintained in CNV_1113 Portfolio Bucket Hierarchy

It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

ITEM_TYPEType

Item types define the structure and behavior of the portfolio item. In Syway item types will be based on the function and number of phases of the project.

Refer configuration table field /RPM/ITEM_TYPE- ITEM_TYPE for allowed values.

It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

TEXT1Name

Short description of the PPM Item


It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

LTEXTItem Description

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

Entered where information is available

STATUSItem Status

Represents status of an item

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

Baseline start date of the item/ project used for planning within the portfolio/ bucket.

It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

PLANNED_FINNISHPlanned Finish

Expected Delivery Date. Baseline finish date of the item/ project used for planning within the portfolio/ bucket.

It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

CATEGORYInvestment Reason

In Syway, Investment Reason is level-3 category of investment.

Refer configuration table field RPM_PROJ_CAT- CATEGORY 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

GEOGRAPHYCompany Code

In SyWay, this field Represents Company code; the legal entity in which the Syway Project will be executed.

Refer configuration table field V_DPR_AREA- AREA for the allowed values.

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

Internal ID of Initiative where Item must be linked to Initiative

Dropdown list from the Initiatives maintained in CNV_1023 Portfolio Initiatives

This is an optional field

ZXX2Spending Range

The Capex spending range used for reporting the project size.

Dropdown values from /SYQ/T_SPND_RNGE

It is a Required Field: Preload Check to be done to confirm that this field is in filled the Data Collection Template

ZXX3GBU Market Hierarchy

GBU Market Hierarchy is a GBU-led Market segmentation, applied to both customer and product combination.

To be selected only for applicable PPM Items.

Dropdown values from  /SYQ/T_BU_DMN

Preload Check to be done to confirm that this field is filled the Data Collection Template when required

ZXX4End User Market

Node of GBU Market Hierarchy used for reporting

To be selected only for applicable PPM Items

Dropdown values from  /SYQ/T_END_USR_MKT

Preload Check to be done to confirm that this field is filled the Data Collection Template when required

ZXX5Corporate Hierarchy

Corporate-led Market segmentation used for reporting

To be selected only for applicable PPM Items.

Preload Check to be done to confirm that this field is filled the Data Collection Template when required

ZXX6Cluster

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.

ZXX7Product Hierarchy

Reference to the product hierarchy node ( at any level) required for reporting.  

It is a required field when Item Type is related to either IS or R&I project.  

Refer table HRRP_NODE- NODEVALUE where HRRP_NODE- NODETYPE = N and HRYTYPE = MD01"

Preload Check to be done to confirm that this field is filled in the Data Collection Template when required.

ZXX10Export Control

To identify if the project is applicable for regulatory governance.

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

JustificationJustification (Export Control)

This field captures the justification for the relevance of export control (long text field), not required  if "Non Determined" option is selected.

This is required field except if "Non Determined": Preload Check to be done to confirm that this field is filled in the Data Collection Template

ZXX11Need-to-know

This field indicates confidential projects. Access will be restricted if selection is "Yes"

Options are Yes/No

It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

ZXX14Project Owner

This field stores Position of the Project Owner for the PPM Item and is mandatory for all SyWay business functions. 

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.

ZXX16Project Financial Controller

This field represent Position of the Project Financial Controller for a project and is mandatory for all SyWay business functions.

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

ZXX18Starting Risk Magnitude

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  

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.

ZXX19Starting Risk Likelihood

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

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

ZXX20Residual Risk Magnitude

For the Risk managed ongoing approved project - this field defines remaining risk magnitude. 

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

ZXX21Residual Risk Likelihood

For the Risk managed ongoing approved project - this field defines remaining risk likelihood.

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

ZXX22Regulatory Mandated Magnitude

Impact of regulatory compliance on project delivery.

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

ZXX23Regulatory Mandated Likelihood

Probability of impact due to regulatory compliance.

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

ZXX24Regulatory Mandated Time Horizon (to start project)

Regulatory defined deadline by which a project must commence.

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

ZXX25Capitalization Date

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

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

ZXX26Profit Center

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.

Refer master table field CEPC-PRCTR for Profit center list. the Data Collection Template,  

It is a Required Field: 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

ZXX27WeGo ID

This stores the WEGO project ID for reporting for R&I related projects in WEGO.

This is an optional field for migration

ZXX29Budget Provision

Used to group those PPM Items where the budget is drawn from the Budget provision Item.

Selection of existing Item Serial Numbers where the item type is Budget Provision

Field content to be verified in Preload check, field can contain only Item numbers of item type Budget Provision.

ZXX30Opportunity ID

If IS or R&I PPM item is created with reference to a CRM Opportunity, the corresponding Opportunity ID will be entered.

This is an optional field.

ZXX31Archetype

This field represent Archetype of the R&I PPM item.

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.

ZXX32Must Do Justification

This field provides input to the ranking of items in the prioritization dashboard. and is relevant across all PPM item types.


ZXX33Legacy Project ID

Legacy Project ID refers to the project identifier used in the previous SAP system before migration to the current S/4 HANA platform. It will be mandatory for the cutover projects only.

Preload Check to be done to confirm that this field is filled in the Data Collection Template when required.

ZXX34Plant

Plant represent a site of the PPM Item. Mandatory for all PPM Items.

It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

ZXX35Idea ID

Field to store the Idea number where this is known.

This is an optional field for migration

ZXX36Subsidy

Use this checkbox if the project is eligible for government or institutional subsidies.

This is an optional field for migration

Sub_RelevanceSubsidy Relevance

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.

Preload Check to be done to confirm that this field is filled in the Data Collection Template when required.

Key_AssumpKey Assumptions

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

VariationsVariations

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

OtherOther Information

This field is used to provide additional details about project.  (This is a long text field)

This is an optional field for migration

ACT_DPCPTActive Decision Point

Indicates the currently active Decision Point (Stage Gate) for the item.

To be selected if item is not initial phase

Drop down field from /RPM/ITEM_PHASE based on selected ITEM_TYPE

InstanceInstance

Instance where the item is to be loaded.


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 customization 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.
ZXXX01Variation 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

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-ZINV = B4 Then Z011


IF PROJ-ZINV = B1, H1, or H2 Then Z013


IF PROJ-PSPID 4&5 Character of Project ID is /J: Then Z001


If PROJ-PSPID 4&5 Character of Project ID is /M: then Z002


f PROJ-PSPID 4&5 Character of Project ID is /C: then Z003


If no WBS elements is Capital, PRPS-IMPRF="" then Item type PRPS-Z010


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-ZINV = B4 Then Z011

IF PROJ-ZINV = B1, B5, H1, or H2 Then Z013

IF PROJ-PSPID 4&5 Character of Project ID is /J: Then Z001

If PROJ-PSPID 4&5 Character of Project ID is /M: then Z002

f PROJ-PSPID 4&5 Character of Project ID is /C: then Z003


If no WBS elements is Capital, PRPS-IMPRF="" then Item type PRPS-Z010

5DCT
ITEM_TYPETypeS/4 Hana/RPM/ITEM_DITEM_TYPETypeManually copy from Non ECC source
6WP2/PF2PROJTEXT1Project 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
15DCT
CATEGORYInvestment ReasonS/4 Hana/RPM/ITEM_DCATEGORYInvestment Reason Manually copy from Non ECC source
16



S/4 Hana/RPM/ITEM_DSUBCATEGORYSub Business Driver

Value Mapping: Investment Reason

Based on the Category field

17



S/4 Hana/RPM/ITEM_DTTYPEMain Business Driver

Value Mapping: Investment Reason

Based on the Category field

18



S/4 Hana/RPM/ITEM_DPTYPEInvestment Category

Value Mapping: Investment Reason

Based on the Category 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
27DCT
ZXX2Spending RangeS/4 Hana/RPM/ITEM_DZXX2Spending RangeManually copy from Non ECC source
28DCT
ZXX3GBU Market HierarchyS/4 Hana/RPM/ITEM_DZXX3GBU Market HierarchyManually copy from Non ECC source
29DCT
ZXX4End User marketS/4 Hana/RPM/ITEM_DZXX4End User MarketManually copy from Non ECC source
30DCT
ZXX5Corporate HierarchyS/4 Hana/RPM/ITEM_DZXX5Corporate HierarchyManually copy from Non ECC source
31DCT
ZXX6ClusterS/4 Hana/RPM/ITEM_DZXX6ClusterManually copy from Non ECC source
32DCT
ZXX7Product HierarchyS/4 Hana/RPM/ITEM_DZXX7Product HierarchyManually copy from Non ECC source
33DCT
ZXX10Export controlS/4 Hana/RPM/ITEM_DZXX10Export ControlManually copy from Non ECC source
34DCT
JustificationJustification (Export Control)S/4 HanaSTXLJustificationJustification (Export Control)Manually copy from Non ECC source
35DCT
ZXX11Need-to-knowS/4 Hana/RPM/ITEM_DZXX11Need-to-knowManually copy from Non ECC source
36WP2/PF2PROJZZ_POSITPosition of the person responsibleS/4 Hana/RPM/ITEM_DZXX14Project OwnerValue Mapping: Old Position ID  to New Position ID
37DCT
ZXX14Project OwnerS/4 Hana/RPM/ITEM_DZXX14Project OwnerManually copy from Non ECC source
38



S/4 Hana/RPM/ITEM_DZXX15Project OwnerValue Mapping: Position Name from Position
Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001
39DCT
ZXX16Project Financial Controller Position IDS/4 Hana/RPM/ITEM_DZXX16Project Financial Controller Position IDManually copy from Non ECC source
40



S/4 Hana/RPM/ITEM_DZXX17Project Financial Controller Position NameValue Mapping: Position Name from Position
Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001
41



S/4 Hana/RPM/ITEM_DZXX37Scoring Methodology

Value Mapping: Investment Reason

Based on the Category field

42DCT
ZXX18Starting risk MagnitudeS/4 Hana/RPM/ITEM_DZXX18Starting risk MagnitudeManually copy from Non ECC source
43DCT
ZXX19Starting risk LikelihoodS/4 Hana/RPM/ITEM_DZXX19Starting risk LikelihoodManually copy from Non ECC source
44DCT
ZXX20Residual risk MagnitudeS/4 Hana/RPM/ITEM_DZXX20Residual risk MagnitudeManually copy from Non ECC source
45DCT
ZXX21Residual risk LikelihoodS/4 Hana/RPM/ITEM_DZXX21Residual risk LikelihoodManually copy from Non ECC source
46DCT
ZXX22Regulatory Mandated MagnitudeS/4 Hana/RPM/ITEM_DZXX22Regulatory Mandated MagnitudeManually copy from Non ECC source
47DCT
ZXX23Regulatory Mandated LikelihoodS/4 Hana/RPM/ITEM_DZXX23Regulatory Mandated LikelihoodManually copy from Non ECC source
48DCT
ZXX24Regulatory Mandated Time Horizon (to start project)S/4 Hana/RPM/ITEM_DZXX24Regulatory Mandated Time Horizon (to start project)Manually copy from Non ECC source
49DCT
ZXX25Capitalization DateS/4 Hana/RPM/ITEM_DZXX25Capitalization DateManually copy from Non ECC source
50WP2/PF2PROJPRCTRProfit CenterS/4 Hana/RPM/ITEM_DZXX26Profit CentreValue Mapping:  Profit Center Old to New
51DCT
ZXX26Profit CentreS/4 Hana/RPM/ITEM_DZXX26Profit CentreManually copy from Non ECC source
52WP2/PF2PRPSZZ_WEGO_IDWEGO IDS/4 Hana/RPM/ITEM_DZXX27Wego IDIf all WBS Elements for the PSPID record has the same WEGO Number only.
53DCT
ZXX27WeGo IDS/4 Hana/RPM/ITEM_DZXX27WeGo IDManually copy from Non ECC source
54DCT
ZXX29Budget ProvisionS/4 Hana/RPM/ITEM_DZXX29Budget ProvisionManually copy from Non ECC source
55DCT
ZXX30Opportunity IDS/4 Hana/RPM/ITEM_DZXX30Opportunity IDManually copy from Non ECC source
56DCT
ZXX31ArchetypeS/4 Hana/RPM/ITEM_DZXX31ArchetypeManually copy from Non ECC source
57DCT
ZXX32Must Do JustificationS/4 Hana/RPM/ITEM_DZXX32Must Do JustificationManually copy from Non ECC source
58WP2/PF2PROJPSPIDIDS/4 Hana/RPM/ITEM_DZXX33Legacy 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
59WP2/PF2PROJWERKSPlant S/4 Hana/RPM/ITEM_DZXX34PlantValue Mapping: Old Plant to New
60DCT
ZXX34PlantS/4 Hana/RPM/ITEM_DZXX34PlantManually copy from Non ECC source
61DCT
ZXX35Idea IDS/4 Hana/RPM/ITEM_DZXX35Idea IDManually copy from Non ECC source
62DCT
ZXX36SubsidyS/4 Hana/RPM/ITEM_DZXX36SubsidyManually copy from Non ECC source
63DCT
Sub_RelevanceSubsidy RelevanceS/4 HanaSTXLSub_RelevanceSubsidy RelevanceManually copy from Non ECC source
64DCT
Key_AssumpKey AssumptionsS/4 HanaSTXLKey_AssumpKey AssumptionsManually copy from Non ECC source
65DCT
VariationsVariationsS/4 HanaSTXLVariationsVariationsManually copy from Non ECC source
66DCT
OtherOther InformationS/4 HanaSTXLOtherOther InformationManually 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 PointZXXX01Variation ReferenceS/4 Hana/RPM/DECISIONZXXX01Variation 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

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

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

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

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

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

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 using transaction CN41n

Conversion Accuracy

Verify that the WBS Structure  in target were created correctly as per project template using transaction CN41n


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.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 97) Mar 26, 2026 08:08 KOHN-ext, Jacob
v. 109 Mar 26, 2026 07:42 KOHN-ext, Jacob
v. 108 Mar 26, 2026 07:35 KOHN-ext, Jacob
v. 107 Mar 16, 2026 11:09 KOHN-ext, Jacob
v. 106 Mar 12, 2026 09:06 KOHN-ext, Jacob
v. 105 Mar 12, 2026 08:42 KOHN-ext, Jacob
v. 104 Mar 05, 2026 14:57 KOHN-ext, Jacob
v. 103 Mar 05, 2026 14:00 KOHN-ext, Jacob
v. 102 Mar 05, 2026 12:11 KOHN-ext, Jacob
v. 101 Mar 04, 2026 15:55 KOHN-ext, Jacob

Go to Page History