| Status | Approved |
| Owner | Soumen Laru |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach of Profit Centre Group (Alt, Std Hierarchy)s into S/4 HANA.
The document details out the field list, extraction criteria, scoping, mapping of Profit Centre Group (Alt, Std Hierarchy)s.
Note: Profit Centre Standard and Alternate hierarchies will be constructed newly based on the new organizational design. Therefore, even though extracting and transforming of source hierarchy is an option, that will not be used. Instead, a DCT( Data Construction Template) will be used to collect the new hierarchy details.
Conversion Scope
Profit Centre Group (Alt, Std Hierarchy)s which will be listed as part of scope list with new numbering will be in scope of migration.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Profit Centre Group (Alt, Std Hierarchy) | TBD | S4HANA | |
| WP2 | Profit Centre Group (Alt, Std Hierarchy) | TBD | S4HANA |
Additional Information
Multi-language Requirement
In the Syensqo Profit Centre Group (Alt, Std Hierarchy)s, the following four language keys must be maintained:
- English (EN)
- French (FR)
- Italian (IT)
- Chinese (ZN)
Note: For certain countries it may be required to also maintain account descriptions for certain Profit Centre Group (Alt, Std Hierarchy)s in local language as per regulatory requirement (e.g. Japanese) in the respective country. Such requests must be backed by supporting evidence of the underlying regulatory requirement.
Such data will be collected as part of DCT for the translation texts for Profit Centre Group (Alt, Std Hierarchy)s.
Document Management
Legal Requirement
Special Requirements
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Label | Data Type | Length | Syensqo Requirement R = Required : Mandatory field. O = Optional: Not mandatory. If a value is entered it doesn't impact Business Process. C = Conditional: Not mandatory. If a value is entered it impacts Business Process or Reporting. S = System: System generates the value. NU = Not Used |
| SETHEADER | SETNAME | SETNAMENEW | Set Name | CHAR | 24 | R |
| SETHEADERT | DESCRIPT | SETTEXT | Description | CHAR | 40 | R |
| SETNODE | SETNAME | SETNAMENEW | Parent Group Name | CHAR | 24 | R |
| SETNODE | SUBSETNAME | SUBSETNAME | Child Group Name | CHAR | 24 | C |
| SETLEAF | SETNAME | SUBSETNAME | Group Node Name | CHAR | 24 | R |
| SETLEAF | VALUE | SETVALMIN | Profit Center Code | CHAR | 40 | R |
| SETLEAF | VALFROM | VALFROM | Valid-From Date | CHAR | 8 | R |
| SETLEAF | VALTO | VALTO | Valid-To Date | CHAR | 8 | R |
Data Cleansing
ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
1. | N/A |
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
Extraction
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; 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 . This is to be conducted using DCT (Data Collection Template) in
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. | Ensure DCT is collected for the Profit Centre Group (Alt, Std Hierarchy)s based on the collection template | Data team |
2. | Perform preliminary completeness check documented in section 5.2.8.1.1 | 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 |
5. | Report extraction result to person in charge of APOI conversion | Data 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 |
| KOKRS | Controlling Aera | Default to 'CO01' |
| SETHEADER-SETNAME | Set Name | The standard hierarchy will be organized via the following structure: - GBU / Company Code / Plant / Function The standard hierarchy will only include authorization relevant dimensions for cost centers. All reporting dimension can be covered via alternative (flexible) hierarchies |
| SETHEADERT-DESCRIPT | Description | Group description |
| SETNODE-SETNAME | Parent Group Name | The code of the parent group. If node 2, it refers to node 1. If node 1 : no reference. |
| SETNODE-SUBSETNAME | Child Group Name | The code of the child group. If node 1, it refers to node 2. If node 2 : no reference as it will be directly profit center values. For the values, refer to the field Set Name. |
| SETLEAF-SETNAME | Group Node Name | Changes based on the length of the item/package. |
| SETLEAF-VALUE | Profit Center Code | ID of the Profit center assigned to the Group (node of the standard or alternative hierarchy). The Profit center ID is defined within Profit center master data and not within the hierarchy. The field here is just to display. |
| SETLEAF-VALFROM | Valid-From Date | Validity date of the profit center. display only. Defined at PC level. It is just displayed here. |
| SETLEAF-VALTO | Valid-To Date | Validity date of the profit center. display only. Defined at PC level. It is just displayed here. |
Suggestion to add:
Decimal validation - Check table TCURX for the document currency key and if Decimals (TCURX-CURRDEC) is ‘0’, validate that no decimal value is populated.
Extraction Dependencies
Item # | Step description | Team responsible |
1. | Any period / year end close activities have been fully completed | Business |
2. | Reconciliation for intercompany payables have been completed, and adjustment made in legacy SAP system | Business |
3. | Reconciliation of migrated Purchase Order is completed before the extraction of Accounts Payable Open Items | Business and Data |
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. | Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into toolMigrate. | Data team |
2. | In tool, select the Cost Centre Group (Alt, Std Hierarchy) Object | Data team |
3. | Go to Process Area Launch and Process the Object - Cost Centre Group (Alt, Std Hierarchy) Object | Data team |
4. | Launch the Objects to execute transformation. | Data team |
5. | Monitor the transformation progress and ensure performance and completion is within allowed timeframe | Data team |
6. | Generate Pre-Load reports . | Data team |
7. | Generate data load count. | Data team |
8. | Log errors as defects, if any and address resolutions. Close defects. | Data team |
9. | Re-transform and re-validate the Pre-load reports if necessary. | Data team |
10. | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
11. | Analyse and resolve any pre-load defects logged by business. | Data team |
12. | Repeat steps 6 to 11 if necessary | Data team |
13. | 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 | DCT/ECC | SETHEADER | SETNAME | Set Name | S/4HANA | SETHEADER | SETNAME | Set Name | Copy From DCT as-is |
| 2 | DCT/ECC | SETHEADERT | DESCRIPT | Description | S/4HANA | SETHEADERT | DESCRIPT | Description | Copy From DCT as-is |
| 3 | DCT/ECC | SETNODE | SETNAME | Parent Group Name | S/4HANA | SETNODE | SETNAME | Parent Group Name | Copy From DCT as-is |
| 4 | DCT/ECC | SETNODE | SUBSETNAME | Child Group Name | S/4HANA | SETNODE | SUBSETNAME | Child Group Name | Copy From DCT as-is |
| 5 | DCT/ECC | SETLEAF | SETNAME | Group Node Name | S/4HANA | SETLEAF | SETNAME | Group Node Name | Copy From DCT as-is |
| 6 | DCT/ECC | SETLEAF | VALUE | Profit Center Code | S/4HANA | SETLEAF | VALUE | Profit Center Code | Copy From DCT as-is |
| 7 | DCT/ECC | SETLEAF | VALFROM | Valid-From Date | S/4HANA | SETLEAF | VALFROM | Valid-From Date | Copy From DCT as-is |
| 8 | DCT/ECC | SETLEAF | VALTO | Valid-To Date | S/4HANA | SETLEAF | VALTO | Valid-To Date | Copy From DCT as-is |
Transformation Mapping
Mapping Table Name | Mapping Table Description |
N/A |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool. | Data Team |
Pre-Load Validation
Project Team
Completeness
Task | Action |
Generation of | Mandatory field check.
|
Record Count | Record Count
|
Accuracy
Task | Action |
Mandatory field mapping and transformation | Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values. |
Business
Completeness
| Task | Action |
|---|---|
| Verify record count in Pre-load reports by region | Confirm the Preload File contains all the records in scope of migration based on the DCT (Data Construction Template) |
Accuracy
| Task | Action |
|---|---|
| Conversion accuracy | Verify Profit Centre Group (Alt, Std Hierarchy)s are transformed accurately as per endorsed transformation/mapping rules. Review error reports in tool for any mismatch or missing transformed values. In legacy system, execute ECC tcode SE16N to display table SETHEADER, SETLEAF and SETNODE ( with SETCLASS = '0106' ) to confirm copied fields are accurately copied. ( If applicable) |
Load
The load process includes:
- Execute the automated data load into target system using load tool or produce the load file if the loading of records to be done using LTMC cockpit object of Profit Centre Group (Alt, Std Hierarchy).
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_ECC, XXXX_S4HANA, XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE)
Load Run Sheet
Item | Step description | Team responsible |
1 | Ensure the load tools are transported into the correct tool instance. | Data team |
2 | Ensure DCTs and all required mappings are submitted and complete | Data team |
3 | Ensure Pre-load sign-offs are obtained. | Data team |
4 | Execute upload of Profit Centre Group (Alt, Std Hierarchy) Object using Migration Cockpit Object for Profit Centre Group (Alt, Std Hierarchy) Upload | Data team |
5 | Generate the post load reports in tool. | Data team |
6 | Log errors as defects, if any and address resolutions. Close defects. | Data team |
7 | Resolve defects by reupload and re-generate post load reports if necessary. | Data team |
8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
9 | Repeat steps 5 to 7 if necessary. | Data team |
Load Phase and Dependencies
Configuration
Item # | Configuration item |
1. | Controlling Area |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| N/A |
Error Handling
Error type | Error description | Action taken |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Reconciliation of Record Count | Check Record count between DCT, Preload file and target extracted data from tables SETHEADER, SETNODE, SETLEAF. A Summary report to be added in the post-load report |
Accuracy
| Task | Action |
|---|---|
| Check values in key fields for accuracy | Refer to the post-load file and Manual check of the Loaded data using KCH3 and SE16N |
Business
Completeness
| Task | Action |
|---|---|
| Record Count Check | Business to check Post-Load File and Summary report in post-load |
Accuracy
| Task | Action |
|---|---|
| Spot check | Spot check some sample records from the post-load report to be picked for checking in SAP transaction code KCH3 to verify accuracy of the data. |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- is in scope based on data design and any exception requested by business.
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||