You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

Purpose

</Start CR359 - Global Hierarchy Definition> 

The purpose of this document is to define the approach for the maintenance of master data  'Investment Classification' Global Hierarchy which defines classification criteria for a Portfolio Item.


Conversion Scope

The scope of this document covers the approach applicable to Investment Classification  Global Hierarchy which are created in S/4 HANA following the Project Scoring and Other dropdowns Master Data Design Standard.  

This is a completely new object for Syensqo with the data being sourced using DCT (Data Collection Template).

List of source systems and approximate number of records

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

DCTAll Records
S/4HANATBD

For Mock-1 conversions, data will be loaded directly into S/4HANA ROW and China instances.

Note: The Master Data Management (MDM) process is not built yet; the approach for loading and reconciling PPM master data in MDM will be covered as part of the MDM design and is not covered in this Conversion Specification.

Additional Information

Multi-language Requirement

Maintained in English Language only.

Document Management

Not applicable

Legal Requirement

Not applicable

Special Requirements

Not applicable


Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
UHDT_VRSNVER_IDVRSIDVersion ID (Hierarchy)CHAR40System Generated
UHDT_VRSNVER_STATUSVRSSTVersion StatusCHAR1Mandatory
UHDT_VRSNHIER_HIDVHRIDHierarchy IDCHAR20Mandatory
UHDT_VRSNHIER_CATGCAKEYHierarchy SubtypeCHAR4Mandatory
UHDT_VRSNUPDATED_ATVRSUTVersion Updated TimeDEC15System Generated
UHDT_VRSNUPDATED_BYVRSUBVersion Updated By   CHAR12System Generated
UHDT_VRSNCREATED_ATVRSCTVersion Creation Time   DEC15System Generated
UHDT_VRSNCREATED_BYVRSCBVersion Created By   CHAR12System Generated
UHDT_VRSNLOCKED_BYUNAMEUser Name   CHAR12System Generated
UHDT_VRSNLOCKED_ATVRSLTVersion locked at   DEC15System Generated
UHDT_VRSNMAINTENANCE_LANGLANGULanguage Key   LANG1System Generated
UHDT_NODENODE_IDNODIDNode ID   CHAR40System Generated
UHDT_NODEVER_IDVRSIDVersion ID  CHAR40System Generated
UHDT_NODENODE_PIDNPNIDNode Parent ID  CHAR40Mandatory
UHDT_NODENODE_TYPENODTPNode Type  CHAR1Mandatory
UHDT_NODENODE_ENTITYBNNAMBusiness Entity Name  CHAR30System Generated
UHDT_NODENODE_LEVELNLEVLNode Level  NUMC6System Generated
UHDT_NODENODE_LVALNLVALNode Low Value  CHAR40Mandatory
UHDT_NODECREATED_ATNODCTNode Creation Time  CHAR14System Generated
UHDT_NODECREATED_BYNODCBNode Created By  CHAR12System Generated
UHDT_NODEUPDATED_ATNODUTNode Updated Time  CHAR14System Generated
UHDT_NODEUPDATED_BYNODUBNode Updated By   CHAR12System Generated
UHDT_NTXTNODE_IDNODIDNode ID (for Text)   CHAR40System Generated
UHDT_NTXTLANGLANGULanguage Key (Node Text)   LANG1System Generated
UHDT_NTXTLVAL_TXTNLTXTNode Low Text  CHAR128Mandatory
UHDT_NTXTVER_IDVRSIDVersion ID (Hierarchy for Node Text)  CHAR40System Generated
UHDT_NATTRVALSNODE_IDNODIDNode ID (for Attribute)  CHAR40System Generated
UHDT_NATTRVALSATTR_NAMENATNMAttribute Name  CHAR30System Generated
UHDT_NATTRVALSATTR_LVALALVALAttribute Low Value  CHAR40Mandatory
UHDT_NATTRVALSVER_IDVRSIDVersion ID (Hierarchy for Node Attribute)  CHAR40System Generated


Data Cleansing

Data cleansing not applicable, as data object Project Scoring and Other dropdowns - Investment Classification' Global Hierarchy will be collected specifically for data migration. 

Collection will be done manually in the Data Collection Template.

IDCriticalityError Message/Report DescriptionRuleOutputSource System


Not applicable



Conversion Process

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

Data Privacy and Sensitivity

Not applicable


Extraction

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 DescriptionTeam Responsible
1Ensure DCT is collected Data Team
2Perform preliminary completeness check, data quality check.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

Selection Screen

Not Applicable
Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
Not Applicable



Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Project Scoring and Other dropdowns - Investment Classification' Global Hierarchy data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules.

Field NameField DescriptionRule
HIER_HIDHierarchy ID

ID of the Hierarchy/Root node

Must be 'SY_INV' for Syensqo's Investment Classification Hierarchy

Display field in DCT

HIER_CATGHierarchy Subtype

Hierarchy Type configured with controls and settings for the Hierarchy

Must be 'ZINV' for Syensqo's Investment Classification Hierarchy

Display field in DCT

NODE_TYPENode Type

Code identifying the type of Node. For the Syensqo Investment Classification hierarchy these are:

Tooltips
- R = Root Node (automatically assigned, 1:1 with hierarchy)
- N = Inner Node (level 1, 2 or 3)
- L = Leaf Node (level 4)

Dropdown to have both code and description

NODE_LVALNode Low Value

External ID of the Node, manually assigned.

Tool Tip:

If Node level 1
- Must be 'G' or 'S'
If Node level 2
- Must be the level 1 ID concatenated with '__01' eg. 'G_01'
If Node level 3
- Must be the level 2 ID concatenated with '__01' eg. 'G_01_01'
If Node level 4
- Will be selected from the Investment Reason master data table /SYQ/T_INVEST_RSN-INVEST_RSN_CD. Dropdown with description required 

It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

LVAL_TXTNode Low Text

Name of the Node:

Tooltip:

- Root node = 'Syensqo Investment Classification'
- Free text for Inner Nodes
- N/a for Leaf Nodes (name is derived from master data)

It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

NODE_PIDNode Parent ID

Reference to the Node ID of the Parent Node. This is the node selected under which a new node is created.

Maintain manually

It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

ATTR_LVALAttribute Low Value

Value of the Node Attribute, selected from the allowed list of values defined in configuration.

-ZCLASS (Classification) dropdown as 'Investment Category', 'Main Business Driver', 'Sub Business Driver' or 'Investment Reason

- ZSCORE must be a valid entry on the Scoring Methodology master data table /SYQ/T_SCORING_METH.

FieldDescription
SCORING_METHOD_CDScoring Methodology Code
SCORING_METHOD

Scoring Methodology Description

ACTIVE

ACTIVE

Dropdown to have both code and description.

-ZFUNC must be a valid entries  (multiple entries are allowed) on the Functions master data table  /SYQ/T_FUNCTION 

FieldDescription
FUNCTION_CDFunction Code
FUNCTION_DESCFunction Description
ACTIVEACTIVE

Dropdown to have both code and description

It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template

Extraction Dependencies

No Dependencies for Extract

Item #Step DescriptionTeam Responsible

Not applicable


Transformation

No transformation mapping required.

 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 DescriptionTeam 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
8Re-transform and re-validate the Pre-load reports if necessary.Data team
9Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.Business
10Analyze and resolve any pre-load defects logged by business.Data team
11Repeat steps 7 to 10 if necessaryData team
12Proceed to pre-load validationsData team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1



S/4 HanaUHDT_VRSNUHDT_VRSNVersion ID (Hierarchy)System Generated
2



S/4 HanaUHDT_VRSNVER_STATUSVersion Status

Mandatory

Load with status = Active

3DCT
HIER_HIDHierarchy IDS/4 HanaUHDT_VRSNHIER_HIDHierarchy ID

Manually copy from Non ECC source

Must be 'SY_INV' for Syensqo's Investment Classification Hierarchy

4DCT
HIER_CATGHierarchy SubtypeS/4 HanaUHDT_VRSNHIER_CATGHierarchy Subtype

Manually copy from Non ECC source

Must be 'ZINV' for Syensqo's Investment Classification Hierarchy

5

  S/4 HanaUHDT_VRSNUPDATED_ATVersion Updated TimeSystem Generated
6

  S/4 HanaUHDT_VRSNUPDATED_BYVersion Updated BySystem Generated
7

  S/4 HanaUHDT_VRSNCREATED_ATVersion Creation TimeSystem Generated
8

  S/4 HanaUHDT_VRSNCREATED_BYVersion Created By System Generated
9

  S/4 HanaUHDT_VRSNLOCKED_BYUser NameSystem Generated
10

  S/4 HanaUHDT_VRSNLOCKED_ATVersion locked atSystem Generated
11

  S/4 HanaUHDT_VRSNMAINTENANCE_LANGLanguage KeySystem Generated
12

  S/4 HanaUHDT_NODENODE_IDNode IDSystem Generated
13

  S/4 HanaUHDT_NODEVER_IDVersion IDSystem Generated
14DCT
NODE_PIDNode Parent IDS/4 HanaUHDT_NODENODE_PIDNode Parent ID

Mandatory

Manually copy from Non ECC source

15DCT
NODE_TYPENode TypeS/4 HanaUHDT_NODENODE_TYPENode Type

Mandatory

Manually copy from Non ECC source

For the Syensqo Investment Classification hierarchy these are:
- R = Root Node (automatically assigned, 1:1 with hierarchy)
- N = Inner Node (level 1, 2 or 3)
- L = Leaf Node (level 4)

16


 S/4 HanaUHDT_NODENODE_ENTITYBusiness Entity NameSystem Generated
17


 S/4 HanaUHDT_NODENODE_LEVELNode LevelSystem Generated
18DCT
NODE_LVALNode Low ValueS/4 HanaUHDT_NODENODE_LVALNode Low ValueMandatory. Manually copy from Non ECC source
19

  S/4 HanaUHDT_NODECREATED_ATNode Creation TimeSystem Generated
20

  S/4 HanaUHDT_NODECREATED_BYNode Created BySystem Generated
21

  S/4 HanaUHDT_NODEUPDATED_ATNode Updated TimeSystem Generated
22

  S/4 HanaUHDT_NODEUPDATED_BYNode Updated BySystem Generated
23

  S/4 HanaUHDT_NTXTNODE_IDNode ID (for Text)System Generated
24

  S/4 HanaUHDT_NTXTLANGLanguage Key (Node Text)System Generated
25DCT
LVAL_TXTNode Low TextS/4 HanaUHDT_NTXTLVAL_TXTNode Low TextMandatory. Manually copy from Non ECC source
26

  S/4 HanaUHDT_NTXTVER_IDVersion ID (Hierarchy for Node Text)System Generated
27

  S/4 HanaUHDT_NATTRVALSNODE_IDNode ID (for Attribute)System Generated
28

  S/4 HanaUHDT_NATTRVALSATTR_NAMEAttribute NameSystem Generated
29DCT
ATTR_LVALAttribute Low ValueS/4 HanaUHDT_NATTRVALSATTR_LVALAttribute Low Value

Mandatory. Manually copy from Non ECC source

Value of the Node Attribute, selected from the allowed list of values defined in configuration.

-ZCLASS (Classification) must be 'Investment Category', 'Main Business Driver', 'Sub Business Driver' or 'Investment Reason

- ZSCORE must be a valid entry on the Scoring Methodology master data table /SYQ/T_SCORING_METH.

FieldDescription
SCORING_METHOD_CDScoring Methodology Code
SCORING_METHOD

Scoring Methodology Description

ACTIVE

ACTIVE

Dropdown to have both code and description.

-ZFUNC must be a valid entries (multiple entries are allowed) on the Functions master data table  /SYQ/T_FUNCTION 

FieldDescription
FUNCTION_CDFunction Code
FUNCTION_DESCFunction Description
ACTIVEACTIVE

Dropdown to have both code and description

30

  S/4 HanaUHDT_NATTRVALSVER_IDVersion ID (Hierarchy for Node Attribute)System Generated

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

CNV_1192_Investment Classification Global Hierarchy template

Transformation Mapping


Mapping Table NameMapping Table Description
Not applicable

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible

Not applicable



Pre-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

Conversion Accuracy

SyWay I2M Data Team to verify that all fields below meet pass the checks:

  1. Mandatory Fields
  2. Null Checks
  3. 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.

Business

Completeness

TaskAction

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

TaskAction

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:

  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. For Mock 1: All data will be loaded into both the S/4 ROW and S/4 China clients. To be included in mock-1 cut-over strategy document 
  3. Post load, activate global hierarchy in SAP S/4HANA via Manage Global Hierarchies Fiori app (F2918) to make the hierarchy available for real-time reporting. Step required for mock-1 only.

Note: Once MDM is available the replication will be done from MDM to both instances ROW and China.

Load Run Sheet

Item #Step DescriptionTeam Responsible

1

Manually create the hierarchy header/root node in each instance (ROW and China)

Data Team

2

Load using fiori app Via Manage Global Hierarchies fiori app (F2918) 

Note: Syniti to evaluate whether standard app can be used for multiple entries upload or required custom program.

Data Team

3

Load 3 records for < > to validate if data is loaded successfully without errors

Data Team

4

Proceed with full load if step 3 is validated

Data Team

5

Validate few records loaded by accessing Manage Global Hierarchies Fiori App

Data Team

6

Generate post load report if step 5 is validated

Data Team

7

Activate Global hierarchy in SAP S/4 Hana via fiori app Manage Global Hierarchies (required for Mock1)

Data Team

8

All steps (from 2 to 7) must be repeated for S/4 ROW and then China

Data Team


Load Phase and Dependencies

Configuration


Item #Configuration Item
1Custom table /SYQ/T_SCORING_METH with fields SCORING_METHOD_CD, SCORING_METHOD, ACTIVE 
2Custom table  /SYQ/T_FUNCTION with fields FUNCTION_CD, FUNCTION_DESC, ACTIVE
3Custom table /SYQ/T_INVEST_RSN-INVEST_RSN_CD
4Global Hierarchy Type ZINV

Conversion Objects

Object #Preceding Object Conversion Approach

Not applicable

Error Handling


Error TypeError DescriptionAction Taken

Not applicable


Post-Load Validation

Project Team

Completeness

TaskAction

Verify Count

SyWay I2M Data Team to verify the record count created in target S/4 HANA by accessing post load 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

TaskAction

Conversion Accuracy

Verify that the tables in target S/4 HANA were loaded correctly via SE16 download


Business

Completeness

TaskAction
Verify CountExtract data in S/4 Hana via fiori tile and verify the count

Accuracy

TaskAction
Verify CountExtract data in S/4 Hana via fiori tile and check correct value match.


Key Assumptions

  • Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
  • Project Scoring and Other dropdowns - Investment Classification  Global Hierarchy is in scope based on data design and any exception requested by business.

</END CR359>

See also

Change log

Version Published Changed By Comment
CURRENT (v. 32) Apr 02, 2026 10:28 NADAR-ext, Parvati
v. 35 Apr 02, 2026 10:14 NADAR-ext, Parvati
v. 34 Apr 02, 2026 09:41 CONNELLY-ext, Delia
v. 33 Apr 01, 2026 16:28 NADAR-ext, Parvati
v. 32 Apr 01, 2026 13:37 NADAR-ext, Parvati
v. 31 Apr 01, 2026 13:32 NADAR-ext, Parvati
v. 30 Apr 01, 2026 13:15 NADAR-ext, Parvati
v. 29 Apr 01, 2026 12:18 NADAR-ext, Parvati
v. 28 Mar 26, 2026 14:38 NADAR-ext, Parvati
v. 27 Mar 26, 2026 08:01 NADAR-ext, Parvati

Go to Page History

  • No labels