17362 – KSO SAP HANA

SAP BODS Support Document

Author: Satabdi Lal

Sweekriti Lama
Sayani Bhattacharyya

Version: 0.1
Status: For approvals

Kingfisher Group Confidential

1. Overview:
The KSO HANA project is a Proof of Concept (POC) to deliver Sales, Demand, Stock
and Order Forecasting for the Kingfisher Sourcing Organisation (KSO). Here in this
project, we have covered the data being sourced from the three countries, namely
UK B&Q, POLAND and HONG KONG.

2. ETL System Overview:

Integration is done using Extract, Transform and Load Tools (ETL) and the tool used
for integration is SAP Business Object Data Services (BODS).

2.1. System Design:

2.1.1. Source Systems:
-----------------------

Data would be extracted from various source systems for the three countries as
mentioned below:

For United Kingdom:

----------------------------
 SAP BW System
 SAP BI System

For Poland:
---------------
 SAP F&R Casto System
 Casto Poland ECC6 System for RFC Call
 Casto Poland BI System

For Hong Kong:

---------------------
 Source Files provided by Apex

2.1.2. Design Approach:

---------------------------
  The data from the source systems are extracted using SAP BODS ETL Tool.
 In the BODS jobs data is being transformed as per the logic provided in the
Integration design document (IDD) before loading the same into the target
system. Also, validation process is incorporated to filter out unwanted data.
 The transformed data is then stored in the SAP HANA Staging Tables (target
system for BODS) and date-time stamped pipe separated target flat files(with
the same data) are also created which are stored in the following server path :
(The production path for all the countries are yet to be provided).
 For UK: Path yet to be provided
 For Poland: Path yet to be provided
 For Hong Kong: Path yet to be provided.
 The date-time stamped flat files are created with a motive to maintain the data
back up for each run.
 After populating the staging target HANA tables and after creating the date-
time stamped target flat files, the control table,
KFGP_T_BODS_LOAD_CONTROL and a control file,
KFGP_T_BODS_LOAD_CONTROL (Path: yet to be provided) gets loaded
with the name of the table that got populated during the job run along with the
time of completion.

2.1.3. BODS Job Design:

---------------------------

The BODS jobs are built following the below mentioned approach:
 In BODS, the only executable unit is a job.
 Inside each job, there is a script, which is used to create the name of the
date-time stamped target Flat file.
 Each job has a work-flow, which is made as a recoverable unit i.e. upon the
failure of a job, it will get executed from that point of failure, the next time we
re-run the job.
 Inside each workflow, there are two data-flows, whose functionality is as
mentioned below:
 The first dataflow is to populate the staging target table with the data from
the source systems.
 The second dataflow is to populate the Control Table and the control file,
which maintains the name of the table that got loaded during the run along
with the date and time of completion.
 However, there is another dataflow in a couple of jobs (which happens to
be the first dataflow in some workflows like
JOB_UKBQ_KSO_HANA_Load_COST_and_RETAIL_PRICE) that
behaves as the intermediate dataflow to do some intermediate
calculations.

 Inside each dataflow, several components have been built so as to suffice the
extract, transform and load logic in the job.
 Most of the jobs are Full load. But there are a couple of jobs, which would
load the delta data into the target HANA Staging table, after comparing the
previous data with the current. The delta data would be provided by the
source systems.
 For a couple of jobs for Poland, we have made use of the RFC Calls to the
ECC6 Source systems. In these jobs, there are a couple of jobs, which uses
parameterised Functions and the rest are non-parameterised ones.
 Function Call with Parameters:

Input Parameters to be passed to the Function Module:

Passing Parameters:

Function Module Call in BODS:

 Function Call without Parameters: