EHub Training

Technical Design Guideline

Document
Technical Design Guideline Document

Document Control

Revision History

Date Version Revision Description Author

04/01/2019 1.0 Initial draft of Template Govind Bajaj

Document Approval / Sign Off

Name Project Role Signature Date

2/10
Technical Design Guideline Document

Table of Contents

1 OVERVIEW ................................................................................................... 4

3 FLOWGRAPHS IN HANA SDI/SDQ ............................................................. 5

3.1 Package Structure ............................................................................................................................... 5

3.2 Naming Guidelines .............................................................................................................................. 6

3.2.1 Flowgraph.................................................................................................................................... 6
3.2.2 Calculation Views ....................................................................................................................... 7
3.2.3 Data Completeness ...................................................................................................................... 7
3.2.4 Data Quality ................................................................................................................................ 8

4 SAP DS JOBS............................................................................................... 9
4.1 Job Hierarchy ...................................................................................................................................... 9

4.2 DataStores............................................................................................................................................ 9

4.3 Naming Conventions ........................................................................................................................... 9

3/10
Technical Design Guideline Document

1 Overview
Purpose of this document is to provide guidelines for technical design of ETL process for
object conversion using Enterprise Hub (EHub) platform. This includes guidelines for
 Strategy for Extract and Transform in EHub
 Process orchestration of extract and transform using HANA SDI/SDQ flowgraphs
 Information views (Calculation Views) for reporting
 Load of data using SAP Data Services Jobs

2 Typical Extract and Transform Flow in EHub

Data quality and transformation activities are shown in below diagram. It shows the flow
of information and enrichment of data in each step of Extract and Transform process of
Data Migration activity.

Each of the data layers mentioned below are linked to a schema in EHub
 Landing Layer – This corresponds to schemas holding data from source systems.
EHub, at present, has two schemas for holding data from source systems –
ZSLT_SHE and ZST_ZT1
 Staging Layer – This corresponds to schema EHUB_STG. This layer is used for
‘consolidation’ of data from multiple source systems. Usually, output of this layer
is a single table.
 Alignment Layer – This corresponds to schema EHUB_ALG. This layer is used
for storing data associated with data cleansing, data transformation and matching.
Usually, output of transforms will be
o Data Cleansing
 Table for storing Valid records due to completeness check
 Table for storing Invalid records due to completeness check
o Data Matching
 Table for storing the output of match process
o Data De-Duplication
 Table for storing the unique records
 Table for storing the duplicate records
 Preload Layer – This corresponds to schema EHUB_PLD. This is the layer which
holds data for SAP DS to consume. Usually, output of data validation is stored in
two tables
o Table for storing the records which have been validated successfully
o Table for storing the records which have failed validation

4/10
Technical Design Guideline Document

Transform
Process Input Output Schema of Output Table
Data
Consolidation Source Tables <TableName>_Extract EHUB_STG
Data
Cleansing <TableName>_Extract <TableName>_Complete EHUB_ALG
<TableName>_InComplete EHUB_ALG
Data Convert <TableName>_Complete <TableName>_Transformed EHUB_ALG
Data Matching <TableName>_Transformed <TableName>_Matched EHUB_ALG
Data De-Dup <TableName>_Matched <TableName>_Survived EHUB_ALG
<TableName>_Duplicates EHUB_ALG
Data
Validation <TableName>_Survived <TableName>_PLD EHUB_PLD

Note (for Mock Project)

1. Please use schema associated with the user ID assigned to you in HANA (<BODS_USERXX)for all
layers of data
2. Please use survived table as source in SAP DS. In EHub systems we use PLD table but since we
do not have data replication from target to EHub, we will skip this step

3 Flowgraphs in HANA SDI/SDQ

3.1 Package Structure

To distinguish between flowgraphs for transform processes mentioned in above table,
sub-packages are created for each Conversion Object. As an example, for MaterialMaster
conversion object create MaterialMaster as a sub_package and then under this sub
package create below listed packages. The hierarchy of packages will appear as below

5/10
Technical Design Guideline Document

Transform Process HANA Package

Data Consolidation DataExtract
Data Cleansing DataCleanse

Data Convert DataConvert

Data Matching DataMatch
Data De-Dup DataDeDup

Data Validation DataQuality

Note –
For mock project, please create sub-packages under the package assigned to your
HANA user id (EHUB_TRAINING_USERXX)
No Flowgraphs will be created for Data Validation for reason mentioned earlier

3.2 Naming Guidelines

3.2.1 Flowgraph
Naming guideline for flowgraph is shown below

<ConversionObjectName>_<SourceTable/ViewName>_DataTransformProcess

For example
MaterialMaster_MARA_Extract
MaterialMaster_MARC_Extract

6/10
Technical Design Guideline Document

MaterialMaster_MARA_Cleanse

3.2.2 Calculation Views

All HANA information views are created in the package structure EnterpriseHub
Reports as shown below

3.2.3 Data Completeness

For Data Completeness related information views, there is a sub-package called
DataCompleteness.
Data Completeness is based on data output of data cleanse transform process. For each
column marked as mandatory in data mapping sheet, information view should check that
the value in the column is not null or not blank. Calculated measures are created for each
mandatory column – One to check if the value is complete and other is based on if value
is incomplete.

7/10
Technical Design Guideline Document

Naming convention for information views for Data Completeness is

DataCompleteness_<ConversionObjectName>_<Table/View Name>

3.2.4 Data Quality

Information view related to Data Quality measures the quality of data with respect to
configuration and data tables from target system. Values in columns of data marked as
relevant for validation need to be checked for values in corresponding tables in target
systems.
For example,
 value in Plant column in survived table should match with values in T005W table in target.
 Value in material column in survived table should match with values in MARA table in target
Information views for data quality are created under sub-package DataQuality as shown
below

Naming Convention for information views for data quality

DataQuality_<ConversionObjectName>_<Table/View Name>

8/10
Technical Design Guideline Document

4 SAP DS Jobs

4.1 Job Hierarchy

4.2 DataStores
Data Stores created for training user in SAP DS in Training environment are given below
HANA Data Store: EHUB_SOURCE
S4H Data Store: EHUB_TARGET.

4.3 Naming Conventions

Naming Conventions for each object in BODS

Project: PRJ_EHUB _<Username>

Job: JOB_EHUB_<ObjectName>

Workflow/Conditionals: WF_EHUB_<ObjectName>

DataFlow: DF_EHUB_<ObjectName>

9/10
Technical Design Guideline Document

Script: SCR_<Type of work it does>

Ex : SCR_Intializing_Global_Variable>

Staging Tables: STG_EHUB_<Objectname>_<Table_Name>

10/10