Purpose

The purpose of this document is to define the conversion approach to create the WBS - CAPEX, OPEX, Statistical

in S/4 HANA.

In SAP, a WBS element (Work Breakdown Structure element) is a key component in project structure. WBS elements are organized hierarchically and facilitates planning, execution, and control.

Conversion Scope

The scope of this document covers the approach for converting applicable active WBS - CAPEX, OPEX, Statistical from Legacy Source Systems into S/4HANA following the WBS - CAPEX, OPEX, Statistical Master Data Design Standard.

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 to be included in the initial extract includes:

1. 1. The data from legacy system includes:

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

Additionally WBS elements without any initial extract will be created in the DCT only, this includes - 

1. WBS elements with reference to PPM item and template project- 
   1. Capital Lease (Level 2 One WBS per Company Code/Plant, with statistical active)
   2. Direct Asset Purchases (Level 2 WBS per GBU/Company Code/Plant/Cost Centre)
   3. Capitalized Spares (Level 2 WBS per GBU/Company Code/Plant/Cost Centre)
2. WBS elements with no reference to PPM items -
   1. For the Provisions (One WBS per Company code/Plant)
   2. Intercompany recharge (One Level 1 WBS per Company Code, Level 2 WBS per Trading Partner)

List of source systems and approximate number of records

Migration instance and migration group is defined by the company code of the WBS element.

Inter-company recharge WBS elements are replicated to other S/4 Hana instances by batch job as per business process. 

Additional Information

Multi-language Requirement

The WBS element name is maintained in a single language only, no translation required.

Document Management

Not required.

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

Data cleansing tasks are set out in CNV-1024 which deals with projects and also by definition includes the closing of WBS elements in those projects.

Conversion Process

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

Data Privacy and Sensitivity

Extraction

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 to identify the records that are applicable for the Target loads

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

DCT Rules

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

Extraction Dependencies

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

Transformation Rules. 

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

The following does not apply to WBS elements created directly in the DCT.

The transformation of WBS element structure from the legacy systems is changed from a multi-level structure to a formal phase based approach with adherence to pre-approved project structures across all project types.

To facilitate this only WBS elements flagged account assignment from PF2/WP2 will be created and assigned to the project structures in S/4 which has already created during PPM item creation (CNV-1022), (relevancy criteria for migration is the same), while a mapping of all WBS elements, including non-account assignment objects will be provided.   

The following is executed for WBS elements across a single project at a time.

Parent/Number/Level Determination

1. Target Structure - The project structure created in S/4 is used for this, select PSPNR from PRPS where PSPHI = Target PSPHI and STUFE = MAX of STUFE 2.   All projects which fall within the relevancy criteria has phase level structure.

1.1 If count selection = 1. (New project structure has only a single phase, for capex all FXA relevant WBS elements must be linked at this level)

1.1.1 Source AUC - From source system select all WBS elements for the project Investment Profiles 

Loop by Source AUC  WBS element assigning if count is >0

TARGET - PRHI-UP = PARENT from 1 above.

Target - PSPNR = Parent PSPNR + .01 (incrementing by .01 for each subsequent WBS element (such that first would be A.0000001.01 second A.0000001.02 and so forth)

Target - STUFE = PARENT STUFE +1.

Target - CAPEX / OPEX = CAPEX

 Lover Levels  -  For each SOURCE AUC  see if any lower level WBS elements with account assignment active in subsequent levels taking note that the relationship may be more than level lower.  This is done using PSHI where SOURCE AUC WBS element is maintained in up.  This should specifically exclude any WBS elements with Investment Profiles..

Loop by Source CHILD  WBS element assigning 

TARGET - PRPH-UP = TARGET from 1.1 above.

TARGET - PSPNR = PRPNR from 1.1.2 above + .01 (incrementing by .01 for each subsequent WBS element (such that first would be A.0000001.01.01 second A.0000001.01.02 and so forth)

TARGET - STUFE= PARENT STUFE +1.

Target - CAPEX / OPEX = OPEX

1.1.2   Source Opex - Any WBS elements which have not been assigned to the structure is now assigned to PARENT WBS from 1.1  This takes care of situations where there is no Capital settlements in the parent child relationships but where postings exist.

Loop at SOURCE OPEX WBS element - assigning 

TARGET - PRHI-UP = PARENT from 1 above.

Target - PSPNR = Parent PSPNR + .01 (increments continue )

TARGET - STUFE= PARENT STUFE +1.

Target - CAPEX / OPEX = OPEX

1.2 If count selection > 1. New project structure has multiple phases, by default all Investment Profile relevant WBS elements to be linked to the Execution phase WBS element`.

1.2.1 Source AUC - From source system select all WBS elements for the project Investment Profiles

Loop by Source AUC  WBS element assigning f count is >0

TARGET - PRHI-UP = TARGET from 1.2 above.

Target - PSPNR = Parent PSPNR + .01 (incrementing by .01 for each subsequent WBS element (such that first would be A.0000001.01 second A.0000001.02 and so forth)

Target - STUFE = PARENT STUFE +1.

Target - CAPEX / OPEX = CAPEX

 Lover Levels  -  For each SOURCE AUC  see if any lower level WBS elements with account assignment active in subsequent levels taking note that the relationship may be more than level lower.  This is done using PSHI where SOURCE AUC WBS element is maintained in up.  This should specifically exclude any WBS elements selected in 2 above directly.

Loop by Source CHILD  WBS element assigning 

TARGET - PRPH-UP = TARGET from 1.2 above.

TARGET - PSPNR = PRPNR from 2 above + .01 (incrementing by .01 for each subsequent WBS element (such that first would be A.0000001.01.01 second A.0000001.01.02 and so forth)

TARGET - STUFE= PARENT STUFE +1.

Target - CAPEX / OPEX = OPEX

1.2.2   Source Opex - Any WBS elements with account assignment active which have not been assigned to the structure is now assigned to the execution PARENT WBS from 1.2  This takes care of situations where there is no Capital settlements in the parent child relationships but where postings exist.

Loop at SOURCE OPEX wbs element - assigning 

TARGET - PRHI-UP = PARENT from 1.2 above.

Target - PSPNR = Parent PSPNR + .01 (increments continue )

TARGET - STUFE= PARENT STUFE +1.

Target - CAPEX / OPEX = OPEX

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Load Phase and Dependencies

Configuration

Conversion Objects

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

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• WBS - CAPEX, OPEX, Statistical is in scope based on data design and any exception requested by business.

See also

Change log