Project ID

Coding Mask

Description

T

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

Coding Mask for Project Templates

DCT

DCT

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

Repeat Req # 1 to 3 if required

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

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

Template description entered manually.

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

The profiles contain default values and control parameters for processing objects and functions in the Project System. Project profile is maintained on the template project.

Rule applicable as below:

Rule 1: The Template Project mapped to PPM item type are assigned to project profile ZPS0001 and ZPS0002.

Template projects are mapped to item types through customizing settings for SAP Portfolio and Project Management (PPM).  Refer config table /RPM/V_PSITPT.

Refer Appendix below for applicable PPM item type mapped with template projects and its respective allowed project profile and project type.

Refer Appendix below

Rule 2:

Project template "Detailed Engineering and construction" is not mapped to a PPM item but is assigned to project profile ZPS0001. Such project template is not mapped in config table config table /RPM/V_PSITPT.

Refer Appendix below

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

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 

40 character description of the template WBS element. 

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 will be maintained as per rules defined in Appendix below:

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

Item Type DP are mapped to PS WBS Element through customizing settings for SAP Portfolio and Project Management (PPM).  Refer config table /RPM/V_WBSDP_MAP - Item Type DP to PS WBS

Rule 1:

Item type = Z001to Z009 in /RPM/V_WBSDP_MAP, for decision point id, field DECISION_ID mapped to WBS, AA assignment element PRPS-BELKZ = blank, if PRPS-STUFE = 1 or 2

Rule 2:

Item type = Z010, Z012, Z013, Z014 in /RPM/V_WBSDP_MAP, for decision point id field DECISION_ID mapped to WBS, AA assignment element PRPS-BELKZ = active, if PRPS-STUFE = 2

Rule 3:

Template project with project profile PROJ-PROFL = ZPS0001, mapping does not exist in /RPM/V_PSITPT, and WBS PRPS-STUFE = 3 and beyond, AA assignment element PRPS-BELKZ = active

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

Template project with project profile PROJ-PROFL = ZPS0001 and mapping does not exist in config table /RPM/V_PSITPT, investment profile is mandatory on template WBS for level  PRSP-STUFE = 3 and Capex/Opex = Capex, PRPS-IMPRF = mandatory

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 

Level of the WBS element within the template. 

Level 1 WBS element represent project i.e T-000000 same as project definition number
Level 2 WBS element represent project phase T-000000-00
Level 3 WBS represents the Asset category ( Investment profile/AUC class) OR Expense category for cost controlling and settlements to CCs/PSG -000000-00-00-XX
Level 4 (Optional) WBS represents the subdivision of the Assets being build/constructed for cost controlling and settlements to FXA or for work order OR WBS represent the subdivision of the expenses incurred for cost controlling assignments -000000-00-00-XX-XX

Level 5 (Optional)  -000000-00-00-XX-XX-XX

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

PRHI-LEFT

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

PRHI-RIGHT

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. 

  Table: PRPS, check PRPS-PSPHI. For PRPS-PSPHI in table PROJ-PROFL = ZPS0001, PRPS-      ZX01 = 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-ZX01 = not blank

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

Copy from source to target

Derived from Project profile

Copy from source to target system

Ensure all the fields that require value mapping, as stipulated.

Mapping tables, have the correct values mapped and imported into tool.

Data Team 

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.

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.

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.

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

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

Map Item Type to Project or PS or Commercial Project (Post template upload required config)

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

Conversion Accuracy

Verify that the Project Definition / WBS in target S/4 HANA were loaded correctly via Project Builder display and table PROJ / PRPS