You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

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 Item is created under the 3rd level bucket (functions) under GBU 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 templates will be prepopulated with relevant information from Capital and Budget Managed Operating PS Project Definitions in scope for migration but while these systems serve as sources, extensive construction will be necessary to produce properly formatted data load sheets for S/4 HANA. 


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 last 3 years or has AUC balance.
    2. Budgeted Operating projects (e.g. Budgeted Maintenance, Marketing, Demolition projects) open as at migration date with postings in the last 3 years.
    3. Closed Capital Projects with postings within the agreed timeframe. (currently migration relevant is 2028)
    4. Closed Budgeted Operating projects with postings within the  agreed timeframe. (currently migration relevant is 2028)
    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 in the last 3 years

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

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

  

List of source systems and approximate number of records 

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2Relevant Open PS Projects
S/4 HanaTBD
WP2Relevant Open PS Projects
S/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.

The PS Project definition with WBS element hierarchy (Level 1 & 2)  is automatically created from the approved PPM item once stage-gate 1 is approved., the PS project structure is based on the configuration of PPM item type to a PS template project (created as per CVN-1019 Template Projects) with the Decision Flow Management settings in the SAP system.  As per CNV-1019 Template Project - SyWay Project - Syensqo - Wiki knowledge base.   Program will be required to perform mass status change.


Relevancy Logic: 

Table PROJ

Field "Company Code" in scope.

Field project profile not excluded.

Result: Object numbers of Project that are in company codes in scope.

Table JEST:

Field "Object number" = Key in the object numbers of Project 

Field "Status Inactive" = blank, Then filter object number that has status I0046 (Closed). (for postings in the agreed timeframe)

Result closed projects.

Table PRPS

Field PSPHI For closed projects numbers, Result WBS numbers for 

Table RPSCO / COSP:

Field "Object number" = Key in the object numbers of WBS

Field "Fiscal Year" = the agreed timeframe, (currently migration relevant is 2028)

Result = Object numbers that have cost in current year.

These WBS needs to be migrated.

Table BPGE

Using object number from PRPS (both open and closed)

If any WBS object has a record then project is seen to have a budget and is included

Additional Information

Multi-language Requirement

All item names and texts will be maintained in a single language as entered, with no requirement for translation.

Document Management

Not applicable

Legal Requirement

Not applicable

Special Requirements

Not applicable

Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
/RPM/ITEM_DEXTERNAL_ID/RPM/TV_EXTIDIDCHAR24System Generated
/RPM/ITEM_DPARENT_ID/RPM/TV_EXTIDParent Bucket IDCHAR24Mandatory
/RPM/ITEM_DPARENT_GUID
Bucket GUID

System Generated
/RPM/ITEM_DPORTFOLIO_GUID



System Generated
/RPM/ITEM_DPORTFOLIO_ID/RPM/TV_EXTIDPortfolio IDCHAR24Mandatory
/RPM/ITEM_DITEM_TYPE/RPM/TV_ITEM_IDTypeCHAR15Mandatory
CGPL_TEXTTEXT1CGPL_TEXT1NameCHAR40Mandatory
STXLLTEXTCLUSTDItem 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_DFORECAST_STARTRPM_TV_FORECAST_STARTForecasted StartDATS8Conditional
/RPM/ITEM_DFORECAST_FINISHRPM_TV_FORECAST_FINISHForecasted FinishDATS8Conditional
/RPM/ITEM_DCATEGORYRPM_PROJECT_CATEGORYCategoryNUMC4Mandatory
/RPM/ITEM_DSUBCATEGORYRPM_PROJ_SUBCATEGORYSubcategoryNUMC4Mandatory
/RPM/ITEM_DGEOGRAPHYRPM_TV_PROJECT_GEOGRAPHYAreaCHAR4Mandatory
/RPM/ITEM_DESCALATIONRPM_TV_ESCALATIONEscalationCHAR1Conditional
/RPM/ITEM_DCURRENCYRPM_TV_CURRENCYCURRENCYCUKY5Mandatory
/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_DZXX1
Investment CategoryNUMC2Mandatory
/RPM/ITEM_DZXX2
Spending RangeNUMC2Mandatory
/RPM/ITEM_DZXX3
Business Unit/ DomainNUMC2Mandatory
/RPM/ITEM_DZXX4
End User MarketNUMC2Conditional
/RPM/ITEM_DZXX5
Market DriverNUMC2Conditional
/RPM/ITEM_DZXX6
ClusterNUMC2Conditional
/RPM/ITEM_DZXX7
GBU Product FamilyCHAR40Conditional
/RPM/ITEM_DZXX8
GBU Product CategoryCHAR40Conditional
/RPM/ITEM_DZXX9
Product (s)CHAR40Mandatory
/RPM/ITEM_DZXX10
Export ControlNUMC2Mandatory
/RPM/ITEM_DZXX11
Need-to-knowCHAR1Mandatory
/RPM/ITEM_DZXX12
Sustainability ScoreNUMC3Mandatory
/RPM/ITEM_DZXX13
EU TaxonomyNUMC2Conditional
/RPM/ITEM_DZXX14HROBJIDPerson ResponsibleNUMC8Mandatory
/RPM/ITEM_DZXX15STEXTPerson ResponsibleSTEXT40System Generated
/RPM/ITEM_DZXX16HROBJIDProject Financial ControllerNUMC8Mandatory
/RPM/ITEM_DZXX17STEXTProject Financial ControllerSTEXT40System 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_DZXX28
Investment ReasonNUMC2Mandatory
/RPM/ITEM_DZXX29
Budget ProvisionCHAR10Conditional
/RPM/ITEM_DZXX30
Opportunity IDCHAR40Conditional
/RPM/ITEM_DZXX31
ArchetypeNUMC2Conditional
/RPM/ITEM_DZXX32
Must Do JustificationNUMC2Conditional
/RPM/ITEM_DZXX33PS_PSPIDLegacy Project IDCHAR24Conditional
/RPM/ITEM_DZXX34WERKS_DPlantCHAR4Conditional
/RPM/ITEM_DZXX35
Idea IDCHAR40Conditional
/RPM/ITEM_DZXECJ
Justification (Export Control)CHAR60Conditional
/RPM/ITEM_DZXX36
Subsidy Relevant CHAR1Conditional


Relationship between /RPM/ITEM_D and CGPL_TEXT is the field /RPM/ITEM_D-GUID


Data Cleansing

.

IDCriticalityError Message/Report DescriptionRuleOutputSource System
1Medium
Completed PS projects to be closed
SAP ECC


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.


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
2Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. SyWay 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
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

It is a Required Field: Preload Check to be done to confirm that this field is filled 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 the Data Collection Template

TEXT1Name

40 character description of the PPM Item

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

LTEXTItem DescriptionLong-text Description, this field is used to provide a concise description of the PPM Item. Conditional for projects where additional project scope information is required
STATUSItem Status

Represents status of an item (from Customizing). Refer configuration table field /RPM/ITEM_STATUS- STATUS against ITEM_TYPE for the allowed values of the selected Item Type.

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

PLANNED_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 the Data Collection Template

PLANNED_FINISHPlanned 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 the Data Collection Template

FORECAST_STARTForecasted StartA forecast start date is predictive date when an item/project is likely to begin. In the Syway design, if this field is available in Operational Project Management tool (outside SAP) then required to be maintained. 
FORECAST_FINISHForecasted FinishA forecast finish date is predictive date when an item/project is likely to complete. In the Syway design, if this field is available in Operational Project Management tool (outside SAP) then required to be maintained.
CATEGORYCategory

In Syway, "Category" represents the business driver. It is a dropdown field with customizable values. This is a dropdown field RPM_PROJ_CAT-CATEGORY.

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

SUBCATEGORYSubcategory

In Syway, "Sub Category" represents the rationale behind the investment/expense for the item/project. This is a dropdown field whose values are configurable and depend on the selected "Category". Refer configuration table field RPM_PROJ_SUBCAT- SUBCATEGORY against the selected field RPM_PROJ_SUBCAT- CATEGORY.

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

GEOGRAPHYArea

Represents Company code; the legal entity in which the Syway Project will be executed. Dropdown values from V_DPR_AREA- AREA.

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

ESCALATIONEscalationCheckbox; Selection indicates if PPM item is qualified for the Prioritization process. For R&I it will be managed at cluster level PPM Item
INITIATIVE_IDINITIATIVE IDInternal ID of Initiative where Item must be linked to Initiative
ZXX1Investment category

In SyWay, investment category is a mandatory field to define the drivers for the project Growth/ Sustenance. Dropdown values from /SYQ/T_INV_CAT

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

ZXX2Spending Range

The Capex spending range used for reporting the project size i.e. XS, S, M, L & XL.  Dropdown values from /SYQ/T_SPND_RNGE

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

ZXX3Business Unit/ DomainBusiness Unit/ Domain field is an organizational unit within GBU/ Function which owns the project.  Dropdown values from  /SYQ/T_BU_DMN
ZXX4End User MarketClassification of the industrial end users based upon type of industry e.g. aerospace, automative etc. Dropdown values from  /SYQ/T_END_USR_MKT
ZXX5Market Driver

Market driver in SyWay is factor that influence demand/ growth/ success of the project.

Dropdown values from /SYQ/T_MKT_DRVR

ZXX6ClusterIn 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.  Field content from /SYQ/T_CLSTR
ZXX7GBU Product FamilyGBU Product Family relevant for the project. When Item Type is related to either IS or R&I project then either of GBU product family, GBU product category or Product is required.
ZXX8GBU Product CategoryGBU Product Category relevant for the project. When Item Type is related to either IS or R&I project then either of GBU product family, GBU product category or Product is required.
ZXX9Product (s)Product relevant for the project. When Item Type is related to either IS or R&I project then either of GBU product family, GBU product category or Product is required.
ZXX10Export ControlTo identify if the project is applicable for regulatory governence, a dropdown list will appear with values Yes, No & Non-Determined.  This is a dropdown field from /SYQ/T_EXPORT_CNTL
ZXECJJustification (Export Control)

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

ZXX11Need-to-know

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

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

ZXX12Sustainability ScoreThis field is used to determine whether the project is subject to environmental compliance requirements. Questionnaire will be assigned to this field.
ZXX13EU TaxonomyEU Taxonomy is mandatory field for IS projects.  This is a dropdown field from /SYQ/T_EU_TXNMY
ZXX14Person Responsible

This field represent Position of the Person Responsible for WBS elements (Project Manager) and is mandatory for all SyWay business functions. Manually selected from the drop-down list. Refer configuration table field TCJ04-PS_VERNR for field validation.

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

ZXX16Project Financial Controller

This field represent Position of the Project Financial Controller for a project and is mandatory for all SyWay business functions. Manually selected from the drop-down list. Refer configuration table field TCJ05-ASTNR for field validation.

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

ZXX18Starting Risk MagnitudeThis field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction  This is a dropdown field /SYQ/T_RISK_MAGNITUDE
ZXX19Starting Risk LikelihoodThis field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction This is a dropdown field /SYQ/T_RISK_LKLHD
ZXX20Residual Risk MagnitudeThis field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction This is a dropdown field  from /SYQ/T_RISK_MAGNITUDE
ZXX21Residual Risk LikelihoodThis field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction This is a dropdown field from /SYQ/T_RISK_LKLHD
ZXX22Regulatory Mandated MagnitudeThis field is mandatory if dropdown value of the "Category" field = Regulatory compliance  This is a dropdown field from /SYQ/T_REG_MAGNITUDE
ZXX23Regulatory Mandated LikelihoodThis field is mandatory if dropdown value of the "Category" field = Regulatory compliance  This is a dropdown field from /SYQ/T_REG_LKLHD
ZXX24Regulatory Mandated Time Horizon (to start project)This field is mandatory if dropdown value of the "Category" field = Regulatory compliance This is a dropdown field from /SYQ/T_REG_TIME_HORIZON
ZXX25Capitalization DateFor ongoing Capex projects SyWay carries out "Depreciation forecast", this date is mandatory for the "Capital Projects" Item types. Item Types are Z001,Z002, Z003, Z008, Z009, Z011
ZXX26Profit Centre

Profit centre is required on PPM Item to create Project in SAP PS automatically. Refer master table field CEPC-PRCTR for Profit center list.

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

ZXX27WeGo IDSystem calculated score for prioritization and ranking
ZXX28Investment Reason

In Syway, "Investment Reason" represent the detailed investment/ expense reason. This is a dropdown field and depend on the selected "Sub Category" This is a dropdown field from /SYQ/T_INV_REASON

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

ZXX29Budget Provision"Budget Provision" Item Type exists as a distinct category. Additionally, a custom field named "Budget Provision" will be available in other CAPEX item types. This field will feature a dropdown containing Budget Provision PPM items for selection.
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. N/A for IS & IT PPM Items.  Refer configuration table field RPM_PROJ_TYPE- PTYPE against the selected field RPM_PROJ_TYPE- CATEGORY. This is a dropdown field from /SYQ/T_ARCHETYPE

Conditional based on Category

ZXX32Must Do Justification

If financial analysis required, then this field is mandatory.

Required if Category is-
1. New growth - Capacity expansion   or
2. Existing growth - Capacity improvement  or
3. Asset Management

ZXX33Legacy Project IDLegacy 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.
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 the Data Collection Template

ZXX35Idea ID

Field to store the Idea number where known.

This is an optional field.

ZXX36Subsidy Relevant

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

In conjunction with DCT business user will be provided with Person Responsible / Applicant list for reference.

Extraction Dependencies

Item #Step DescriptionTeam Responsible

1

Ensure DCT is collected for Item

Data Team

2

Perform preliminary completeness check

Data Team

3

Raise issues as defects if Req # 1 to 2 are not met

Data Team

4

Repeat Req # 1 to 3 if required

Data Team


Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow Syniti Migrate
to make the data Target ready:

  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
1WP2PROJPSPIDIDS/4 Hana/RPM/ITEM_DLegacy Project IDLegacy 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
2WP2


S/4 Hana/RPM/ITEM_DITEM_TYPEType

Apply first successful rule


If PROJ-PSPID start with RR* then use data from 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


3WP2PROJTEXT1Project DescriptionS/4 HanaCGPL_TEXTTEXT1Name

Copy source to target

4WP2STXLLTEXTCLUSTDS/4 HanaSTXLLTEXTCLUSTDCopy source to target
7WP2PROJSPROGForecast start date of project definitionS/4 Hana/RPM/ITEM_DFORECAST_STARTForecasted StartCopy from source, format YYYYMMDD
8WP2PROJEPROGForecast finish date for project definitionS/4 Hana/RPM/ITEM_DFORECAST_FINISHForecasted FinishCopy from source, format YYYYMMDD
9WP2PROJPLFAZProject planned start dateS/4 Hana/RPM/ITEM_DPLANNED_STARTPlanned StartCopy from source, format YYYYMMDD
10WP2PROJPLSEZProject planned finish dateS/4 Hana/RPM/ITEM_DPLANNED_FINISHPlanned Finish

Copy from source, format YYYYMMDD

11WP2PROJVBUKRCompany code for the projectS/4 Hana/RPM/ITEM_DGEOGRAPHY
AreaCopy from Source
12WP2PROJPWHIEWBS currency (project definition)S/4 Hana/RPM/ITEM_DCURRENCYCURRENCY

Copy from Source

13WP2PROJPRCTRProfit CenterS/4 Hana/RPM/ITEM_DZXX26Profit CentreValue Mapping:  Profit Center Old to New
14WP2PROJZZ_IZWEKInvestment reasonS/4 Hana/RPM/ITEM_DZXX29Investment ReasonValue Mapping:  Investment Reason Old to new
15WP2PROJWERKSPlant S/4 Hana/RPM/ITEM_DZXX34PlantValue Mapping: Old Plant to New
16WP2PROJZZ_POSITPosition of the person responsibleS/4 Hana/RPM/ITEM_DZXX14Person responsible Position IDCopy from Source
17WP2PRPSZZ_WEGO_IDWEGO IDS/4 Hana/RPM/ITEM_DZXX27Wego IDIf all WBS Elements for the PSPID record has the same WEGO Number only.
1PF2PROJPSPIDIDS/4 Hana/RPM/ITEM_DLegacy Project IDLegacy 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
2PF2PROJ

S/4 Hana/RPM/ITEM_DITEM_TYPEType

Apply first successful rule only


If PROJ-PSPID start with R-* 

then use data from 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

3PF2PROJTEXT1Project DescriptionS/4 HanaCGPL_TEXTTEXT1Name

Copy source to target

4PF2STXLLTEXTCLUSTDS/4 HanaSTXLLTEXTCLUSTDCopy source to target
7PF2PROJSPROGForecast start date of project definitionS/4 Hana/RPM/ITEM_DFORECAST_STARTForecasted StartCopy from source, format YYYYMMDD
8PF2PROJEPROGForecast finish date for project definitionS/4 Hana/RPM/ITEM_DFORECAST_FINISHForecasted FinishCopy from source, format YYYYMMDD
9PF2PROJPLFAZProject planned start dateS/4 Hana/RPM/ITEM_DPLANNED_STARTPlanned StartCopy from source, format YYYYMMDD
10PF2PROJPLSEZProject planned finish dateS/4 Hana/RPM/ITEM_DPLANNED_FINISHPlanned Finish

Copy from source, format YYYYMMDD

11PF2PROJVBUKRCompany code for the projectS/4 Hana/RPM/ITEM_DGEOGRAPHY
AreaValue Mapping: Old to New Company Code
12PF2PROJPWHIEWBS currency (project definition)S/4 Hana/RPM/ITEM_DCURRENCYCurrency

Copy from Source

13PF2PROJPRCTRProfit CenterS/4 Hana/RPM/ITEM_DZXX26Profit CentreValue Mapping:  Profit Center Old to New
14PF2PROJZZ_IZWEKInvestment reasonS/4 Hana/RPM/ITEM_DZXX29Investment ReasonValue Mapping:  Investment Reason Old to new
15PF2PROJWERKSPlant S/4 Hana/RPM/ITEM_DZXX34PlantValue Mapping: Old Plant to New
16PF2PROJZZ_POSITPosition of the person responsibleS/4 Hana/RPM/ITEM_DZXX14Person responsible Position IDCopy from Source
17PF2PRPSZZ_WEGO_IDWEGO IDS/4 Hana/RPM/ITEM_DZXX27Wego IDIf all WBS Elements for the PSPID record has the same WEGO Number only
1



S/4 Hana/RPM/ITEM_DEXTERNAL_IDIDSystem Generated
2DCT
PARENT_IDParent Bucket IDS/4 Hana/RPM/ITEM_DPARENT_IDParent Bucket IDCopy from source to target system
3DCT


S/4 Hana/RPM/ITEM_DPORTFOLIO_IDPortfolio ID

Default to Syensqo

4DCT
ITEM_TYPETypeS/4 Hana/RPM/ITEM_DITEM_TYPETypeCopy from source to target system
5DCT
TEXT1NameS/4 HanaCGPL_TEXTTEXT1NameCopy from source to target system
6DCT
LTEXTItem DescriptionS/4 HanaSTXLLTEXTCLUSTDCopy from source to target system
7DCT
STATUSItem StatusS/4 Hana/RPM/ITEM_DSTATUSItem StatusCopy from source to target system
8DCT
PLANNED_STARTPlanned StartS/4 Hana/RPM/ITEM_DPLANNED_STARTPlanned StartCopy from source to target system
9DCT
PLANNED_FINISHPlanned FinishS/4 Hana/RPM/ITEM_DPLANNED_FINISHPlanned FinishCopy from source to target system
10DCT
FORECAST_STARTForecasted StartS/4 Hana/RPM/ITEM_DFORECAST_STARTForecasted StartCopy from source to target system
11DCT
FORECAST_FINISHForecasted FinishS/4 Hana/RPM/ITEM_DFORECAST_FINISHForecasted FinishCopy from source to target system
12DCT
CATEGORYCategoryS/4 Hana/RPM/ITEM_DCATEGORYCategoryCopy from source to target system
13DCT
SUBCATEGORYSubcategoryS/4 Hana/RPM/ITEM_DSUBCATEGORYSubcategoryCopy from source to target system
14DCT
GEOGRAPHYAreaS/4 Hana/RPM/ITEM_DGEOGRAPHYAreaCopy from source to target system
18DCT
ESCALATIONEscalationS/4 Hana/RPM/ITEM_DESCALATIONEscalationCopy from source to target system
19DCT
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

20



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



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



S/4 Hana/RPM/ITEM_DPERIODTYPEFin Period BreakdownDefault to "12"(Annually)
23DCT
INITIATIVE_IDINITIATIVE IDS/4 Hana/RPM/ITEM_DINITIATIVE_IDINITIATIVE IDCopy from source to target system
24DCT
ZXX1Investment categoryS/4 Hana/RPM/ITEM_DZXX1Investment categoryCopy from source to target system
25DCT
ZXX2Spending RangeS/4 Hana/RPM/ITEM_DZXX2Spending RangeCopy from source to target system
26DCT
ZXX3Business Unit/ DomainS/4 Hana/RPM/ITEM_DZXX3Business Unit/ DomainCopy from source to target system
27DCT
ZXX4End User marketS/4 Hana/RPM/ITEM_DZXX4End User marketCopy from source to target system
28DCT
ZXX5Market driverS/4 Hana/RPM/ITEM_DZXX5Market driverCopy from source to target system
29DCT
ZXX6ClusterS/4 Hana/RPM/ITEM_DZXX6ClusterCopy from source to target system
30DCT
ZXX7GBU product familyS/4 Hana/RPM/ITEM_DZXX7GBU product familyCopy from source to target system
31DCT
ZXX8GBU product categoryS/4 Hana/RPM/ITEM_DZXX8GBU product categoryCopy from source to target system
32DCT
ZXX9Product (s)S/4 Hana/RPM/ITEM_DZXX9Product (s)Copy from source to target system
33DCT
ZXX10Export control relevantS/4 Hana/RPM/ITEM_DZXX10Export control relevantCopy from source to target system
34DCT
ZXX11Need-to-knowS/4 Hana/RPM/ITEM_DZXX11Need-to-knowCopy from source to target system
35DCT
ZXX12Overall Sustainability ScoreS/4 Hana/RPM/ITEM_DZXX12Overall Sustainability ScoreCopy from source to target system
36DCT
ZXX13EU taxonomyS/4 Hana/RPM/ITEM_DZXX13EU taxonomyCopy from source to target system
37DCT
ZXX14Person responsible Position IDS/4 Hana/RPM/ITEM_DZXX14Person responsible Position IDCopy from source to target system
38



S/4 Hana/RPM/ITEM_DZXX15Person Responsible Position NameValue Mapping: Position Name from Position
Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001
41DCT
ZXX16Project Financial Controller Position IDS/4 Hana/RPM/ITEM_DZXX16Project Financial Controller Position IDCopy from source to target system
42



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
48DCT
ZXX18Starting risk MagnitudeS/4 Hana/RPM/ITEM_DZXX18Starting risk MagnitudeCopy from source to target system
49DCT
ZXX19Starting risk LikelihoodS/4 Hana/RPM/ITEM_DZXX19Starting risk LikelihoodCopy from source to target system
50DCT
ZXX20Residual risk MagnitudeS/4 Hana/RPM/ITEM_DZXX20Residual risk MagnitudeCopy from source to target system
51DCT
ZXX21Residual risk LikelihoodS/4 Hana/RPM/ITEM_DZXX21Residual risk LikelihoodCopy from source to target system
53DCT
ZXX22Regulatory Mandated MagnitudeS/4 Hana/RPM/ITEM_DZXX22Regulatory Mandated MagnitudeCopy from source to target system
54DCT
ZXX23Regulatory Mandated LikelihoodS/4 Hana/RPM/ITEM_DZXX23Regulatory Mandated LikelihoodCopy from source to target system
55DCT
ZXX24Regulatory Mandated Time Horizon (to start project)S/4 Hana/RPM/ITEM_DZXX24Regulatory Mandated Time Horizon (to start project)Copy from source to target system
56DCT
ZXX25Capitalization DateS/4 Hana/RPM/ITEM_DZXX25Capitalization DateCopy from source to target system
57DCT
ZXX26Profit CentreS/4 Hana/RPM/ITEM_DZXX26Profit CentreCopy from source to target system
58DCT
ZXX27Project Equivalent ScoreS/4 Hana/RPM/ITEM_DZXX27Project Equivalent ScoreCopy from source to target system
62DCT
ZXX28WeGo IDS/4 Hana/RPM/ITEM_DZXX28WeGo IDCopy from source to target system
64DCT
ZXX29Investment ReasonS/4 Hana/RPM/ITEM_DZXX29Investment ReasonCopy from source to target system
65DCT
ZXX30Budget ProvisionS/4 Hana/RPM/ITEM_DZXX30Budget ProvisionCopy from source to target system
66DCT
ZXX31Opportunity IDS/4 Hana/RPM/ITEM_DZXX31Opportunity IDCopy from source to target system
67DCT
ZXX32ArchetypeS/4 Hana/RPM/ITEM_DZXX32ArchetypeCopy from source to target system
68DCT
ZXX33Must Do JustificationS/4 Hana/RPM/ITEM_DZXX33Must Do JustificationCopy from source to target system
69DCT
ZXX34Legacy Project IDS/4 Hana/RPM/ITEM_DZXX34Legacy 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 to target system
70DCT
ZXX35PlantS/4 Hana/RPM/ITEM_DZXX35PlantCopy from source to target system
71DCT
ZXECJJustification (Export Control)S/4 Hana/RPM/ITEM_DZXECJJustification (Export Control)Copy from source to target system
72DCT
ZXX36Subsidy Relevant S/4 Hana/RPM/ITEM_DZXX35Subsidy Relevant Copy from source to target system

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.


The Standard template for the upload of Item to 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

Transformation Mapping

Mapping Table NameMapping Table Description
Company CodeValue Mapping: Old to New Company Code
T001Value Mapping: Currency From Company Code
HRP1000Value Mapping: Position Name from Position
PlantValue Mapping: Old Plant to New
Profit CenterValue Mapping:  Profit Center Old to New
Investment ReasonValue Mapping:  Investment Reason Old to new

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
6Post Process - for all Items where Legacy Project ID not blank - Create PS Project definition with WBS element hierarchy (Level 1 & 2) from the approved PPM item by setting stage gate 1 to Approved.  Program required to perform mass status change.SyWay Data Team
7Validate few records loaded by accessing PS Project AppSyWay Data Team
8

 Generate post load report if step 5 is validated

SyWay Data Team
9

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

Item #Configuration Item
1Override Default Global Settings  (Master Switches  0002   Switched off - Item will have manual ID)
2Define Currency Units
3Define Period Types
4Define Capacity Units
5Configure Fields for Mass Import
6Item Types - /RPM/ITEM_TYPE- ITEM_TYPE
7Item Type Status - /RPM/ITEM_STATUS- STATUS
8Category - RPM_PROJ_CAT- CATEGORY
9Sub-Category RPM_PROJ_SUBCAT- SUBCATEGORY
10Area - DPR_AREA
11Project Type - RPM_PROJ_TYPE
12Plant - T001W
13Responsible Person - TCJ04
14Applicant - TCJ05
15Priority Group
16Investment category
17Spending Range
18Business Unit/ Domain 
19End User market
20GBU product family
21GBU product category
22Product (s) 
23Investment Reason
24Archetype
25Cluster 

Conversion Objects

Object #Preceding Object Conversion Approach
1113Portfolio Bucket Hierarchy
1023Portfolio Initiative

1073

Profit Centre

1019

Template Projects



Error Handling

Error TypeError DescriptionAction Taken

Invalid Data

Invalid Portfolio

Validate Transformation Rules

Invalid Data

Invalid Bucket ID (Parent ID does not exist)

Validate DCT content

Invalid DataInvalid Item TypeValidate Transformation rules and DCT values
Invalid DataInvalid entry in field "Field Name"Validate the DCT content for the named field
Invalid DataInvalid datesValidate format of the date fields.


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

Conversion Accuracy

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


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.


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.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 40) 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

  • No labels