SAP BI / Business Objects Architecture

Master data and Transaction data will be extracted from the defined source systems and loaded into the GPMR BI. The
Technology used to extract data from GSAP to GPMR via ETL SSIS will be based on Open Hub Destination(OHD). We have
cubes that are split according to Region and Quarters. We will connect 4 DTPs (as per Quarter cubes) for a region into an
Open Hub Destination, this will dump all the data into a flat file.
The SSIS ETL layer has 2 components- SSIS ETL adapters for extracting data from the flat file and BW Loader for loading data
to GPMR. The SSIS ETL adapter will pull the data from the flat file into an inbound table of SSIS where mapping/transformation
of data with Master reference data will be done. Data will be moved to the outbound table and the SSIS ETL adapter (BW
loader) will load the data to GPMR.
Sequel Server Integration Services Tool (SSIS)
Microsoft SQL Server 2005 Integration Services (SSIS) is the designated Extraction Transformation and Loading tool for
GPMR. SSIS ETL functionality will be utilised to extract, transform and load master data and transaction data from source
systems and stage the data for extraction into GPMR data warehouse layer (SAP BI).It is proposed that the XtractIS BW
Loader will be used to load data from SSIS to GPMR BI. The extraction of data from GSAP to SSIS is done using following
adapters available with SSIS ETL tool.

Master Data (Text and Attributes):

Sales Performance will use ETL SSIS Adapter-Xtract IS Table to load both Master data Text and
Attributes.
Hierarchies:

Sales Performance will use Xtract IS BW Table. Open Hub doesnt support hierarchies at the moment
hence the only option is to use Xtract IS Tables.
Transactional Data:

Sales Performance will use Xtract IS Adapter to extract data from the cubes. GSAP BW will create the
Open Hub Destinations for transactional data flow allowing the use of delta loads.
Change of interface technology on SSIS

Data Harmonization Tool

The Data Harmonization tool will collect master data from GSAP BW and other sources and consolidate the master
data before feeding into SSIS.
DBAT?

DBAT allocations are only for the GSAP countries. The Sales Performance Project will not take on the
creation of any new allocation processes for countries that do not currently have one. If it is deemed
new allocation processes are required, a separate project would need to be initiated and budgeted.

Master Data:

Master data Text and Hierarchies will be extracted from GSAP BI using
ABAP program and output will be a flat file.

Master data Attributes using OHS in the SSIS Integration layer, and then
loaded into GPMR Master data tables(info-objects) using Xtract IS BW
loader.

The Customer master data will be sourced from GSAP. Also legacy
customer data (Non-GSAP) will be send to DHT and then data will be
aligned with GSAP structure and harmonized before sending to GPMR

The master data for some objects will be created as part of the Data
Harmonization Project and maintain by them.

The Product master data will be sourced from the Global Product
Catalogue(GPC).

The SSIS integration layer will pick up these flat files from their specific
location and will load it into the inbound table.

The Master data files will move from the inbound table to the outbound
table and will go through transformation and look up if required

The Data Harmonization Tool will master some master data text,
attributes and hierarchies and will be loaded by the DHT team directly into
GPMR

All the hierarchies will be loaded in GPMR via SSIS and the source for all
hierarchies is GSAP, DHT and GPC.

The list of Hierarchies in scope of SALES PERFORMANCE along with their

sources are listed below.
GSAP
Channel Classification
Customer Sector / Sector Segment (internal business
segment)
NACE Hierarchy (external business segment)

Global Product Catalogue (GPC): Product master data :

The Product master and reference data is sourced from GPC through
the SSIS integration layer. This data comes into GPMR without any
conversion and transformation and is direct mapping to GPMR. The
frequency of the data load from GPC will be monthly. For Sales
Performance, the existing extract for FPS will be enhanced to meet
the requirements for Sales Performance

Design Approach / Solution:

The GPC application will export data into number of flat files having
Product Master Data and these flat files will be picked up GPMR
Integration environment SSIS.

These files will be validated and then subsequently loaded into Data
Acquisition layer of GPMR BI environment using Xtract IS BW loader
SSIS component via full load info-packages.

The data is then data is moved to the subsequent master data Info
object tables using DTPs.

Frequency:
Ongoing product master data files will be sent monthly to Global
PMR by 2nd Working day.
Frequency:

PMR by 2

nd

Ongoing customer master data files will be sent monthly to Global

Working day

Data Flow in BI
Master Data and Reference Data (BI Infoobjects)
Master data is the supporting reference data that is required for the reporting purposes. The master data and
the attributes listed will be loaded from GSAP into SAP BI via SSIS ETL after Deployment 1 via the SSIS ETL layer
and would be harmonized if required. In comparison there will be some infoobjects available in GPMR that will
be reused for Sales Performance.
The Master data Text and Attributes will be extracted from GSAP BI using Xtract IS table in the SSIS Integration
layer, and then loaded into GPMR Master data tables using Xtract IS BW loader

GPMR Layer Architecture

The GPMR Sales Performance solution is comprised of 6 layers, each layer providing a distinct function and
enabled through a portfolio of applications as illustrated in the diagram below. This diagram does not represent
the actual cubes and DSOs to be used in Sales performance, and hence only to be used for understanding the
architecture. The focus of this document is the Data Warehouse Layer for Sales performance.

Source System Layer

Integration Layer
Data Warehouse (DWH) Layer
Reporting Layer
Access Layer

The Data flow of Transaction Data within SAP BI adopts the GPMR layered architecture and is comprised of six
distinct layers. Separate Info areas will be created in BI7 for each defined layer / application component.
1.
2.
3.
4.
5.
6.

Data Acquisition Sub-layer

Corporate Memory Sub-layer
Data Propagation Sub-layer
Business Transformation Sub-layer
Dimensional Reporting Sub-layer
Virtual Reporting Sub-layer

Sales Performance BI Layer Architecture

For Sales Performance we have 5 layer architecture as follows
1.

Data Acquisition Layer

(PSA layer in GPMR BI)
The data acquisition layer comprises of a series of Persistent Staging Area. This is first layer in GPMR
that receives data from the SSIS ETL layer. The data transfer from SSIS ETL layer to the data
acquisition layer(PSA) is done with the use of Infopackage in combination with the Xtract IS BW Loader
adapter and subsequent layers are done by DTPs (Data Transfer Process).

2.

Corporate Memory Layer

(DSO layer in GPMR BI)
The Corporate Memory Layer comprises of write optimized DSO and forms the back up for all data. The
data transfer from the PSA layer to the Corporate Memory layer will be done by DTPs (Data Transfer
Process) as per region and currency. If there is any need to look up for historical data then it can be
done at the corporate memory layer rather than going to the source.

3.

Data Propagation Layer

(DSO layer in GPMR BI)
The Data Propagation layer consist of write-optimized DSO which are logically split as per regions,
currency and quarters. The data transfer from the PSA layer to the Data Propagation layer will be done
by DTPs (Data Transfer Process).

4.

Dimensional Reporting Layer

(Infocube layer in GPMR BI)
The Dimensional Reporting layer consist of Infocubes. They are split as per regions quarters and
currency. The data transfer from the Data Propagation layer to the Dimensional Reporting Layer will be
done by DTPs (Data Transfer Process).

5.

Virtual Reporting Layer

(Multiprovider layer in GPMR BI)
The Virtual Reporting layer which consist of multiprovider forms the basis for reporting by logically
grouping the data in all the Infocubes that are assigned to it, thus enabling cross-reporting, example
reporting on Tariff and Allocated data.

For Sales Performance, there is no Business Transformation in Deployment 1 as there are no reporting
requirements and hence the layer is excluded in the Sales Performance Architecture. As reporting requirements
are unknown at this stage we are unable to ascertain if there is a requirement to provide for a
business transformation layer in GPMR BI design. The layer will not be provided for as part of the deployment 1technical build, the design will be re-visited following finalization of reporting requirements.

Description

The original source of master data and hierarchies will be from GSAP BW, OPSM and GPC. The
master data from GSAP and OPMIS/legacy systems will be fed into the data harmonization tool
and the harmonized data will sourced to GPMR via the integration layer of MS SSIS ETL tool. The
master data for product will be sourced from Global Product Catalogue(GPC) as this is where it is
mastered. The extraction of data from GSAP BW to SSIS ETL will be done with Xtract IS adapters.
The list of master data entities is provided in section 3.2.1.

From the SSIS ETL layer the harmonized master data sourced from DHT and the mapped
transaction data will be migrated to the Data Acquisition layer within GPMR BI. The load from
SSIS ETL layer to the Data Acquisition Layer of GPMR will be done using Xtract IS adapter-BW
Loader. The data acquisition layer comprises of a series of Persistent Staging Area.

From the PSA data will be loaded to the data propagation and the corporate memory layer in
parallel. This step loads the transaction data from the PSA to the Data Propagation layer in SAP
BI. This will be a series of write-optimised Data Store Objects (DSO). This layer will be used to
logically partition the data by region and quarters. The Data Propagation layer feeds data to the

Dimensional Reporting layer.

4

The Corporate Memory layer consist of write-optimized data store objects and the data will be
loaded in parallel from the data acquisition layer. The Corporate Memory layer will store a copy
of all the untransformed sourced data thats fed into the Data Propagation layer and will form as
a back-up, recover or source data for any new requirement without having to go back to the
source for the transactional data.

The Dimensional Reporting layer forms the last physical store of data in GPMR BI.

The Virtual reporting layer consist of multiproviders that logically groups underlying infoproviders
from the dimensional reporting layert. It provides for consolidated reporting across the defined
data streams., example reporting on Tariff and Allocated data together in reports or repoting
across multiple quarters within a region. This layer will not physically store data.

The Product master data will be loaded from Global Product Catalogue (GPC) to the SSIS layer via
DHT.

Reporting layer Business Objects and SAP Bex will be used to create BI/BO reports based on the
infoproviders based on the multiproviders within the virtual reporting layer. The list of reports will
be provided in deployment 2 dependent on the reporting requirement.

The GSAP Portal will be the point of access to the Sales Performance community users for the
reports.

Sales Performance Deployment Approach

Overview
The Sales Performance project will be implemented over three deployments which tie in with three different
Global PMR programme releases.

In summary, these are:

1.

Deployment 1: Technical Deployment which will be delivered as part of the GPMR, release 1
timelines. Scope of this deployment is:
a. Build and deploy the BI database and data-model based on the GSAP SP 2.2 solution
b. Design, build and deploy the interfaces necessary to take data from GSAP to GPMR.
c. Design, build and deploy the necessary data extractors from GSAP.
d. Build and deploy interfaces for LPG and Canada
e. Go-live with CoBs: Global Marine, Global Aviation, LPG and Sulphur.
f.
Go-live with Canada
g. Switch off OPSM (decommission all reports, all interfaces, all extracts)
h. Upgrade GPMR data-model to Streamline 2.3

GPMR Sales Performance Reporting: Three Deployment Approach

Deployment 1: Technical Deployment

BI build based on StBC 2.2 data model

GSAP BW Sales Performance Cube data extractors

GSAP to GPMR ETL Interface

Code drop to production but no ongoing data loads; No end user reports

2.

Deployment 2: Phase 1: Cores Sales Performance will be delivered as part of GPMR release 2
timelines. Scope of this deployment is:
a. Build and deploy Core Sales Performance reporting in GPMR (see scoping document)
b. Build and deploy interfaces to the legacy systems (OPMIS, JDE, or SIMON)
c. Decommission OPSM (for local reporting and GPMR type reports and some interface)
d. Go-live with CoBs: Lubricants and the following B2B businesses: Commercial Fuels, Bitumen,
Local Marine and Local Aviation; and Retail
e. Provide harmonised master data through the Data Harmonisation Tool (DHT) project.

Deployment 2: Phase 1

Core Sales Performance Solution based on StBC 2.2 data model

Decommission of OPSM, and build of outgoing to interfaces to systems such as Lubes Data
Mart

Interface to legacy OPMIS

End user Core Sales Performance Reporting

Ongoing load from GSAP BW and legacy environment

CoB: B2B (Commercial Fuels, Bitumen, Aviation (local), Marine (local)), Lubricants

3.

Deployment 3: Phase 2: Additional Sales Performance will be delivered as part of GPMR release 3.
Scope of deployment 3 are:
a. Other lubricant reporting (see scoping document)
b. Target reporting
c. Build and deploy interfaces for LPG and Canada
d. Go-live with CoBs: Global Marine, Global Aviation, LPG and Sulphur.
e. Go-live with Canada
f.
Switch off OPSM (decommission all reports, all interfaces, all extracts)
g. Upgrade GPMR data-model to Streamline 2.3

Deployment 3: Phase 2

Additional Functionality based on StBC 2.3 data model

Interface to LPG systems and Canada

CoB: LPG, Sulphur, Global Aviation and Marine

Various reports:

VP/GM Profitability

Customer Profitability Analysis

Product Profitability Analysis

Customer Profitability Trend Analysis

Product Profitability Trend Analysis

Top XX Customer report

Financial Analysis

Volume Unit of Measure, Currency and Exchange rates, Time Characteristics:

GPMR Sales Performance BI system will only hold Volume in L15 and KGS. Conversion to the
Alternative Unit of Measure will be done within the reporting layer.

Unit conversion will be undertaken in the reporting layer utilising SAP BI conversion types based on the
central units of measure table. Target UOM will be specified by the end user at run-time via a sap BI
reporting variable. A customer exit variable will read the central unit of measure table to identify the
dimension of the target UOM, and select the stored quantity corresponding to the dimension (L15 or
KGS) as the basis for the conversion

The design accommodates to store local currency only (country specific) in the BI system. Reporting
will be possible in local currency and USD. The user will have the option to choose from this list of
target currencies at the time of running the reports. The currency conversion will be applied at query
runtime for local to USD.

The Sales performance reports will be mainly reported on Calendar Month time characteristics