Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Status

pagestatus Peer Review

Owner
Stakeholders
Purpose

The purpose of this document is to define the conversion approach to create Template Project in S/4 HANA. .

As per SyWay design, Template projects are standardized reusable Project structures used for creating operational Project and/or WBS quickly and consistently in S/4 Hana.  

Syensqo design: Templates Projects consists of both a Project definition and/or WBS elements. In Syway, these Templates element hierarchy structure. These templates are created as Operative Projects Project templates starting with letter T, these are not the STANDARD Projects and Standard WBS elements. Once created, the template project status is locked.

Conversion Scope

The scope of this document covers the approach for uploading Template Project into S/4HANA following the Template Project Master Data Design Standard. 


Scope include:

There will be 2 types of Template There will be 2 types of Template Project Definitions

  1. Template Project definition assigned to PPM Item types - Used to create Project structure automatically from PPM item.
  2. Template Project Definition which are not assigned to PPM item types - Used to create sub-hierarchy of WBS on an existing project rather than creating wbs WBS element individually.

Project Templates can will be created for any all of the below mentioned project profiles. 

ZPS0001

CAPITAL

Capital/ Operational Expense

ZPS0002

Operational Expense

ZPS0003

Statistical Expense

ZPS0004

Intercompany Recharges

ZPS0005

Provisional Expense

ZPS0005 

 Provisional Projects

Applicable Project code as per design for project template:

Project ID

Description

A

Coding Mask

for Capital Projects

T

E

Coding Mask for Internal/ Operational Projects

R

Coding Mask for R&I Projects

Description

T

-000000-00-00-XX-XX-XX

Coding Mask for Project Templates

Conversion Scope

The scope of this document covers the approach for converting active Template Project from Legacy Source Systems into S/4HANA following the Template Project Master Data Design Standard.

The scope of this document covers the approach for converting active Project Definition from Legacy Source Systems into S/4HANA following the Master Data Design Standard for Template Projects.

Scope include:

  • Project definitions and wbs elements to be assigned to PPM item types
  • Template Project Definition which are not assigned to item types - Used to create sub-hierarchy of WBS on an existing project rather than creating wbs element individually

 The data from legacy system includes:

All the projects below will be migrated from legacy source systems (PF2 and WP2) into S/4HANA –

  1. ??? Template projects

The data from legacy system excludes:

Templates linked to excluded controlling areas, company codes, plants


Once the template project upload is done in S/4 HANA, template project should be locked.

Template Project Definition status as locked.

  1. Table PROJ - Object number of template Project definition
  2. Table JEST - Field "Object number" = Key in the object numbers of template Project definition from PROJ.
  3. Table JEST - Filter object number that do have status = I0065-Master data locked
  4. Table TJ02 - Status number from JEST table to TJ02 table provides description for system statuses.

Template WBS element status as locked

  1. Table PRPS - Object numbers of template WBS 
  2. Table JEST - Field "Object number" = Key in the object numbers of WBS from PRPS.
  3. Table JEST - Filter object number that do have status = I0043-Locked.
  4. Table TJ02 - Status number from JEST table to TJ02 table provides description for system statuses.                  

   The data from legacy system includes:

         Not applicable, Source of data is DCT.

List of source systems and approximate number of records

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

DCT

Project DefinitionPF2 and WP2
S/4HANA15

DCT

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements

WBS element
S/4HANA

Migration load to be done to ROW instance with replication to other S/4 Hana instance via interface (API) to the China instance  To be included in cut-over strategy document.

Additional Information

Multi-language Requirement

Project Definition / WBS description will be made available in English. 

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not ApplicableN/A

Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
PROJPSPIDPS_PSPIDProject definitionCHAR24Mandatory
PROJPOST1PS_POST1PS: Short descriptionCHAR40Mandatory
PROJSTSPRPS_STSPRWBS status profileCHAR8MandatorySystem Generated
PROJVBUKRPS_VBUKRCompany codeCHAR4Mandatory
PROJVKOKRPS_VKOKRControlling area Area for the projectCHAR4MandatorySystem Generated
PROJPWHIEPS_PWHIEWBS  WBS currency (project definition)CHAR5MandatorySystem Generated
PROJPLFAZPS_PLFAZ_CHGProject planned start dateDATS8Mandatory

Default as 

01.01.2000 

PROJVGPLFPS_VGPLFPlanning method for project basic datesNUMC1MandatorySystem Generated
PROJEWPLFPS_EWPLFPlanning method for project forecast datesNUMC1MandatorySystem Generated
PROJPROFLPROFIDPROJProject ProfileCHAR7MandatorySystem Generated
PROJBPROFBP_BPROFILBudget ProfileCHAR6MandatorySystem Generated
PROJBESTAPS_BESTANDProject StockCHAR1MandatorySystem Generated
PROJSCOPESCOPE_CVObject ClassMandatoryPROJXSTATPS_XSTATStatistical WBS elementCHAR12ConditionalSystem Generated
PROJSCPRFPS_SCHDPRFProfile for WBS schedulingCHAR12MandatorySystem Generated
PROJPPROFPLINTBP_PPROFILPlanning ProfileCHAR6MandatoryPLINTIndicator PROJPLINTPLINTIndicator for Integrated PlanningCHAR1MandatorySystem Generated
PROJSCHTYPPS_SCHED_TYPEScheduling scenarioCHAR1MandatorySystem Generated
PROJFUNC_AREAFKBERFunctional AreaCHAR16MandatoryConditional
PRPSPOSIDPS_POSIDWBS element IDCHAR24Mandatory
PRPSPOST1PS_POST1PS: Short descriptionCHAR40Mandatory
PRPSPBUKRPS_PBUKR
Company code for WBS elementCHAR4Mandatory
PRPSPKOKRPS_PKOKRControlling areaAreaCHAR4MandatorySystem Generated
PRPSPRARTPS_PRARTProject TypeCHAR2MandatoryPRPSPLAKZPS_PLAKZPlanning elementCHAR1Conditional
PRPSBELKZPS_BELKZAccount assignment elementCHAR1ConditionalPRPSFAKKZPS_FAKKZBilling elementCHAR1Conditional
PRPSPWPOSPS_PWPOSCurrencycurrencyCHAR5MandatorySystem Generated
PRPSSCOPESCOPE_CVObject ClassCHAR2MandatoryPRPSXSTATPS_XSTATStatistical WBS elementCHAR1ConditionalSystem Generated
PRPSIMPRFPSIM_ZSCHMPROFIInvestment ProfileCHAR7Conditional
PRPSEEINHPS_EEINHUnit of measureCHAR3MandatorySystem Generated
PRPSFUNC_AREAFKBERFunctional AreaCHAR16MandatoryConditional
PRPSPSPHIPSPIDCurrent number for projectCHAR24MandatorySystem generated
PRPSSTUFEPS_STUFESTUFPS_PBUKRELevel in Project HierarchyIN13MandatorySystem generated
PRPSPRHILEFTPS_POSIDPHILEWBS_LEFTCHAR24MandatorySystem generated
PRPSPRHIUPPS_POSIDPHIUPWBS_UPCHAR24MandatorySystem generated
PRPSZX01SYCAP_OPX
CAPEX/ OPEX CHAR10MandatoryConditional


Data Cleansing

Data cleansing not applicable, as data object Project Template data (Project Definition and WBS) will be collected specifically for data migration. 

Collection will be done manually in the Data Collection Template.

IDCriticalityError MessageIDCriticalityError Message/Report DescriptionRuleOutputSource System


Not Applicable



Conversion Process

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

Image Added

Data Privacy and Sensitivity

N/ANot Applicable.


Extraction

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

The data

exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
  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.
  • 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 to identify the records that are applicable for the Target loads

    Extraction Run Sheet

    Req #Requirement DescriptionTeam Responsible

    Selection Screen

    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

    Extraction Run Sheet

    Req #Requirement DescriptionTeam Responsible
    1Ensure DCT is collected for Project Template (Project Definition / WBS elements)Data Team
    2Perform preliminary completeness check, data quality 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

    Selection Screen

    Not Applicable
    Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
    Data
    Not Applicable



    Data Collection Template (DCT)

    Target Ready Data Collection Template will be created for Template Project data with exception of some fields which require transformation as mentioned in the transformation rule.

    Template Project DCT Rules

    Field NameField DescriptionRule
    Project Level (Table - PROJ)
    PROJ_
    PSPIDProject definition

    Unique Identifier

    for the Project template,

    manually generated via coding mask starting with "T-000000".

    T = Single digit project coding key followed by separator '-' and six digit numeric character 000000.

    PROJ_
    POST1PS: Short description

    Template

    name

    description  (Name) entered manually.

    PROJ_
    VBUKRCompany code

    Represents legal entity.

    Refer configuration table field T001-BURKS for data validation.

    The project template will have the default company code 1000.

    PROJ

    _

    -VBUKR = 1000

    PROFLProject Profile

    The profiles contain default values and control parameters for processing objects and functions in the Project System.


     This field is

    Project profile is maintained on the

    templates.
     The templates mapped to PPM item are assigned to project profile ZPS0001 and ZPS0002
     Other templates will be assigned the project profiles ZPS0003, ZPS0004, ZPS0005.
    Project template "Detailed Engineering and construction" is not mapped to a PPM item but is assigned to project profile ZPS0001 .PROJ_XSTATStatistical WBS elementIndicator to specify whether a WBS element is only for statistical purposes or whether it may carry actual costs. Mandatory for Statistical Projects with Project profile ZPS0003. Derived from the profile ZPS0003.PROJ_FUNC_AREAFunctional AreaThe Functional Area allows classification of project-related costs by function.
     Defined on the project template, and WBS elements will inherit the value.
     For project templates linked to Item Types Z001, Z002 & Z003 the Functional Area will be "IS".
     For project templates linked to Item Types Z004, Z005, Z006 & Z007 the Functional Area will be "R&I".
     For project templates linked to Item Types Z008 & Z009 the Functional Area will be "IT"
     WBS LevelPOSIDWBS element IDUnique Identifier for the WBS Element template as per project coding mask. Starts with "T"POST1PS: Short description (1st text line)40 character description of the WBSE templatePBUKRCompany code for WBS elementRepresents legal entity and inherited from the Project Definition. Refer configuration table field T001-BURKS for data validation.
     The project template will have the default company code 1000.PRARTProject TypeIt is an attribute that serve as classification field that help to define the nature, purpose, and governance of a WBS element. They are useful for reporting, controlling, and compliance alignment.
     Refer configuration table field TCJ1-PRART for allowed values. Project Type will be mainatined as per rules defined in AppendixBELKZAccount assignment elementThis indicator enables financial posting on the WBS element. It will be checked in below conditions:
     1. Template WBS elements linked to  DP of Item types Z001- Z009 will have AA Blank on L1 and L2 WBS
    2. Template WBS elements for linked to DP of Item types Z010, Z012, Z013, Z014 will have  AA active on L2 WBS
    3. Template not linked to Item type but Project Profile = ZPS0001 will only have AA Active from L3 and beyond
    4. Templates not linked to item type but project Prfoile = ZPS0003, ZPS0004, ZPS0005 will have AA active on all levelsIMPRFInvestment ProfileInvestment Profile on WBS element is used to enable auto generation of AuC w.r.t. predefined asset class.
    Applicable to only those Templates that are not linked to Item type but Belonging to Project profiles = ZPS0001.
    Mandatory on Template WBS where Level = 3 and Capex/OPex indicator = Capex. Refer to Appendix. FUNC_AREAFunctional Area For template WBS  linked to Item Types Z001, Z002 & Z003 the Functional Area will be "IS".
     For template WBS linked to Item Types Z004, Z005, Z006 & Z007 the Functional Area will be "R&I".
     For template WBS linked to Item Types Z008 & Z009 the Functional Area will be "IT"For WBS elements governed by project profiles ZPS0004 & ZPS0005, this field will be maintained manually or derived from Responsible Cost Center.PSPHICurrent number for projectProject ID assigned to the WBS elements in the project template.STUFELevel in Project HierarchyLevel of the WBS element within the template. LEFTWBS_LEFTThis field represents the left-adjacent WBS element in the same hierarchy level required for navigating sibling relationships within a WBS hierarchy.UPWBS_UPThis field represents the immediate superior WBS element (parent node) required for establishing parent-child relationships in the WBS hierarchy.ZX01CAPEX/ OPEX IndicatorThis field identifies expense is CAPEX or OPEX.
     It is maintained on the project template's WBS elements.
    - For project profile ZPS0001 this field will not be maintained on project template.
    - For project profiles ZPS0002 & ZPS0003 this field will be set to OPEX on the project template.

    Extraction Dependencies

    Item #Step DescriptionTeam Responsible

    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

    Transformation Rules

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

    Transformation Mapping

    Mapping Table NameMapping Table Description

    Transformation Dependencies

    List the steps that need to occur before transformation can commenceItem #Step DescriptionTeam Responsible

    Pre-Load Validation

    Project Team

    Completeness

    TaskAction

    Accuracy

    TaskAction

    Business

    Completeness

    TaskAction

    Accuracy

    TaskAction

    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

    Load Phase and Dependencies

    Configuration

    Item #Configuration Item

    Conversion Objects

    Object #Preceding Object Conversion Approachlist the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

    template project.

    Rule applicable as below:

    Rule 1: 

    Project profile =PROJ- PROFL=ZPS0001 - CAPITAL/ Operational Expense

    Template name (PROJ_POST1)Project Type (PRPS-PRART)
    Industrial Project with Qualification17 Industrial Projects
    Industrial Project17 Industrial Projects
    Industrial Project - Simple17 Industrial Projects
    New Product IntroductionNew Product Introduction
    New Product IntroductionProduct & Process Improvement
    Customer and business supportCustomer and business support
    OPD Opportunity DevelopmentOPD Opportunity Development
    IT Full Lifecycle Project18 IT Project
    IT Small Project18 IT Project
    Opex project34 Operational Expense
    Turnaround Projects19 Turnaround Projects
    Direct Asset Purchase11 Direct Asset Purchase
    Capitalised Maintenance29 Budgeted Maintenance
    Capitalised Lease16 Capital Lease
    Detailed Engineering and construction Templates 17  Industrial Projects

    Rule 2:

    Project profile =PROJ- PROFL=ZPS0002 - Operational Expense

    Template name (PROJ_POST1)Project Type (PRPS-PRART)
    OPD Opportunity DevelopmentOPD Opportunity Development
    Opex project34 Operational Expense

    Rule 3 Project profile =PROJ- PROFL = ZPS0005 - Provisional Projects

    Template name (PROJ_POST1)Project Type (PRPS-PRART)
    Safety and Environment Provision13 Safety and Environment Provision

    IAS19 Provision14 IAS19 Provision
    Restructuring Provision12 Restructuring Provision
    Environmental Fines22 Environmental Fines
    Social Fines23 Social Fines
    Corruption Fines24 Corruption Fines
    FUNC_AREAFunctional Area

    The Functional Area allows classification of project-related costs by function. 


    Template name (PROJ_POST1)

    Project Profile

    PROJ- PROFL

    Project Type

    Project Type (PRPS-PRART)

    Functional Area

    PROJ-FUNC_AREA

    Industrial Project with QualificationZPS0001 - CAPITAL/ Operational Expense17 Industrial ProjectsIS
    Industrial ProjectZPS0001 - CAPITAL/ Operational Expense17 Industrial ProjectsIS
    Industrial Project - SimpleZPS0001 - CAPITAL/ Operational Expense17 Industrial ProjectsIS
    New Product IntroductionZPS0001 - CAPITAL/ Operational ExpenseNew Product IntroductionR&I
    New Product IntroductionZPS0001 - CAPITAL/ Operational ExpenseProduct & Process ImprovementR&I
    Customer and business supportZPS0001 - CAPITAL/ Operational ExpenseCustomer and business supportR&I
    New Application introductionZPS0001 - CAPITAL/ Operational ExpenseNew Application DevelopmentR&I
    OPD Opportunity DevelopmentZPS0002 - Operational ExpenseOPD Opportunity DevelopmentR&I
    IT Full Lifecycle ProjectZPS0001 - CAPITAL/ Operational Expense18 IT Project

    IT

    IT Small ProjectZPS0001 - CAPITAL/ Operational Expense18 IT Project

    IT





    Template WBS (Table - PRPS
    POSIDWBS element ID

    Unique Identifier for the WBS Element template as per project coding mask starts with "T".

    Project definition key = Project WBS key, T = Single digit key 

    POST1PS: Short description (1st text line)

    40 character description of the template WBS element. 

    PBUKRCompany code for WBS elementRepresents legal entity and inherited from the Project Definition. Refer configuration table field T001-BURKS for data validation.
    PRARTProject Type

    It is an attribute that serve as classification field that help to define the nature, purpose, and governance of a WBS element. 
    Refer configuration table field TCJ1-PRART for allowed values.

    Project type in-line with the Project profile as mentioned above PROJ-PROFL

    BELKZAccount assignment element

    This indicator enables financial posting on the WBS element. It will be checked in below conditions:

    Applicable rule:

    Template name (PROJ_POST1)

    Project Profile

    PROJ- PROFL

    Project Type

    Project Type (PRPS-PRART)

    Lvl 1 WBS 

    PRPS-STUFE=1

    Acc Assignment = BELKZ

    Lvl 2 WBS 

    PRPS-STUFE=2

    Acc Assignment = BELKZ

    Lvl 3 WBS 

    PRPS-STUFE=3

    Acc Assignment = BELKZ

    Lvl 4 WBS 

    PRPS-STUFE=4

    Acc Assignment = BELKZ

    Below template Projects required mapping to PPM item type config
    Industrial Project with QualificationZPS0001 - CAPITAL/ Operational Expense17 Industrial ProjectsBlankBlankNot applicableNot applicable
    Industrial ProjectZPS0001 - CAPITAL/ Operational Expense17 Industrial ProjectsBlankBlankNot applicableNot applicable
    Industrial Project - SimpleZPS0001 - CAPITAL/ Operational Expense17 Industrial ProjectsBlankBlankNot applicableNot applicable
    New Product IntroductionZPS0001 - CAPITAL/ Operational ExpenseNew Product IntroductionBlankBlankNot applicableNot applicable
    New Product IntroductionZPS0001 - CAPITAL/ Operational ExpenseProduct & Process ImprovementBlankBlankNot applicableNot applicable
    Customer and business supportZPS0001 - CAPITAL/ Operational ExpenseCustomer and business supportBlankActiveNot applicableNot applicable
    OPD Opportunity DevelopmentZPS0002 - Operational ExpenseOPD Opportunity DevelopmentBlankActiveNot applicableNot applicable
    IT Full Lifecycle ProjectZPS0001 - CAPITAL/ Operational Expense18 IT ProjectBlankBlankNot applicableNot applicable
    IT Small ProjectZPS0001 - CAPITAL/ Operational Expense18 IT ProjectBlankBlankNot applicableNot applicable
    Opex projectZPS0002 - Operational Expense34 Operational ExpenseBlankActiveNot applicableNot applicable
    Turnaround ProjectsZPS0001 - CAPITAL/ Operational Expense19 Turnaround ProjectsBlankBlankNot applicableNot applicable
    Direct Asset PurchaseZPS0001 - CAPITAL/ Operational Expense11 Direct Asset PurchaseBlankActiveNot applicableNot applicable
    Capitalised MaintenanceZPS0001 - CAPITAL/ Operational Expense29 Budgeted MaintenanceBlankBlankNot applicableNot applicable
    Capitalised LeaseZPS0001 - CAPITAL/ Operational Expense16 Capital LeaseBlankActiveNot applicableNot applicable
    New Application introductionZPS0001 - CAPITAL/ Operational ExpenseNew Application DevelopmentBlankBlankNot applicableNot applicable
    Below template Projects are standalone projects with no mapping to PPM item type config
    Detailed Engineering and construction Templates ZPS0001 - CAPITAL/ Operational Expense17  Industrial ProjectsBlankBlank

    Active 

    Mandatory

    Investment profile PRPS-IMPRF = Not blank

    Active 

    Mandatory

    Investment profile PRPS-IMPRF = Blank

    Safety and Environment ProvisionZPS0005 - Provisional ProjectsSafety and Environment Provision

    BlankActive

    Not applicable

    Not applicable

    IAS19 ProvisionZPS0005 - Provisional ProjectsIAS19 ProvisionBlankActiveNot applicableNot applicable
    Restructuring ProvisionZPS0005 - Provisional ProjectsRestructuring ProvisionBlankActiveNot applicableNot applicable
    Environmental FinesZPS0005 - Provisional ProjectsEnvironmental FinesBlankActiveNot applicableNot applicable
    Social FinesZPS0005 - Provisional ProjectsSocial FinesBlankActiveNot applicableNot applicable
    Corruption FinesZPS0005 - Provisional ProjectsCorruption FinesBlankActiveNot applicableNot applicable


    IMPRFInvestment Profile

    Investment Profile on WBS element is used to enable auto generation of AUC w.r.t. predefined asset class.

    Template project PROJ_POST1 = 'Detailed Engineering and construction'  with project profile PROJ-PROFL = ZPS0001, project type PRPS-PRART = 17  Industrial Projects, investment profile is mandatory on template WBS for level  PRSP-STUFE = 3 where indicator  PRPS-ZX01, Capex/Opex = Capex, PRPS-IMPRF = mandatory

    FUNC_AREAFunctional Area

    The value of this field will be inherited from the project definition template.

    It should not be changed at the WBS element level i.e PROJ-FUNC_AREA = PRPS-FUNC_AREA 

    PSPHICurrent number for projectProject ID assigned to the WBS elements in the project template
    STUFELevel in Project Hierarchy
    1. Template project WBS relevant for PPM item type, project profile = ZPS0001 - CAPITAL/ Operational Expense, ZPS0002 - Operational Expense, WBS level 1 PRPS-STUFE=1 & Level 2 PRPS-STUFE=2 are applicable. WBS level PRPS-STUFE = 3, 4, 5 are not applicable
      1. Level 1 represent project template definition
      2. Level 2 represent phase/stage

    2. Template project WBS not relevant for PPM item type,

         a. Template Project, ‘Detailed Engineering and construction Template’, project profile = ZPS0001 - CAPITAL/ Operational Expense, WBS level 1 PRPS-STUFE=1, Level 2 PRPS-STUFE=2, Level 3 PRPS-STUFE= 3, Level 4 PRPS-STUFE= 4 are applicable.

              Level 1 represent project template definition

              Level 2 WBS, with account assignment not allowed

              Level 3 represent Asset Category or Expense Category

              Level 4 represent Cost Collector

         b. Template projects Safety and Environment Provision, IAS19 Provision, Restructuring Provision, Environmental Fines, Social Fines, Corruption Fines with project profile ZPS0005 -  Provisional Projects, WBS level 1 PRPS-STUFE=1 & Level 2 PRPS-STUFE=2 applicable. WBS level PRPS-STUFE = 3, 4, 5  not applicable.

              Level 1 represent project template definition with account assignment not allowed

              Level 2 WBS, with account assignment allowed


    LEFTWBS_LEFT

    This field represents the left-adjacent WBS element in the same hierarchy level required for navigating sibling relationships within a WBS hierarchy.

    PRHI-LEFT

    UPWBS_UP

    This field represents the immediate superior WBS element (parent node) required for establishing parent-child relationships in the WBS hierarchy.

    PRHI-RIGHT

    SYCAP_OPXCAPEX/ OPEX

    This field identifies expense is CAPEX or OPEX.
     It is maintained on the project template's WBS elements.
    - For project profile ZPS0001 this field will not be maintained on project template WBS. 

      For PRPS-PSPHI in table PROJ-PROFL = ZPS0001, PRPS-PRPS-SYCAP_OPX = blank

    -For project profiles ZPS0002 this field will be set to OPEX on the project template WBS.

      For PRPS-PSPHI in table PROJ,  PROJ-PROFL = ZPS0001, PRPS-PRPS-SYCAP_OPX = not blank

    Appendix: Post template upload, Template projects are mapped to item types through customizing settings for SAP Portfolio and Project Management (PPM) (config table /RPM/V_PSITPT). as per the config rationale. 

    Template namePPM Item TypePS Project ProfilePS Project TypeRule for L1 WBSERule for L2 WBSERule for L3 WBSERule for L4 WBSE
    Industrial Project with QualificationZ001 Industrial Project with QualificationZPS0001 - CAPITAL/ Operational Expense17 Industrial ProjectsRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment not allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Industrial ProjectZ002 Industrial ProjectZPS0001 - CAPITAL/ Operational Expense17 Industrial ProjectsRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment not allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Industrial Project - SimpleZ003 Industrial Project - Simple ?ZPS0001 - CAPITAL/ Operational Expense17 Industrial ProjectsRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment not allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    New Product IntroductionZ004 New Product IntroductionZPS0001 - CAPITAL/ Operational ExpenseNew Product IntroductionRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment not allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    New Product IntroductionZ005 Product & Process ImprovementZPS0001 - CAPITAL/ Operational ExpenseProduct & Process ImprovementRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment not allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Customer and business supportZ006 Customer and business supportZPS0001 - CAPITAL/ Operational ExpenseCustomer and business supportRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    OPD Opportunity DevelopmentZ007 OPD Opportunity DevelopmentZPS0002 - Operational ExpenseOPD Opportunity DevelopmentRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    IT Full Lifecycle ProjectZ008 IT Full Lifecycle ProjectZPS0001 - CAPITAL/ Operational Expense18 IT ProjectRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment not allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    IT Small ProjectZ009 IT Small ProjectZPS0001 - CAPITAL/ Operational Expense18 IT ProjectRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Opex projectZ010 Opex ProjectZPS0002 - Operational Expense34 Operational ExpenseRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Turnaround ProjectsZ011 Turnaround ProjectsZPS0001 - CAPITAL/ Operational Expense19 Turnaround ProjectsRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment not allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Direct Asset PurchaseZ012 Direct Asset PurchaseZPS0001 - CAPITAL/ Operational Expense11 Direct Asset PurchaseRepresent project template definition
    A/C assignment not allowed
    Represent Cost Collector WBS
     Mapped to a PPM decision point.
     A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Capitalised MaintenanceZ013 Capitalised MaintenanceZPS0001 - CAPITAL/ Operational Expense29 Budgeted MaintenanceRepresent project template definition
     A/C assignment not allowed
    Represent phase/stage.
     Mapped to a PPM decision point.
     A/C assignment Not  allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Capitalised LeaseZ014 Capital LeaseZPS0001 - CAPITAL/ Operational Expense16 Capital LeaseRepresent project template definition
     A/C assignment not allowed
    Represent Cost Collector WBS
     Mapped to a PPM decision point.
     A/C assignment allowed
    Statistical Indicator Active
    N/A - no L3 in this templateN/A - no L4 in this template
    Detailed Engineering and construction TemplatesN/AZPS0001 - CAPITAL/ Operational Expense17  Industrial ProjectsRepresent project template definition
     A/C assignment not allowed
    Level 2 WBS only 
    A/c Assignment not allowed
    Represent Asset Category or Expense Category. 
    A/c assignment is  mandatory
    Investment profile can be added for capex WBS only
    Represent Cost Collector 
    A/c assignment is mandatory.
    Investment Profile not allowed
    Safety and Environment ProvisionN/AZPS0005 - Provisional ProjectsSafety and Environment Provision

    Represent project template definition
     A/C assignment not allowed
    Settlement rule to GL Account
    A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template
     IAS19 ProvisionN/AZPS0005 - Provisional ProjectsIAS19 ProvisionRepresent project template definition
     A/C assignment not allowed
    Settlement rule to GL Account
    A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Restructuring ProvisionN/AZPS0005 - Provisional ProjectsRestructuring ProvisionRepresent project template definition
     A/C assignment not allowed
    Settlement rule to GL Account
    A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    New Application introductionZ017 New Application DevelopmentZPS0001 - CAPITAL/ Operational ExpenseNew Application DevelopmentRepresent project template definition
    A/C assignment not allowed
    Represent phase/stage.
    Mapped to a PPM decision point.
    A/C assignment not allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Environmental FinesN/AZPS0005 - Provisional ProjectsEnvironmental FinesRepresent project template definition
    A/C assignment not allowed
    Settlement rule to GL Account
    A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Social FinesN/AZPS0005 - Provisional ProjectsSocial FinesRepresent project template definition
    A/C assignment not allowed
    Settlement rule to GL Account
    A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template
    Corruption FinesN/AZPS0005 - Provisional ProjectsCorruption FinesRepresent project template definition
    A/C assignment not allowed
    Settlement rule to GL Account
    A/C assignment allowed
    N/A - no L3 in this templateN/A - no L4 in this template


    Note: Upfront Automated Fields are not included in DCT as SAP validates these fields upon entry.

    Extraction Dependencies

    No Dependencies for Extract

    Item #Step DescriptionTeam Responsible

    NA


    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
    8Re-transform and re-validate the Pre-load reports if necessary.Data team
    9Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.Business
    10Analyze and resolve any pre-load defects logged by business.Data team
    11Repeat steps 7 to 10 if necessaryData team
    12Proceed to pre-load validationsData team


    Transformation Rules

    Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
    Template Project definition
    1DCT
    PROJ_PSPIDProject definitionS/4 HanaPROJPSPIDProject definitionCopy from source to target system
    2DCT
    PROJ_POST1PS: Short descriptionS/4 HanaPROJPOST1PS: Short descriptionCopy from source to target system
    3DCT
    PROJ_VBUKRCompany CodeS/4 HanaPROJVBUKRCompany code

    Copy from source to target

    4



    S/4 HanaPROJVKOKRControlling Area

    Derived from Project profile

    Default to CO01

    5



    S/4 HanaPROJPWHIEProject CurrencyValue Mapping: Currency From Company Code
    Company Code Currency from T001-WAERS where BUKRS = PBUKR
    6DCT
    PROJ_PROFLProject ProfileS/4 HanaPROJPROFLProject ProfileCopy from Source
    7DCT
    PLFAZProject planned start dateS/4 HanaPROJPLFAZProject planned start dateCopy from source to target system
    8



    S/4 HanaPROJBPROFBudget ProfileDerived from Project profile
    9



    S/4 HanaPROJBESTAProject StockDefault to No
    10



    S/4 HanaPROJSCOPEObject ClassDerived from Project profile
    11



    S/4 HanaPROJSCPRFProfile for WBS schedulingDerived from Project profile
    12



    S/4 HanaPROJPPROFPlanning ProfileDerived from Project profile
    13



    S/4 HanaPROJPLINTIndicator for Integrated PlanningDerived from Project profile
    14



    S/4 HanaPROJSCHTYPScheduling scenarioDerived from Project profile
    15DCT
    PROJ_FUNC_AREAFunctional AreaS/4 HanaPROJFUNC_AREAFunctional AreaCopy from source to target system
    Template WBS 
    16DCT
    POSIDWBS element IDS/4 HanaPRPSPOSIDWBS element IDCopy from source to target system
    17DCT
    POST1PS: Short description (1st text line)S/4 HanaPRPSPOST1PS: Short description (1st text line)Copy from source to target system
    18DCT
    PBUKRCompany code for WBS elementS/4 HanaPRPSPBUKRCompany code for WBS element

    Copy from source to target system

    19DCT
    PRARTProject TypeS/4 HanaPRPSPRARTProject TypeCopy from source to target system
    20DCT
    BELKZAccount assignment elementS/4 HanaPRPSBELKZAccount assignment elementCopy from source to target system
    21



    S/4 HanaPRPSPWPOSCurrency

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

    Default to EUR

    22



    S/4 HanaPRPSSCOPEObject classDefault from Project Profile
    23DCT
    IMPRFInvestment ProfileS/4 HanaPRPSIMPRFInvestment ProfileCopy from source to target system
    24DCT
    FUNC_AREAFunctional AreaS/4 HanaPRPSFUNC_AREAFunctional AreaCopy from source to target system
    25DCT
    PSPHIProject DefinitionS/4 HanaPRPSPSPHIProject DefinitionCopy from source to target system
    26DCT
    STUFELevelS/4 HanaPRPSSTUFELevelCopy from source to target system
    27DCT
    LEFTWBS_LEFTS/4 HanaPRPSPRHI-LEFTWBS_LEFTCopy from source to target system
    28DCT
    UPWBS_UPS/4 HanaPRPSPRHI-UPWBS_UPCopy from source to target system
    29DCT
    SYCAP_OPXCAPEX/ OPEX S/4 HanaPRPSSYCAP_OPXCAPEX/ OPEXCopy from source to target system

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

    The standard upload template to be used for Project template upload in S/4 Hana.

    Standard Upload template


    Transformation Mapping


    Mapping Table NameMapping Table Description
    T001Value Mapping: Currency From Company Code

    Transformation Dependencies

    List the steps that need to occur before transformation can commence
    Item #Step DescriptionTeam Responsible

    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 Count

    SyWay I2M Data Team to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets.

    Accuracy

    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
    3. Migration load to be done to ROW instance with replication to other S/4 Hana instances via interface (API) to the China instance  To be included in cut-over strategy document.                                                        
    4. Post Template upload, lock Template Project Definition status as locked.
        1. Table PROJ - Object number of template Project definition
        2. Table JEST - Field "Object number" = Key in the object numbers of template Project definition from PROJ
        3. Table JEST - Filter object number that do have status = I0065-Master data locked
        4. Table TJ02 - Status number from JEST table to TJ02 table provides description for system statuses.

      Lock Template WBS element status as locked

      1. Table PRPS - Object numbers of template WBS 
      2. Table JEST - Field "Object number" = Key in the object numbers of WBS from PRPS.
      3. Table JEST - Filter object number that do have status = I0043-Locked.
      4. Table TJ02 - Status number from JEST table to TJ02 table provides description for system statuses

    Load Run Sheet

    Item #Step DescriptionTeam Responsible

    1

    Load using transaction CNMASSCREATE or Migration cockpit.

    SyWay I2M Data Team

    2

    Load 3 records for < > to validate if data is loaded successfully without errors

    SyWay I2M Data Team

    3

    Load 3 records for < > to validate if data is loaded successfully without errors

    SyWay I2M Data Team

    4

    Proceed with full load if steps 2 and 3 are validated

    SyWay I2M Data Team

    5

    Validate few records loaded by accessing Portfolio Bucket Structure App

    SyWay I2M Data Team

    6

    Generate post load report if step 5 is validated

    SyWay I2M Data Team

    7

    Post Template upload, run CNMASSSTATUS to update the template status to Lock

     SyWay I2M Data Team


    Load Phase and Dependencies

    Configuration


    Item #Configuration Item
    1Controlling Area 
    2Company Code 
    3Project Type
    4Factory Calendar
    5Currency Code
    6Project Profile
    7Investment Profile
    8Budget Profile
    9Planning Profile
    10Functional Area
    11Profile for WBS scheduling
    12Profile for WBS scheduling

    Conversion Objects

    Object #Preceding Object Conversion Approach

    list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

    Error Handling


    Error TypeError DescriptionAction Taken

    Project Definition already existCorrect upload data

    WBS element already existCorrect upload data


    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 Project Definition / WBS in target S/4 HANA were loaded correctly via Project Builder display and table PROJ / PRPS

    Business

    Completeness

    TaskAction
    Verify template Project data - Project Definition / WBSExtract data from PS report CN41N in S/4 Hana

    Accuracy

    TaskAction
    Verify template Project data - Project Definition / WBSExtract data from PS report CN41N in S/4 Hana


    Error Handling

    Error TypeError DescriptionAction Taken

    Post-Load Validation

    Project Team

    Completeness

    TaskAction

    Accuracy

    TaskAction

    Business

    Completeness

    TaskAction

    Accuracy

    TaskAction

    Key Assumptions

    • Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
    • Template Project is in scope based on data design and any exception requested by business.


    Note:  Jira Task: PDM-441

    See also

    Change log

    Change History
    limit10