Versions Compared

Old Version 4

changes.mady.by.user LARU-ext, Soumen

Saved on

compared with

New Version Current

changes.mady.by.user LARU-ext, Soumen

Saved on

Key

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

pagestatus
Percentage Progress | Vectors (Formerly: SP Percentage progress bar)
backgroundColor0052CC
percentage100

OwnerSoumen Laru
Stakeholders

PILLAY-ext, Lawrence WELENSKY-ext, Dave GARCIA-ext, Angel Luis  GONCHIGARU-ext, Ashok 

Purpose

The purpose of this document is to define the conversion approach of Cost Centre Group (Alt, Std Hierarchy)s into S/4 HANA.  

The document details out the field list, extraction criteria, scoping, mapping of cost centre object

Cost Centres will be extracted from Source and based on the list of cost centres from the cost centre mapping sheet, target cost centre data file will be 

of  Cost Centre Group (Alt, Std Hierarchy)s.

Note:  Cost 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. 

As per the current implementation approach, any alternative hierarchies, if applicable, will be uploaded exclusively through the Manage Global Hierarchies application and not via LSMW. Should there be a requirement to upload any alternative hierarchy using LSMW, this specification is designed to accommodate such a scenario. At this stage, there is no anticipated requirement for the inclusion of alternative hierarchies within the migration scope.

Conversion Scope

Cost Centre Group (Alt, Std Hierarchy)s which will be listed as part of scope list with new numbering will be in scope of migration. 


List of source systems and approximate number of records 
SourceScope

Source Approx No. of

Conversion Scope

Cost Centre Group (Alt, Std Hierarchy)s which will be listed as part of scope list with new numbering will be in scope of migration. 

List of source systems and approximate number of records 
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2Cost Centre Group (Alt, Std Hierarchy)TBDS4HANATBD
WP2Cost Centre Group (Alt, Std Hierarchy)TBDS4HANATBD

Additional Information

Multi-language Requirement

In the Syensqo Cost 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 Cost 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 Cost Centre Group (Alt, Std Hierarchy)s.

Document Management

Legal Requirement

Special Requirements




Target Design

The technical design of the target for this conversion approach. 

SETNAMESETNAMENEW Name24SETHEADERTDESCRIPTDescription40SUBSETNAMEChild Group Name24CVALUE40
TableFieldData Element Field LabelData TypeLengthSyensqo 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
SETCLASS
SETCLASSSet
ClassCHAR
4R
SETHEADER
SUBCLASS
SETTEXT
SETSUBCLSSub class org unit CHAR
12R
SETNODESETHEADERSETNAMESETNAMENEWParent Group Set NameCHAR24RSETNODE
SETHEADERT
LANGU
SUBSETNAME
SPRASLanguage KeyCHAR
1
R
SETLEAFSETHEADERTSETNAMEDESCRIPTSUBSETNAMESETTEXTGroup Node NameDescriptionCHAR2440RSETLEAF
SETNODE
LINEID
SETVALMINProfit Center CodeCHAR
SETLINESet Line CounterNUMC10
R
SETLEAFSETNODEVALFROMSETNAMEVALFROMSETNAMENEWParent Group NameValid-From DateCHAR824R
SETLEAFSETNODEVALTOSUBSETNAMEVALTOSUBSETNAMEChild Group NameValid-To DateCHAR824RC
Data Cleansing
SETLEAF
ID
SETNAME

Criticality

Error Message/Report Description

Rule

Output

Source System

1.      

N/A

SUBSETNAMEGroup Node NameCHAR24O
SETLEAFVALFROMVALFROM(Cost Centre) From ValueCHAR40O
SETLEAFVALTOVALTO(Cost Centre) To ValueCHAR40O


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:

Note: When Data Source denotes DCT, no relevancy and extract rules to be applied in Syniti tool. DCT records will be collected by business Data Consultant. 

Image Added

Data Privacy and Sensitivity


Extraction

Conversion Process 

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

Image Removed

Data Privacy and Sensitivity

Extraction

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

  1. The data exists. connects to the source and loads the data into . 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 ; 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 . 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 Cost 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 ScreenParameter NameSelection TypeRequirementValue 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


Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
N/A




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 will be used by the data collectors for collecting data.


Note: Constructed data will be imported into ADM Data Construction page.

There will be two pages -

  1. Main page to contain the hierarchy details with EN Language key Description

  2. Detailed Page will contain descriptions SETHEADERT-LANGU,  ( SETHEADERT-DESCRIPT )  of the SETHEADER-SETNAME in various languages as they are collected.


Table NameField NameField descriptionRule
SETHEADER-SETNAMESet NameThe standard hierarchy will be organized
CSKSKOKRSControlling AeraDefault to 'CO01' 
SETHEADERSETCLASSSet ClassSet to '0101' for Cost Centre Group
SETHEADERSUBCLASSOrganizational Unit as Set SubclassDefault to 'CO01'
SETHEADERSETNAMESet NameThe 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
-
LANGULanguage KeyLanguage Key of the Text
SETHEADERTDESCRIPTDescriptionGroup description
SETNODE
-SETNAME
Parent Group NameThe
LINEIDLine NumberThis will contain the level of the hierarchy nodes ( will do in exact hierarchy form ) - example is given in Load section.
SETNODESETNAME_SETNODEParent Group NameThe code of the parent group. If node 2, it refers to node 1. If node 1 : no reference.
SETNODE
-
SUBSETNAMEChild 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 Cost center values.
For the values, refer to the field Set Name. 
SETLEAF
-
SETNAME_SETLEAFGroup Node NameChanges based on the length of the item/package.
SETLEAF
-VALUE
Cost center CodeID of the Cost center assigned to the Group (node of the standard or alternative hierarchy). The Cost center ID is defined within Cost center master data and not within the hierarchy. The field here is just to display. SETLEAF-VALFROMValid-From DateValidity date of the Cost center. display only. Defined at PC level. It is just displayed here. SETLEAF-VALTOValid-To DateValidity date of the Cost 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:

VALFROM(Profit Centre) From ValueCost Centre Value ( Optional in DCT and Cost centres will be assigned to Hierarchy node in Cost Centre DCT part of CNV-1074 Cost Centre )
SETLEAFVALTO

(Profit Centre) To Value

Cost Centre Value ( Optional in DCT and Cost centres will be assigned to Hierarchy node in Cost Centre DCT part of CNV-1074 Cost Centre ) 

Descriptions will be collected on multiple languages and therefore a detail page to created and linked to the main page

Table NameField NameField descriptionRule
SETHEADERSETNAMESet NameThe standard hierarchy will be organized via the following structure:
- GBU / Company Code / Plant

The standard hierarchy will only include authorization relevant dimensions for cost centers.

All reporting dimension can be covered via alternative (flexible) hierarchies
SETHEADERTLANGULanguage KeyLanguage Key of the Text
SETHEADERTDESCRIPTDescriptionGroup description

Extraction Dependencies


Item #

Step description

Team responsible

1.      

N/A




Transformation

The Target fields are mapped to the applicable DCT field that will be its source.  

Note:  as this object is DCT, the mapping rule for all the fields is 'Copy'  as described in the transform rule section. However, some reports are to be created and executed to ensure integrity in the data collected in DCT as described in 'Pre-load Data Validation' section. 

This step 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

    1. Prepare target-ready data in the target 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 Validationin the load section.
    2. Produce the preload reports as requested in the 'Preload Data Validation' section. 

    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 Trial Balance object PY.Cost Centre Group (Alt, Std Hierarchy) Object

    Data team

    3.      

    Go to Process Area Launch and Process the Object - Trial Balance object - R4 Trial Balance PYCost Centre Group (Alt, Std Hierarchy) 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 systemSource TableSource FieldSource descriptionTarget systemTarget TableTarget FieldTarget descriptionTransformation logic
    1DCT/ECCSETHEADER
    SETNAME
    SETCLASSSet
    Name
    ClassS/4HANASETHEADER
    SETNAME
    SETCLASSSet
    Name
    ClassCopy From DCT as-is
    2DCT/ECC
    SETHEADERT
    SETHEADER
    DESCRIPT
    SETNAME
    Description
    Set NameS/4HANA
    SETHEADERT
    SETHEADER
    DESCRIPT
    SETNAME
    Description
    Set NameCopy From DCT as-is
    3DCT/ECC
    SETNODE
    SETHEADERT
    SETNAMEParent Group Name
    LANGULanguage KeyS/4HANA
    SETNODE
    SETHEADER
    SETNAMEParent Group Name
    LANGULanguage keyCopy From DCT as-is
    4DCT/ECC
    SETNODE
    SETHEADERT
    SUBSETNAME
    DESCRIPT
    Child Group Name
    DescriptionS/4HANA
    SETNODE
    SETHEADERT
    SUBSETNAME
    DESCRIPT
    Child Group Name
    DescriptionCopy From DCT as-is
    5DCT/ECC
    SETLEAF
    SETNODE
    SETNAMEGroup Node Name
    LINEIDSet LineS/4HANA
    SETLEAF
    SETNODE
    SETNAMEGroup Node Name
    LINEIDSet LineCopy From DCT as-is
    6DCT/ECC
    SETLEAF
    SETNODE
    VALUECost center Code
    SETNAMEParent Group NameS/4HANA
    SETLEAF
    SETNODE
    VALUECost
    SETNAMEParent Group Name
    center Code
    Copy From DCT as-is
    7DCT/ECC
    SETLEAF
    SETNODE
    VALFROMValid-From Date
    SUBSETNAMEChild Group NameS/4HANA
    SETLEAF
    SETNODE
    VALFROMValid-From Date
    SUBSETNAMEChild Group NameCopy From DCT as-is
    8DCT/ECCSETLEAF
    VALTOValid-To Date
    SETNAMEGroup Node NameS/4HANASETLEAF
    VALTOValid-To Date
    SETNAMEGroup Node NameCopy From DCT as-is

    Transformation Mapping

    9DCT/ECCSETLEAFVALFROM

    Mapping Table Name

    Mapping Table Description
    Cost Centre
    Group (Alt, Std Hierarchy)

    Mapping of legacy Cost center to target system value

    Person Responsible

    Mapping of legacy Person Responsible to New Person Responsible

    User ID

    Mapping of legacy User ID

    Hierarchy Group

    Mapping of Legacy Hierarchy Group to Hierarchy Group

    Transformation Dependencies

    List the steps that need to occur before transformation can commence
    ( From Value )S/4HANASETLEAFVALFROMValid-From DateCopy From DCT as-is
    10DCT/ECCSETLEAFVALTOCost Centre ( To Value )S/4HANASETLEAFVALTOValid-To DateCopy 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
    Item #Step DescriptionTeam Responsible
    1Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool.Data Team
    2

    Ensure Cost Centre Group (Alt, Std Hierarchy) hierarchies are loaded into target S/4HANA

    		Data Team
    and values are imported into ADM Construction page correctlyData Team


    Pre-Load Validation

    Project Team

    Completeness

    Task

    Action

    Generation of
    Pre-load reports

    Mandatory field check.

    • Cost Centre Group (Alt, Std Hierarchy)s are mapped to new values
    • Cost Centre Group (Alt, Std Hierarchy) Hierarchy Mapped to new valuesLanguage key(LANGU) for description in various languages maintained. 

    Record Count

    Record Count

    • Confirm the record counts in preload summary report
      • Total Records: To be Filled in Summary Report
      • Valid Records: To be Filled in Summary Report
      • Invalid Records: To be Filled in Summary Report

    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. 
    Review the data report to ensure mapping value is not missing in tool.
    Capture errors in the Data Error report.

    Business

    Completeness

    TaskAction
    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

    TaskAction
    Conversion accuracy

    Verify Cost 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 = '0101' ) to confirm copied fields are accurately copied. ( If applicable)

    Load

    The load process includes:

    confirm copied fields are accurately copied. ( If applicable)


    Load

    Loading of standard hierarchy: Load Template is different from the data collection template. Loading of standard hierarchy will be done using LSMW with Idoc ( COSTCENTERGROUP_CREATE_01) as the technology behind. 

    Loading of Alternate hierarchy: Loading of alternate hierarchy will be done using LSMW with Idoc ( COSTCENTERGROUP_CREATE_01) as the technology behind. However, some fiori based app will be explored to check if that could be used for upload alternate hierarchy. In this option,  loading is done using either the "Manage Global Hierarchies" (F2918) or "Manage Flexible Hierarchies" (F2759) app in your Fiori launchpad.

    Loading of Descriptions in various Languages: Loading of descriptions in various languages will be done using tcode SE63.


    Three exports views will be required to upload this object. 

    Export view 1. 

    Please generate an export view for the load template as in the table below, details of mapping of fields between DCT to load template.

    LNIND = H for the record where DCT field SETNAME is empty

    LNIND = L for all the other lines

    Parent = DCT Field SETNAME_SETNODE

    VALU1 = DCT Field SUBSETNAME

    VALU2 = DCT Field LINEID

    VALU3 = 0 for standard hierarchy and count of VALFROM for combination of other fields ( LNIND, Parent, VALU1, VALU2 ) 

    VALU4 = DCT Field DESCRIPT

    LNIND

    Parent 

    VALU1

    VALU2

    VALU3

    VALU4

    H


    <Controlling area - KOKRS>




    L

    <SETHEADER-SETNAME>

    <SETHEADER-SETNAME>

    0

    0

    <SETHEADERT-DESCRIPT>

    L

    <SETNODE-SETNAME>

    <SETNODE-SUBSETNAME>

    <SETNODE-LINEID> E.G 1 

    0

    <SETHEADERT-DESCRIPT>

    L

    <SETNODE-SETNAME>

    <SETNODE-SUBSETNAME>

    <SETNODE-LINEID> E.G 2

    0

    <SETHEADERT-DESCRIPT>

    L

    <SSETNODE-SETNAME>

    <SETNODE-SUBSETNAME>

    <SETNODE-LINEID> E.G 3

    0

    <SETHEADERT-DESCRIPT>

    L

    <SETNODE-SETNAME>

    <SETNODE-SUBSETNAME>

    <SETNODE-LINEID> E.G 4

    0

    <SETHEADERT-DESCRIPT>

    L

    <SETNODE-SETNAME>

    <SETNODE-SUBSETNAME>

    <SETNODE-LINEID> E.G 4

    0

    <SETHEADERT-DESCRIPT>

    L

    <SETNODE-SETNAME>

    <SETNODE-SUBSETNAME>

    <SETNODE-LINEID> E.G 3

    0

    <SETHEADERT-DESCRIPT>

    L

    <SETNODE-SETNAME>

    <SETNODE-SUBSETNAME>

    <SETNODE-LINEID> E.G 4

    0

    <SETHEADERT-DESCRIPT>

    L

    <SETNODE-SETNAME>

    <SETNODE-SUBSETNAME>

    <SETNODE-LINEID> E.G 4

    0

    <SETHEADERT-DESCRIPT>


    Export view 2.

    Generate 2nd export view containing below columns. This view will contain the profit centres to be assigned to the hierarchy node. 

    This view is created for the non-blank entries from SETLEAF.

    SETNAME

    VALFROM

    VALTO

    <SETLEAF-SETNAME>

    <SETLEAF-VALFROM>

    <SETLEAF-VALTO>

    <SETLEAF-SETNAME>

    <SETLEAF-VALFROM>

    <SETLEAF-VALTO>

    <SETLEAF-SETNAME>

    <SETLEAF-VALFROM>

    <SETLEAF-VALTO>


    Export view 3.

    Generate 3rd view containing the descriptions of the Hierarchy for different languages. 

    SETNAME

    LANGUAGE

    DESCRIPTION

    <SETHEADER-SETNAME>

    <SETHEADER-LANGU>

    <SETHEADER-DESCRIPT>

    <SETHEADER-SETNAME>

    <SETHEADER-LANGU>

    <SETHEADER-DESCRIPT>

    <SETHEADER-SETNAME>

    <SETHEADER-LANGU>

    <SETHEADER-DESCRIPT>


    Note:  Description translation data which will be given in the export view 3, will be loaded using tcode SE63.  LSMW will be created based on the tcode SE63 to enable mass upload of this data. However, further checks will be done to check if some Fiori App could be used for uploading. 


    Note:

  • 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 Cost 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

    DCT, 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 Cost Centre Group (Alt, Std Hierarchy) Object using Migration Cockpit Object for Cost 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

    TaskAction
    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

    TaskAction
    Check values in key fields for accuracy

    Refer to the post-load file and Manual check of the Loaded data using KSH3 and SE16N


    Business

    Completeness

    TaskAction
    Record Count Check

    Business to check Post-Load File and Summary report in post-load


    Accuracy

    TaskAction
    Spot checkSpot check some sample records from the post-load report to be picked for checking in SAP transaction code KSH3 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

    Change History
    limit10

    Workflow history

    Workflow Report
    parent@self
    hideheadertrue
    typeapprovals