| Status | Revision under Review |
|---|---|
| Owner | |
| Stakeholders |
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 active WBS - CAPEX, OPEX, Statistical from Legacy Source Systems into S/4HANA following the WBS - CAPEX, OPEX, Statistical Master Data Design Standard.
Due to the complexity of the changes required to the existing WBS structures all data will be built in a DCT.
An initial extract of the relevant WBS master data, including suggested mapping to new structures, will be provided in google sheet format to assist business in decision making on including any relevant WBS element from PF2 and WP2.
The data from legacy system to be included in the initial extract includes:
- WBS elements for Capital projects (eg. Industrial, Facility IT and R&I) open as at migration date with postings in the last 3 years or has AUC balance.
- WBS elements for Budgeted Operating projects (eg. Budgeted Maintenance, Demolition projects) open as at migration date with postings in the last 3 years.
- WBS elements for Closed Capital Projects with postings within the agreed timeframe (currently migration relevant is 2028).
- WBS elements for Closed Budgeted Operating Projects with postings within the agreed timeframe (currently migration relevant is 2028).
- Specifically also included are WBS elements for IT and R&I Projects with postings in the last 3 years.
The data from legacy system be included in the initial extract excludes:
- WBS elements for company codes out of scope
- WBS for out of scope Plants.
- WBS with no costs (no movement in past 3 years), Project created by mistake
- WBS which has deletion indicator set
Additionally WBS elements without any initial extract will be created using the DCT, this includes -
- WBS elements with reference to PPM item and template project-
- Capital Lease (Level 2 One WBS per Company Code/Plant, with statistical active)
- Direct Asset Purchases (Level 2 WBS per GBU/Company Code/Plant/Cost Centre)
- Capitalized Spares (Level 2 WBS per GBU/Company Code/Plant/Cost Centre)
- WBS elements with no reference to PPM items -
- For the Provisions (One WBS per Company code/Plant),
- Intercompany recharge (One Level 1 WBS per Company Code, Level 2 WBS per Trading Partner)
WBS elements can be referenced in transactional data conversions, this may result in additional WBS elements may be required to be added to the DCT, transactional data which may require additional WBS elements are
- Financial postings
- CNV-9031 Project - Actual GL Line Items (PNL - WBS for AuC)
- CNV-9032 GL Line Items (PNL - Internal Order, Statistical/ Opex WBS)
- Maintenance processing
- CNV-9005 Work Order
- Procurement
- CNV-9045 Open Purchase Orders
Predecessor Objects
CNV-1024 Project Definition
List of source systems and approximate number of records
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | S/4 Hana | |||
| WP2 | S/4 Hana | |||
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.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PRPS | POSID | PS_POSID | WBS element | CHAR | 24 | Mandatory |
| PRPS | PS_POSNR | PS_POSNR | WBS Element internal number | CHAR | 8 | System Generated |
| PRPS | OBJNR | J_OBJNR | Object Number | CHAR | 8 | System Generated |
| PRPS | POST1 | PS_POST1 | Description | CHAR | 40 | Mandatory |
| PRPS | VERNR | PS_VERNR | No. of Person Resp. | NUMC | 8 | Mandatory |
| PRPS | ASTNR | PS_ASTNR | Applicant no. | NUMC | 8 | Mandatory |
| PRPS | PBUKR | PS_PBUKR | Company code | CHAR | 4 | Mandatory Only 1 Company Code allowed per PSPHI |
| PRPS | PKOKR | PS_PKOKR | Controlling area | CHAR | 4 | Mandatory |
| PRPS | PRCTR | PRCTR | Profit Center | CHAR | 10 | Mandatory Only 1 Company Code allowed per PSPHI |
| PRPS | PRART | PS_PRART | Project Type | CHAR | 2 | Mandatory |
| PRPS | PLAKZ | PS_PLAKZ | Planning Element | CHAR | 1 | System Generated |
| PRPS | BELKZ | PS_BELKZ | Acct asst elem. | CHAR | 1 | Mandatory |
| PRPS | FAKKZ | PS_FAKKZ | Billing Element | CHAR | 1 | Conditional Only relevant when For project profile maintained in PSPHI is ZPS0005 |
| PRPS | FKSTL | PS_FKSTL | Responsible CC | CHAR | 10 | Mandatory |
| PRPS | FKOKR | PS_FKOKR | CA resp. cost center | CHAR | 4 | Mandatory |
| PRPS | FABKL | FABKL | Factory Calendar | CHAR | 2 | Mandatory |
| PRPS | PWPOS | PS_PWPOS | Currency | CUKY | 5 | Mandatory |
| PRPS | WERKS | WERKS_D | Plant | CHAR | 4 | Mandatory Only 1 Company Code allowed per PSPHI |
| PRPS | SCOPE | SCOPE_CV | Object class | CHAR | 2 | System Generated |
| PRPS | XSTAT | PS_XSTAT | Statistical | CHAR | 1 | Conditional Only relevant for Project profile ZPS0003 |
| PRPS | KOSTL | PS_KOSTL | CCtr posted actual | CHAR | 10 | Conditional This field will be mandatory for all statistical WBS element (XSTAT = X) |
| PRPS | IMPRF | IM_PROFIL | Investment Profile | CHAR | 6 | Conditional Required for CAPEX projects (with Project Profile ZPS0001) at Level 3 WBS elements if the CAPEX field is selected (STUFE=3). |
| PRPS | FUNC_AREA | FKBER | Functional Area | CHAR | 16 | Mandatory |
| PRPS | PSPHI | PS_PSPID | Project Definition | CHAR | 24 | Mandatory |
| PRPS | STUFE | PS_STUFE | Level | CHAR | 3 | Mandatory |
| PRHI | UP | PS_PHIUP | WBS_UP | NUMC | 8 | Conditional Required if (STUFE>1). Can only be a WBS element with the same PSPHI. |
| PRHI | LEFT | PS_PHILE | WBS_LEFT | NUMC | 8 | Conditional |
| PRPS | USR08 | USR08 | Exp Capital'ion | DAT | 8 | Conditional |
| PRPS | USR10 | USR10 | Cross System | CHAR | 1 | Conditional |
| PRPS | ZX01 | CAPEX/ OPEX | CHAR | 10 | Conditional For project profile ZPS0001 this field will be mandatory for all STUFE = 3. For other project profiles mapped. | |
| PRPS | ZX02 | Maintenance event | CHAR | 40 | Conditional This field will be applicable when PRART = Turnaround Projects and STUFE = 3 | |
| PRPS | ZX03 | Trading company code | CHAR | 4 | Conditional Required for project profile ZPS0004 when STUFE = 2 | |
| PRTE | PEINH | Unit of measure | CHAR | 4 | System Generated | |
| PRTE | EEINH | Unit of measure | CHAR | 4 | System Generated | |
| PRTE | IEINH | Unit of measure | CHAR | 4 | System Generated |
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.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
1026-001 | C3 | Projects with no actuals / commitment / used in account assignment for maintenance orders | If the old projects do not have any actual (and/or) commitments in the past year, set the project to status CLSD (CJ20N) | Old project set to closed | WP2/PF2 |
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:
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- 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 Description | Team Responsible |
|---|---|---|
1 | Confirm scope and extraction approach for each ECC source systems WP2, PF2 (direct DB or manual extract) | Data Team (I2M), Data Team (Syniti) |
2 | Establish and validate Syniti connectivity to both ECC source systems | Technical / Basis Team, Data Team (Syniti) |
3 | Perform full data extraction from relevant SAP WBS elements from both source systems WP2, PF2 | Data Team (Syniti) |
4 | Extract WBS via the application layer for additional validations for Manual Data Collection using DCTs | Data Team (I2M) |
5 | Apply agreed Relevancy Criteria to filter only applicable WBS records for S/4HANA | Data Team (I2M), Data Team (Syniti) |
6 | In case of restricted access or connectivity issues, receive pre-extracted reports/files from source system team and upload to Syniti Migrate manually | Data Team (I2M), Data Team (Syniti) |
8 | Perform data quality checks on extracted records (e.g., missing fields, invalid dates, incorrect formats) | Data Team (I2M), Data Team (Syniti) |
9 | Review and approve extracted data sample sets from each source system before transformation begins | Business / Functional Team |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| POSID | WBS element | Unique Identifier for the WBS Element as per project coding mask. The position ID assigned to the WBS element is based on the Project Definition created in S/4. |
| POST1 | Description | 40 character description of the WBSE |
| VERNR | No. of Person Resp. | This field represents the position of the Person Responsible for a WBS Element and is mandatory field. It will be derived from the Project Definition and can be overwritten. Refer configuration table field TCJ04-PS_VERNR for data validation. |
| ASTNR | Applicant no. | This field represent the position of the Project Financial Controller. It will be derived from the Project Definition and can be overwritten. Refer configuration table field TCJ05-ASTNR for data validation. |
| PBUKR | Company code | Represents legal entity and inherited from the Project Definition. Refer configuration table field T001-BURKS for data validation. Additional validation required the Company code used on the WBS element must be the same as that of the Project Definition |
| PRCTR | Profit Center | In Syway, Profit Center represent a plant or a site or generic for GBU. This field will be inherited from the Project Definition, if required it can be overwritten. Refer master data table field CEPC-PRCTR for allowed values. |
| PRART | Project Type | It 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. |
| PLAKZ | Planning Element | Planning element checkbox is used to flag if WBS element is relevant for cost planning. This indicator will be default from configuration. |
| BELKZ | Acct asst elem. | This indicator enables financial posting on the WBS element. It will be checked in below conditions- 1. For WBS elements governed by CAPEX project profiles, activation of this checkbox is mandatory for all elements at level 3 and subordinate levels. 2. For WBS elements governed by Operational, Statistical & Recharge project profiles, activation of this checkbox is mandatory for all WBS elements. |
| FAKKZ | Billing Element | This indicator enables WBS element to record revenue against it. Required for Recharge WBSE only. |
| ABUKR | Requesting co. code | In Syway design this field will not be used |
| FKSTL | Responsible CC | Cost Center responsible for delivery of work. Required for WBS elements of Expense Project (Budget-managed) only. Refer master data table field KOSTL-KOSTL for allowed values. |
| FKOKR | CA resp. cost center | This is automatically derived from the Responsible Cost Center |
| FABKL | Factory Calendar | Factory Calendar defines year wise working and non-working days for a specific plant or business unit. It plays a crucial role in scheduling & planning. Derived from the Plant maintained on the WBS element. Refer configuration table field TFACD-IDENT for allowed values. |
| PWPOS | Currency | Currency at WBS element refers to the local currency used to record, process, and report financial transactions. Currency derived from WBS element's Company Code |
| WERKS | Plant | Plant represent a site of the WBS element. Mandatory for all WBS elements. |
| USR08 | Exp Capital'ion | Expected Capitalization date marks the anticipated execution of the AUC final settlement, restricted to WBS elements that include an Investment Profile. |
| USR10 | Cross System | This checkbox field, will be selected when intercompany services are needed for a WBS element. |
| XSTAT | Statistical | This field checkbox will be inactive for all projects except for WBS elements of project with Project Profile "ZPS0003" i.e. Statistical Expense. |
| KOSTL | CCtr posted actual | This field represents the receiver Cost Center of actual cost for any actual financial posting on the WBS element. |
| IMPRF | Investment Profile | Investment Profile on WBS element is used to enable auto generation of AuC w.r.t. predefined asset class. Refer configuration table field TAPRF-IVPRO for allowed values. |
| FUNC_AREA | Functional Area | Functional Area is an organizational unit used to classify expenses based on their purpose or function e.g. IS, IT & R&I. Project created via PPM Item: Functional Area will be derived from the project template, new WBS element under the hierarchy will inherit the Functional Area of the parent WBS element/ Project Definition. Project created manually i.e. without PPM Item: Functional Area will be maintained manually by the GBS. Refer configuration table field TFKB-FKBER for allowed values. |
| PSPHI | Project Definition | Project ID assigned to the WBS elements. Refer table PROJ-PSPHI for allowed values. |
| STUFE | Level | In a project, WBS elements are structured across multiple levels to form a tree-like hierarchy for better project controlling and monitoring. |
| UP | WBS_UP | This field represents the immediate superior WBS element (parent node) required for establishing parent-child relationships in the WBS hierarchy. |
| LEFT | WBS_LEFT | This field represents the left-adjacent WBS element in the same hierarchy level required for navigating sibling relationships within a WBS hierarchy. |
| ZX01 | CAPEX/ OPEX | This field identifies expense is CAPEX or OPEX. For project profiles ZPS0002 & ZPS0003 this field will be default to OPEX. |
| ZX02 | Maintenance event | This field is used to determine the settlement rule receiver for the relevant maintenance Work Order. This field will be applicable when Project Type = Turnaround Projects at level 3 WBS element |
| ZX03 | Trading company code | This field will be applicable when Project Type = Intercompany Recharge. Mandatory at Level 2 WBS to determine the trading company for intercompany recharges Additional validation required, Trading company must be unique per project. |
In conjunction with DCT business user will be provided with Person Responsible / Applicant list for reference.
Extraction Dependencies
| Item # | Step Description | Team 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 to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in
- 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 Description | Team 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 system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2/WP2 | PRPS | POSID | WBS element | S/4 Hana | PRPS | POSID | WBS element | Old to new: Conversion Exit |
| 2 | PF2/WP2 | PRPS | POST1 | Description | S/4 Hana | PRPS | POST1 | Description | Copy from source to target system |
| 3 | PF2/WP2 | PRPS | VERNR | No. of Person Resp. | S/4 Hana | PRPS | VERNR | No. of Person Resp. | Value Mapping Responsible Person to new Person Responsible Position ID |
| 4 | PF2/WP2 | PRPS | ASTNR | Applicant no. | S/4 Hana | PRPS | ASTNR | Applicant no. | Value Mapping Applicant to new Applicant Position ID |
| 5 | PF2/WP2 | PRPS | PBUKR | Company code | S/4 Hana | PRPS | PBUKR | Company code | Value Mapping: Old to New Company Code |
| 6 | PF2/WP2 | PRPS | PKOKR | Controlling area | S/4 Hana | PRPS | PKOKR | Controlling area | Value Mapping: Old to New Controlling Area |
| 7 | PF2/WP2 | PRPS | PRCTR | Profit Center | S/4 Hana | PRPS | PRCTR | Profit Center | Value Mapping: Old to New Profit Centre |
| 8 | PF2/WP2 | PRPS | PRART | Project Type | S/4 Hana | PRPS | PRART | Project Type | Old to new |
| 9 | PF2/WP2 | PRPS | PLAKZ | Planning Element | S/4 Hana | PRPS | PLAKZ | Planning Element | Copy from source to target system |
| 10 | PF2/WP2 | PRPS | BELKZ | Acct asst elem. | S/4 Hana | PRPS | BELKZ | Acct asst elem. | Copy from source to target system |
| 11 | PF2/WP2 | PRPS | FAKKZ | Billing Element | S/4 Hana | PRPS | FAKKZ | Billing Element | Copy from source to target system |
| 12 | PF2/WP2 | PRPS | FKSTL | Responsible CC | S/4 Hana | PRPS | FKSTL | Responsible CC | Value Mapping: Old to New Cost Centre |
| 13 | PF2/WP2 | PRPS | FKOKR | CA resp. cost center | S/4 Hana | PRPS | FKOKR | CA resp. cost center | Value Mapping: Old to New Cost Centre |
| 14 | PF2/WP2 | PRPS | FABKL | Factory Calendar | S/4 Hana | PRPS | FABKL | Factory Calendar | Copy from Project Definition |
| 15 | PF2/WP2 | PRPS | PWPOS | Currency | S/4 Hana | PRPS | PWPOS | Currency | Copy from Project Definition |
| 16 | PF2/WP2 | PRPS | WERKS | Plant | S/4 Hana | PRPS | WERKS | Plant | Value Mapping: Old to New Plant |
| 17 | PF2/WP2 | PRPS | XSTAT | Statistical | S/4 Hana | PRPS | XSTAT | Statistical | Copy from source to target system |
| 18 | PF2/WP2 | PRPS | KOSTL | CCtr posted actual | S/4 Hana | PRPS | KOSTL | CCtr posted actual | Value Mapping: Old to New Cost Centre |
| 19 | PF2/WP2 | PRPS | IMPRF | Investment Profile | S/4 Hana | PRPS | IMPRF | Investment Profile | Old to new |
| 20 | PROJ | FUNC_AREA | Functional Area | S/4 Hana | PRPS | FUNC_AREA | Functional Area | Copy from Project Definition PROJ-FUNC_AREA | |
| 21 | PF2/WP2 | PRPS | PSPHI | Project Definition | S/4 Hana | PRPS | PSPHI | Project Definition | Load Dependent: PSPID: Old Project to new project mapping |
| 22 | PF2/WP2 | PRPS | STUFE | Level | S/4 Hana | PRPS | STUFE | Level | Copy from source to target system |
| 23 | PF2/WP2 | PRHI | LEFT | WBS_LEFT | S/4 Hana | PRPS | PRHI-LEFT | WBS_LEFT | WBS Element Mapping |
| 24 | PF2/WP2 | PRHI | UP | WBS_UP | S/4 Hana | PRPS | PRHI-UP | WBS_UP | WBS Element Mapping |
| 25 | PF2/WP2 | PRPS | IMPRF | Investment Profile | S/4 Hana | PRPS | ZX01 | CAPEX/ OPEX | If Investment Profile "" then "Opex" Else "Capex" |
| 26 | DCT | PRPS | POSID | WBS element | S/4 Hana | PRPS | POSID | WBS element | Copy from source to target system |
| 27 | DCT | PRPS | POST1 | Description | S/4 Hana | PRPS | POST1 | Description | Copy from source to target system |
| 28 | DCT | PRPS | VERNR | No. of Person Resp. | S/4 Hana | PRPS | VERNR | No. of Person Resp. | Copy from source to target system |
| 29 | DCT | PRPS | ASTNR | Applicant no. | S/4 Hana | PRPS | ASTNR | Applicant no. | Copy from source to target system |
| 30 | DCT | PRPS | PBUKR | Company code | S/4 Hana | PRPS | PBUKR | Company code | Copy from source to target system |
| 31 | Controlling area | S/4 Hana | PRPS | PKOKR | Controlling area | Copy from Project Definition | |||
| 32 | DCT | PRPS | PRCTR | Profit Center | S/4 Hana | PRPS | PRCTR | Profit Center | Copy from source to target system |
| 33 | DCT | PRPS | PRART | Project Type | S/4 Hana | PRPS | PRART | Project Type | Copy from source to target system |
| 34 | DCT | PRPS | PLAKZ | Planning Element | S/4 Hana | PRPS | PLAKZ | Planning Element | Copy from source to target system |
| 35 | DCT | PRPS | BELKZ | Acct asst elem. | S/4 Hana | PRPS | BELKZ | Acct asst elem. | Copy from source to target system |
| 36 | DCT | PRPS | FAKKZ | Billing Element | S/4 Hana | PRPS | FAKKZ | Billing Element | Copy from source to target system |
| 37 | DCT | PRPS | FKSTL | Responsible CC | S/4 Hana | PRPS | FKSTL | Responsible CC | Copy from source to target system |
| 38 | DCT | PRPS | FKOKR | CA resp. cost center | S/4 Hana | PRPS | FKOKR | CA resp. cost center | Copy from source to target system |
| 39 | DCT | PRPS | WERKS | Plant | S/4 Hana | PRPS | WERKS | Plant | Copy from source to target system |
| 40 | DCT | PRPS | XSTAT | Statistical | S/4 Hana | PRPS | XSTAT | Statistical | Copy from source to target system |
| 41 | DCT | PRPS | KOSTL | CCtr posted actual | S/4 Hana | PRPS | KOSTL | CCtr posted actual | Copy from source to target system |
| 42 | DCT | PRPS | IMPRF | Investment Profile | S/4 Hana | PRPS | IMPRF | Investment Profile | Copy from source to target system |
| 43 | DCT | PRPS | S/4 Hana | PRPS | FUNC_AREA | Functional Area | Copy from source to target system | ||
| 44 | DCT | PRPS | PSPHI | Project Definition | S/4 Hana | PRPS | PSPHI | Project Definition | Copy from source to target system |
| 45 | DCT | PRPS | S/4 Hana | PRPS | STUFE | Level | Copy from source to target system | ||
| 46 | DCT | PRPS | LEFT | WBS_LEFT | S/4 Hana | PRPS | PRHI-LEFT | WBS_LEFT | Copy from source to target system |
| 47 | DCT | PRPS | UP | WBS_UP | S/4 Hana | PRPS | PRHI-UP | WBS_UP | Copy from source to target system |
| 48 | DCT | PRPS | USR08 | Exp Capital'ion | S/4 Hana | PRPS | USR08 | Exp Capital'ion | Copy from source to target system |
| 49 | DCT | PRPS | USR10 | Cross System | S/4 Hana | PRPS | USR10 | Cross System | Copy from source to target system |
| 50 | DCT | PRPS | IMPRF | CAPEX/ OPEX | S/4 Hana | PRPS | ZX01 | CAPEX/ OPEX | Copy from source to target system |
| 51 | DCT | PRPS | ZX02 | Maintenance event | S/4 Hana | PRPS | ZX02 | Maintenance event | Copy from source to target system |
| 52 | DCT | PRPS | ZX03 | Trading company code | S/4 Hana | PRPS | ZX03 | Trading company code | Copy from source to target system |
| 53 | DCT | S/4 Hana | PRPS | PS_POSNR | WBS Element internal number | System Generated | |||
| 54 | DCT | S/4 Hana | PRPS | OBJNR | Object Number | System Generated | |||
| 55 | DCT | S/4 Hana | PRPS | FABKL | Factory Calendar | Copy from Project Definition | |||
| 56 | DCT | S/4 Hana | PRPS | PWPOS | Currency | Copy from Project Definition | |||
| 57 | DCT | S/4 Hana | PRPS | SCOPE | Object class | Copy from Project Definition | |||
| 58 | DCT | PBUKR | Company Code | S/4 Hana | Value Mapping: Company Code Instance/GroupThis is to indicate the instance and group the record need to go. | ||||
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
| T001 | Value Mapping: Currency From Company Code |
| Company Code | Value Mapping: BUKRS: Old Company Code to New Company Code |
| Controlling Area | Value Mapping: Old to New Controlling Area |
| Cost Centre | Value Mapping: Old to New Cost Centre |
| Plant | Value Mapping: Old Plant to New Plant |
| Profit Center | Value Mapping: Old to New Profit Centre |
| Applicant | Value Mapping: Applicant to new Applicant Position ID |
| Person Responsible | Value Mapping Responsible Person to new Person Responsible Position ID |
| Investment Reason | Value Mapping: Investment Reason Old to New |
| Company Code Instance/Group | Value Mapping: Company Code to Group and Instance |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| Ensure all the fields and values are imported into ADMM Construction page correctly | Syway Data Team | |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Generation of Pre-load report | Check all the required fields |
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
| Task | Action |
|---|---|
Conversion Accuracy | SyWay I2M Data Team to verify that all fields below meet pass the 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
| Task | Action |
|---|---|
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
| Task | Action |
|---|---|
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:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- 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 Description | Team Responsible |
|---|---|---|
1 | Load using transaction CNMASSCREATE or Migration cockpit | Data Team |
2 | Load 3 records for < > to validate if data is loaded successfully without errors | Data Team |
3 | Load 3 records for < > to validate if data is loaded successfully without errors | Data Team |
4 | Proceed with full load if steps 2 and 3 are validated | Data Team |
5 | Validate few records loaded by accessing CN41N report | Data Team |
6 | Generate post load report if step 5 is validated | Data Team |
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
| 1 | Project Coding Mask |
| 2 | Company Code |
| 3 | Controlling Area |
| 4 | Project Type |
| 5 | Factory Calendar |
| 6 | Currency Code |
| 7 | Plant |
| 8 | Investment Profile |
| 9 | Functional Area |
| 10 | Trading company code |
| 11 | Define Tolerance Limits |
| 12 | WBS Status Profile |
| 13 | Validation |
| 14 | Substitution |
| 15 | Settlement Rules |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1024 | Project Definition |
| 1074 | Cost Centre |
| 1073 | Profit Centre |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
| Invalid Data | Project Definition does not exist | Correct upload data, review load of CNV-1024 |
| Invalid Data | WBS Element already exist | Correct upload data. |
| Invalid Data | Person Responsible does not exist | Correct upload data |
| Invalid Data | Applicant does not exist | Correct upload data |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
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
| Task | Action |
|---|---|
Conversion Accuracy | Verify that the Project Definition in target S/4 HANA were loaded correctly via Project Builder display and table PROJ |
Business
Completeness
| Task | Action |
|---|---|
| Verify template Project data - Project Definition | Extract data from PS report CN41N in S/4 Hana |
Accuracy
| Task | Action |
|---|---|
| Verify template Project data - Project Definition | Extract data from PS report CN41N in S/4 Hana |
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.