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 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.
    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 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 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 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.   The creation will be triggered for items that have legacy projects and items created for Capital Spares, Capital Purchases and Capital Leases.



Identification Logic

Capital project is a project that has any WBS elements with a Investment Profile. PRPS-IZWEK

IT Project is a project that has a WBS element 

  • in WP2 user field 1 starting with IT  PRPS-USR00
  • in PF2 user field 2 starts with IT    PRPS-USR01

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

Budgeted Opex is any other project that has any WBS elements with budget.  WBS has entry in BPGE for value type 41


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 current year.

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.

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_DPTYPE

RPM_PROJECTTYPE

Main Business DriverNUMC4Mandatory
/RPM/ITEM_DTTYPERPM_PROJECT_TECHTYPEInvestment CategoryNUMC4Mandatory
/RPM/ITEM_DGEOGRAPHYRPM_TV_PROJECT_GEOGRAPHYCompany CodeCHAR4Mandatory
/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_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
Mandatory
/RPM/ITEM_DZXX11
Need-to-knowCHAR1Mandatory
/RPM/ITEM_DZXX14HROBJIDPerson ResponsibleNUMC8Mandatory
/RPM/ITEM_DZXX15STEXTPerson ResponsibleSTEXT40System Generated
/RPM/ITEM_DZXX16HROBJIDProject Financial ControllerNUMC8Mandatory
/RPM/ITEM_DZXX17STEXTProject Financial ControllerSTEXT40System Generated
/RPM/ITEM_DZXX37
Scoring Methodology

Mandatory
/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
ArchetypeNUMC2Mandatory
/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
/RPM/DECISIONDECISION_ID/RPM/TV_EXTIDIDCHAR48Mandatory
/RPM/DECISIONSTATUS/RPM/TV_STATUS_COMMONSTATUSCHAR5Conditional
STXLCLUSTD (Sub_Relevance for identification in Transformation)CLUSTDSubsidy RelevanceCLUSTD
Conditional
STXLCLUSTD (Key_Assump for identification in Transformation)CLUSTDKey AssumptionsCLUSTD
Conditional
STXLCLUSTD (Other for identification in Transformation))CLUSTDOther InformationCLUSTD
Conditional


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


Data Cleansing

This is a completely new object based on Projects and WBS information.   All cleansing requirements dealt with in CNV-1024 Project Definition - SyWay Project - Syensqo - Wiki knowledge base and CNV-1026 WBS - CAPEX, OPEX, Statistical - SyWay Project - Syensqo - Wiki knowledge base

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.


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
Portfolio_IDPortfolio ID

Unique Identifier for Syensqo Portfolio ID

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

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

40 character 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-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

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

CATEGORYCategory

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

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

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

INITIATIVE_IDINITIATIVE ID

Internal ID of Initiative where Item must be linked to Initiative

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 corporate-led segmentation dimension, 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

Classification of the industrial end users based upon type of industry.

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

This field defined structured arrangement of the organizational authority.

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

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.
ZXX7GBU Product Family

Product Hierarchy relevant for the project. Any of the Product Hierarchy level can be selected via this field.

(WBS element of the Project will be maintained in the Product's master data i.e. in Material Master) 

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

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

JustificationJustification (Export Control)

Justification to be provided when Export Control is applicable.

Preload Check to be done to confirm that this field is filled in the Data Collection Template if the Export Control field is selected.

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

ZXX13EU Taxonomy

EU Taxonomy is mandatory field for IS projects.  

This is a dropdown field from /SYQ/T_EU_TXNMY

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

ZXX14Person Responsible

This field represent Position of the Person Responsible for WBS elements (Project Manager) 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

This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction  

This is a dropdown field /SYQ/T_RISK_MAGNITUDE

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

ZXX19Starting Risk Likelihood

This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction

This is a dropdown field /SYQ/T_RISK_LKLHD

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

ZXX20Residual Risk Magnitude

This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction

This is a dropdown field  from /SYQ/T_RISK_MAGNITUDE

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

ZXX21Residual Risk Likelihood

This field is mandatory if dropdown value of the "Category" field = HSE Risk reduction or Business risk reduction

This is a dropdown field from /SYQ/T_RISK_LKLHD

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

ZXX22Regulatory Mandated Magnitude

This field is mandatory if dropdown value of the "Category" field = Regulatory compliance: Preload Check to be done

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

This field is mandatory if dropdown value of the "Category" field = Regulatory compliance, Preload Check to be done  

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)

This field is mandatory if dropdown value of the "Category" field = Regulatory compliance, Preload Check to be done

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

For ongoing Capex projects SyWay carries out "Depreciation forecast", this date is mandatory for the "Capital Projects" Item types.

It is a required field for 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 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. 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. 

ZXX27WeGo IDWego ID.  Relevant for the R&I projects only.
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 in 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. 

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

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

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

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

This is an optional field.

ZXX36Subsidy

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

This is an optional field.

InstanceInstance

Instance where the item is to be loaded.

ACT_DPCPTActive Decision Point

Indicates the active decision point for the item.

To be selected if item is not initial phase

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

Sub_RelevanceSubsidy Relevance

Long-text description, this field is used to provide a concise description of the Subsidy Relevance.

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

Long-text description, this field is used to provide key Assumptions related to projects.

Conditional for Items where assumptions are to be maintained,

This is an optional field for migration

VariationVariations

Long-text description, this field is used to provide details about key project variations.

Conditional for projects where variation or change request is required.

This is an optional field for migration

OtherOther Information

Long-text description, this field is used to provide additional details about project.

This is an optional field for migration

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

1

Ensure DCT is collected for Item

Data Team

2

Perform preliminary completeness check

Data Team

3

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

Data Team

4

Repeat Req # 1 to 3 if required

Data Team


Transformation

The Target fields are mapped to the applicable Legacy field that will be its source,. This identifies the transformation activity required to allow Syniti Migrate
to make the data Target ready:

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


3WP2PROJTEXT1Project DescriptionS/4 HanaCGPL_TEXTTEXT1Name

Copy source to target

4WP2STXLLTEXTLong DescriptionS/4 HanaSTXLLTEXTDescriptionCopy source to target
7WP2PROJPLFAZProject planned start dateS/4 Hana/RPM/ITEM_DPLANNED_STARTPlanned StartCopy from source, format YYYYMMDD
8WP2PROJPLSEZProject planned finish dateS/4 Hana/RPM/ITEM_DPLANNED_FINISHPlanned Finish

Copy from source, format YYYYMMDD

9WP2PROJVBUKRCompany code for the projectS/4 Hana/RPM/ITEM_DGEOGRAPHY
AreaValue Mapping: Old to New Company Code
10WP2PROJPWHIEWBS currency (project definition)S/4 Hana/RPM/ITEM_DCURRENCYCURRENCY

Copy from Source

11WP2PROJPRCTRProfit CenterS/4 Hana/RPM/ITEM_DZXX26Profit CentreValue Mapping:  Profit Center Old to New
12WP2PROJWERKSPlant S/4 Hana/RPM/ITEM_DZXX34PlantValue Mapping: Old Plant to New
13WP2PROJZZ_POSITPosition of the person responsibleS/4 Hana/RPM/ITEM_DZXX14Person responsible Position IDValue Mapping: Old Position ID  to New Position ID
14WP2PRPSZZ_WEGO_IDWEGO IDS/4 Hana/RPM/ITEM_DZXX27Wego IDIf all WBS Elements for the PSPID record has the same WEGO Number only.
15PF2PROJPSPIDIDS/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
16PF2PROJ

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

17PF2PROJTEXT1Project DescriptionS/4 HanaCGPL_TEXTTEXT1Name

Copy source to target

18PF2STXLLTEXTLong DescriptionS/4 HanaSTXLLTEXTDescriptionCopy source to target
21PF2PROJPLFAZProject planned start dateS/4 Hana/RPM/ITEM_DPLANNED_STARTPlanned StartCopy from source, format YYYYMMDD
22PF2PROJPLSEZProject planned finish dateS/4 Hana/RPM/ITEM_DPLANNED_FINISHPlanned Finish

Copy from source, format YYYYMMDD

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

Copy from Source

25PF2PROJPRCTRProfit CenterS/4 Hana/RPM/ITEM_DZXX26Profit CentreValue Mapping:  Profit Center Old to New
26PF2PROJWERKSPlant S/4 Hana/RPM/ITEM_DZXX34PlantValue Mapping: Old Plant to New
27PF2PROJZZ_POSITPosition of the person responsibleS/4 Hana/RPM/ITEM_DZXX14Person responsible Position IDValue Mapping: Old Position ID  to New Position ID
28PF2PRPSZZ_WEGO_IDWEGO IDS/4 Hana/RPM/ITEM_DZXX27Wego IDIf all WBS Elements for the PSPID record has the same WEGO Number only
29



S/4 Hana/RPM/ITEM_DEXTERNAL_IDIDSystem Generated
30DCT
PARENT_IDParent Bucket IDS/4 Hana/RPM/ITEM_DPARENT_IDParent Bucket IDManually copy from Non ECC source
31DCT
 Portfolio_IDPortfolio IDS/4 Hana/RPM/ITEM_DPORTFOLIO_IDPortfolio ID

Manually copy from Non ECC source

32DCT
ITEM_TYPETypeS/4 Hana/RPM/ITEM_DITEM_TYPETypeManually copy from Non ECC source
33DCT
TEXT1NameS/4 HanaCGPL_TEXTTEXT1NameManually copy from Non ECC source
34DCT
LTEXTItem DescriptionS/4 HanaSTXLCLUSTDDescriptionManually copy from Non ECC source
35DCT
STATUSItem StatusS/4 Hana/RPM/ITEM_DSTATUSItem StatusManually copy from Non ECC source
36DCT
PLANNED_STARTPlanned StartS/4 Hana/RPM/ITEM_DPLANNED_STARTPlanned StartManually copy from Non ECC source
37DCT
PLANNED_FINISHPlanned FinishS/4 Hana/RPM/ITEM_DPLANNED_FINISHPlanned FinishManually copy from Non ECC source
40DCT
CATEGORYCategoryS/4 Hana/RPM/ITEM_DCATEGORYCategoryManually copy from Non ECC source
41DCT
SUBCATEGORYSubcategoryS/4 Hana/RPM/ITEM_DSUBCATEGORYSubcategoryManually copy from Non ECC source
42DCT
GEOGRAPHYAreaS/4 Hana/RPM/ITEM_DGEOGRAPHYAreaManually copy from Non ECC source
44DCT
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

45



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



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



S/4 Hana/RPM/ITEM_DPERIODTYPEFin Period BreakdownDefault to "12"(Annually)
48DCT
INITIATIVE_IDINITIATIVE IDS/4 Hana/RPM/ITEM_DINITIATIVE_IDINITIATIVE IDManually copy from Non ECC source
49



S/4 Hana/RPM/ITEM_DZXX1Investment categoryThis is determined based on the values maintained in Investment Reason
50DCT
ZXX2Spending RangeS/4 Hana/RPM/ITEM_DZXX2Spending RangeManually copy from Non ECC source
51DCT
ZXX3GBU Market HierarchyS/4 Hana/RPM/ITEM_DZXX3GBU Market HierarchyManually copy from Non ECC source
52DCT
ZXX4End User marketS/4 Hana/RPM/ITEM_DZXX4End User marketManually copy from Non ECC source
53DCT
ZXX5Corporate HierarchyS/4 Hana/RPM/ITEM_DZXX5Corporate HierarchyManually copy from Non ECC source
54DCT
ZXX6ClusterS/4 Hana/RPM/ITEM_DZXX6ClusterManually copy from Non ECC source
55DCT
ZXX7GBU product familyS/4 Hana/RPM/ITEM_DZXX7GBU product familyManually copy from Non ECC source
58DCT
ZXX10Export controlS/4 Hana/RPM/ITEM_DZXX10Export controlManually copy from Non ECC source
84DCT
JustificationJustification (Export Control)S/4 HanaSTXLJustificationJustification (Export Control)Manually copy from Non ECC source
59DCT
ZXX11Need-to-knowS/4 Hana/RPM/ITEM_DZXX11Need-to-knowManually copy from Non ECC source
61DCT
ZXX13EU taxonomyS/4 Hana/RPM/ITEM_DZXX13EU taxonomyManually copy from Non ECC source
62DCT
ZXX14Person responsible Position IDS/4 Hana/RPM/ITEM_DZXX14Person responsible Position IDManually copy from Non ECC source
63



S/4 Hana/RPM/ITEM_DZXX15Person Responsible Position NameValue Mapping: Position Name from Position
Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001
64DCT
ZXX16Project Financial Controller Position IDS/4 Hana/RPM/ITEM_DZXX16Project Financial Controller Position IDManually copy from Non ECC source
65



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
66DCT
ZXX18Starting risk MagnitudeS/4 Hana/RPM/ITEM_DZXX18Starting risk MagnitudeManually copy from Non ECC source
67DCT
ZXX19Starting risk LikelihoodS/4 Hana/RPM/ITEM_DZXX19Starting risk LikelihoodManually copy from Non ECC source
68DCT
ZXX20Residual risk MagnitudeS/4 Hana/RPM/ITEM_DZXX20Residual risk MagnitudeManually copy from Non ECC source
69DCT
ZXX21Residual risk LikelihoodS/4 Hana/RPM/ITEM_DZXX21Residual risk LikelihoodManually copy from Non ECC source
70DCT
ZXX22Regulatory Mandated MagnitudeS/4 Hana/RPM/ITEM_DZXX22Regulatory Mandated MagnitudeManually copy from Non ECC source
71DCT
ZXX23Regulatory Mandated LikelihoodS/4 Hana/RPM/ITEM_DZXX23Regulatory Mandated LikelihoodManually copy from Non ECC source
72DCT
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
73DCT
ZXX25Capitalization DateS/4 Hana/RPM/ITEM_DZXX25Capitalization DateManually copy from Non ECC source
74DCT
ZXX26Profit CentreS/4 Hana/RPM/ITEM_DZXX26Profit CentreManually copy from Non ECC source
76DCT
ZXX27WeGo IDS/4 Hana/RPM/ITEM_DZXX27WeGo IDManually copy from Non ECC source
77DCT
ZXX28Investment ReasonS/4 Hana/RPM/ITEM_DZXX28Investment ReasonManually copy from Non ECC source
78DCT
ZXX29Budget ProvisionS/4 Hana/RPM/ITEM_DZXX29Budget ProvisionManually copy from Non ECC source
79DCT
ZXX30Opportunity IDS/4 Hana/RPM/ITEM_DZXX30Opportunity IDManually copy from Non ECC source
80DCT
ZXX31ArchetypeS/4 Hana/RPM/ITEM_DZXX31ArchetypeManually copy from Non ECC source
81DCT
ZXX32Must Do JustificationS/4 Hana/RPM/ITEM_DZXX32Must Do JustificationManually copy from Non ECC source
83DCT
ZXX34PlantS/4 Hana/RPM/ITEM_DZXX34PlantManually copy from Non ECC source
85DCT
ZXX35Idea IDS/4 Hana/RPM/ITEM_DZXX35Idea IDManually copy from Non ECC source
86DCT
ZXX36Subsidy RelevantS/4 Hana/RPM/ITEM_DZXX36Subsidy RelevantManually copy from Non ECC source
87DCT
Sub_RelevanceSubsidy RelevanceS/4 HanaSTXLSub_RelevanceSubsidy RelevanceManually copy from Non ECC source
88DCT
Key_AssumpKey AssumptionsS/4 HanaSTXLKey_AssumpKey AssumptionsManually copy from Non ECC source
89DCT
VariationVariationsS/4 HanaSTXLVariationVariationsManually copy from Non ECC source
90DCT
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
1



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
2S/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

3S/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 program the active decision point can only be set by changing the statuses of the preceding decision points to end state and the active decision point to start state.

The expectation is that there will be multiple records for each loaded item.

Determination of Preceding decision point

Preceding decision point determined /RPM/ITEM_PHASE-PHASE_ID for ITEM_TYPE.

Determination Decision Point Status

Decision point start status /RPM/DP_STATUS-START_STATUS = X for ITEM_TYPE and PHASE_ID
Decision point start status /RPM/DP_STATUS-END_STATUS = X for ITEM_TYPE and PHASE_ID 


Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic





S/4 Hana/RPM/DECISION ITEMItem ID





S/4 Hana/RPM/DECISIONDECISION_IDDecision Point ID

A record for each Preceding decision point and one for the active decision point.






S/4 Hana/RPM/DECISIONNAMEDecision Point Name

Decision Point Name from RPM/PHASE_T using ITEM_TYPE and DECISION_ID






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 

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

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
8Area
9Object Link
10Plant
11DFM Object Links
12Map Item Types to PS Project

Conversion Objects

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

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

Conversion Accuracy

Verify that the WBS Structure  in target were created correctly as per project template 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