Open Hub

Know How Network

May 1, 2003

Bryan Katis
Platinum Consultant
BW RIG, SAP Labs
 Agenda
2

Overview: BW Open Hub Service

Open Hub Features

InfoSpoke Details

Outlook

Q&A

 SAP AG 2003, Open Hub, B. Katis 2

 The Corporate Information Factory –
Directly supported components of SAP and SAP BW3
DSS Applications APO
Sources Departmental Data Marts BW CRM
mySAP Acctg Finance
ERP
Marketing Sales
ERP SEM
Others ERP
CRM
ETL
Staging Area

Changed
eComm.
Data

EDW Bus. Int.

Exploration
Global warehouse/
ODS data mining
ERP
Corporate Oper.
Applications
Mart cross media
local Granularity
Storage mgr
ODS Manager

Session Near line

Analysis Storage
E-Analytics
Dialogue
Manager
Cookie
Cognition Web Logs
Preformatted
Internet dialogues Source:Bill Inmon
 SAP AG 2003, Open Hub, B. Katis 3
 The Corporate Information Factory –
BW Open Hub Service 4
DSS Applications
Departmental Data Marts
Open Hub Service Acctg Finance
ERP
Marketing Sales
ERP
ERP
CRM
ETL
Staging Area

Changed
eComm.
Data

EDW Bus. Int.

Exploration
Global warehouse/
ODS data mining
ERP
Corporate Oper.
Applications
Mart cross media
local Granularity
Storage mgr
ODS Manager

Session Near line

Analysis Storage
Dialogue
Manager
Cookie
Cognition Web Logs
Preformatted
Internet dialogues Source:Bill Inmon
 SAP AG 2003, Open Hub, B. Katis 4
 Open Data Warehouse Architecture
5

 SAP AG 2003, Open Hub, B. Katis 5

 SAP BW Open Staging and Open Hub Services
6
BW
mySAP.com Server
Applications BW
Server
e-Business
InfoCubes
External
Flat File DataMart

EDW
Relational
DB Link BW Operational Data Store Relational
Table
ETL Master Data
Tools
Flat
File
Data
Provider ODS Objects
ODBO

 SAP AG 2003, Open Hub, B. Katis 6

 Open Hub Service - Details
7
BW
Server
Relational
Table
External
DataMart
InfoCubes
...
...

Flat  Controlled distribution

File of consistent data
 Target: file or DB table
 Central monitoring
Master Data
 Select filter criteria and
columns
 Scheduling
ODS Objects
 Full or delta mode

 SAP AG 2003, Open Hub, B. Katis 7

 Information Distribution - Scenarios
8
Analytical
Application
Sales
Data Mart
Regional
SAP BW Data Mart

BW Data Mart

Legacy
Application

BW Data Mart Open Hub Service

BW Open Hub Platform

BW as an Information Hub
SAP BW
Controlled Distribution
of consolidated and
integrated data

 SAP AG 2003, Open Hub, B. Katis 8

 Open Hub Service - Details
9
Data transfer in Open Hub Service
Data Marts
BW
DB Table BW S-API
InfoCubes /BIC/0H….

DB connect type Other Data

Push
functionality warehouses/marts
Pull
ODS
Open Hub
Pull
Service

Pull Push
Other system
(ERP, CRM, etc)
Master Data

Flat file
.csv

 SAP AG 2003, Open Hub, B. Katis 9

 Open Hub - Functional Details
10
Meta object InfoSpoke for asynchronous data transfer of mass data
 Modelling
 Data Sources: InfoCube, ODS Object, and Master Data (Attributes and
Text)
 Full and Delta Processing (Delta for InfoCubes and ODS Objects)
 Distribution targets: File (.csv format), BW DB Table
 Aggregation, Selection, Transformation
 Scheduling
 Direct Scheduling
 Process Chain Integration
 Monitoring
 AWB-Monitor Functions
 Technical Realization
 Optimized Read Access for Star Schema Transformation

 SAP AG 2003, Open Hub, B. Katis 10

 Model: Design-Time
11
BW
Variant
Scheduler Selections for data source

Periodicity,
Starting condition

Process
Reference to Data Source
Reference to Transformation
Reference to Data
Extern

Data Source Transformation Data Target

Metadata,
Metadata,
Selectabilty,
Data
Data

 SAP AG 2003, Open Hub, B. Katis 11

 Model: Run-Time
12
BW
Request
Selections for data source

Request Broker Log/Monitor

Reference to Data Source
Reference to Transformation
Reference to Data
Extern

Data Source Data Target

Data Data package(in) Data package(out) Data

Transformation
 SAP AG 2003, Open Hub, B. Katis 12
 Accessing the Open Hub Service
13

Transaction RSBO or via

AWB Tools menu

 SAP AG 2003, Open Hub, B. Katis 13

 InfoSpoke Definition – General tab
14
Data Source
 InfoCube
 ODS Object
 InfoObject (Attributes)
 InfoObject (Texts)

Destination
 For Open Hub use only
 Uses InfoSpoke name by
default
 The Open Hub Destination
(as an object) is generated
during the activation

Extraction Mode
 Full or Delta
 Records per Data Package

 SAP AG 2003, Open Hub, B. Katis 14

 InfoSpoke Destination
15
Destination Tab
 Automatically
generated during
destination activation

Destination target options

 .csv file on front end or
Application Server
 DB table name:
/BIC/0H<InfoSpoke
Destination>

 SAP AG 2003, Open Hub, B. Katis 15

 Special Features with Database Table Extractions
16
Deleting Tables Before Extraction
 With an extraction to a database table, you have the option of getting the
history of the data or only storing the new data in the table. Choose Delete
Table Before Extraction when defining your destination if you want to
overwrite the fields. In this case, the table is completely deleted and
regenerated before extraction takes place. We recommend you use this mode
when the table is not to contain a history of the data. If you do not select this
option, the extracted data records are added to the database table using an
‘INSERT’. We recommend you use this mode when the history of the data is
to be retained.

Key Fields from the Table

 With extractions to a database table, you have to note that the generated DB
table can have a maximum of 16 key fields. Therefore, check whether your
field list includes more key fields. If this is the case, you can set the Technical
Key indicator. A key is then added, consisting of the technical fields
OHREQUID (open hub request SID), DATAPAKID (data package ID), and
RECORD (running number of a data record to be added to the table within a
data package). These fields then display the individual key fields for the table.

 SAP AG 2003, Open Hub, B. Katis 16

 Scenarios
17
Using a target table with a technical key would be useful in the
following instances:
 Delta extraction from ODS objects: the data is read in the change log,
in which several records with different RECORDMODEs can exist for
a specific, semantic key (after/before image). In general, extracting to
a table with the semantic key from the ODS object leads to duplicate
records and, ultimately, to a short dump.
 Extracting in full mode to a table that does not need to be deleted
before the extraction. If, for an extracted record, one already exists
with the same key, a short dump occurs due to duplicate records.
 If the source has more than 16 key fields, no DB table can be created
with these key fields. In this case, therefore, the table has to include
a technical key.

 SAP AG 2003, Open Hub, B. Katis 17

 Defining the Extract Structure
18

Define
Aggregation Level

 SAP AG 2003, Open Hub, B. Katis 18

 InfoSpoke Definition – Selection
19

Excludes
possible
as well

 SAP AG 2003, Open Hub, B. Katis 19

 Transformation via Business Add-In (BAdI)
20

Enhanced
User Exit
Handling

 SAP AG 2003, Open Hub, B. Katis 20

 Implementing BAdI’s
21

Enter short text for the

implementation.

If you do not specify an

InfoSpoke under
‘Defined filters’, then
this implementation is
valid for all InfoSpokes.
This means that this is
called up for all
InfoSpokes during the
extraction.

 SAP AG 2003, Open Hub, B. Katis 21

 Implementing BAdI’s (continued)
22
Choose Implementation
type: ABAP Code or
Formula Builder

Double-click on
Transform method to
enter ABAP code.

 SAP AG 2003, Open Hub, B. Katis 22

 Change an InfoSpoke’s Extraction Layout
23
You can manipulate
the Target Structure’s
field order.

Note: Do not remove

or change any of the
structure’s fields or
attributes otherwise
extraction errors will
occur.

Check the paper

‘How-To…change an
InfoSpoke’s
extraction layout’ for
more detailed steps.

 SAP AG 2003, Open Hub, B. Katis 23

 Open Hub Process Chain Integration
24

Designing
complex Dataflow
Processes

 SAP AG 2003, Open Hub, B. Katis 24

 InfoSpoke – Monitoring
25

Monitoring
Runtime Results
in
Detail

 SAP AG 2003, Open Hub, B. Katis 25

 Open Hub Delta Handling
26
You can deactivate the delta administration. Then an additional delta
request is not possible. At the same time, the status of all source
requests that have already been read is reset to Not Yet Read.

The delta administration is also deactivated if one of the following

events occurs:

 A request that has already been

extracted is deleted in the
source object.
 A request that has not yet been
extracted is condensed in the
source object.

You can reactivate the delta

administration. Then a delta
request is once again possible.

Note: Delta requests should be

reset individually rather than
deactivating all deltas at once!
 SAP AG 2003, Open Hub, B. Katis 26
 Open Hub Destination Table – DDIC Description
27

Meta Data Information

for
Extraction Table

 SAP AG 2003, Open Hub, B. Katis 27

 Open Hub Destination Table – Contents
28

Extraction Format
DB Table

 SAP AG 2003, Open Hub, B. Katis 28

 Open Hub Destination File – Description and Data
29
Meta Data Description File
(S_DEST01.TXT)

Data File
(DEST01.CSV)

 SAP AG 2003, Open Hub, B. Katis 29

 Open Hub Scenario for one step data delivery
30
SAP BW

DataStage Jobs

+
ODBC Stage

ODBC Stage
InfoSpoke

How to implement:
•DataStage triggers InfoSpoke via
RDBMS
API and then starts DS Job Non SAP
DB
• BW Process Chain step launches
InfoSpoke delivery and then starts
DS Job
(possible via ABAP process type)

 SAP AG 2003, Open Hub, B. Katis 30

 Changing Open Hub Destinations for Files
31
Whenever I save a file to the Application Server it always gets sent to the
work directory. How can I change the path my files get sent to on the
Application Server?
The default separator for .csv files is a semicolon. How can I change this
to something else like a colon, comma, etc.?
The value that is used for the Field separator is a global setting
maintained in the IMG. Transaction SPRO -> Business Information
Warehouse -> Links to Other Systems -> Link Between Flat File and BW ->
Set options for uploading flat files.

 SAP AG 2003, Open Hub, B. Katis 31

 Changing Open Hub Destinations for Files (cont.)
32
Solution: Go to transaction SE11 or SE16, and choose table RSBFILE.
Select the record based on the OHDEST field and OBJVERS = ‘A’, and
then ‘Change’.

NOTE: When InfoSpokes are transported, the system will use the default
separator (from the IMG) and the work directory path (DIR_HOME) from
the target system. So you would need to manually change this table in
each of the target systems.

 SAP AG 2003, Open Hub, B. Katis 32

 Transports
33
InfoSpoke definitions and the Open Hub Destinations are
transportable using the Transport Connection. They are also both
changeable in the target systems via the Object Changeability
option. This adds the flexibility of changing file paths for the
destinations, or selection criteria for an InfoSpoke for each target
system, for example.

 SAP AG 2003, Open Hub, B. Katis 33

 Open Hub Pricing
34
Whenever you extract data from the SAP BW environment into
3rd-party target systems your SAP BW Enterprise Data Warehouse
functions as an ‘Open Hub Platform’.

The Open Hub Service is one tool among other functions to

accomplish this task. Additionally, DataBrowser functionality
(ListCube transaction) or CRM interfaces can also be used to
export data, and many other options are possible.

Extracting data from SAP BW by any means requires additional

licensing!

For additional pricing information please contact your SAP

representative.

 SAP AG 2003, Open Hub, B. Katis 34

 Outlook beyond BW 3.x
35
Logical file name handling in order to enable full access to the file
system of the Application Server

Separator maintenance in the InfoSpoke definition

Variables used in Selection

Additional Data Sources like BEx Query and Hierarchies

Additional destination formats like ASCII and XML

Remote access to external database tables

Sorting of fields for the output table (without BAdI workaround)

Transformation Library integration for transformations

Deltas available for additional Data Sources

 SAP AG 2003, Open Hub, B. Katis 35

 Further Information
36
 Public Web:
www.sap.com  Solutions  Business
Intelligence

 SAPNet:
http://service.sap.com/bw

http://help.sap.com -> SAP NetWeaver -> SAP

Business Information Warehouse

Documentation Enhancement
http://service.sap.com/bw -> Documentation

How-To Guide
http://service.sap.com/bw -> Services &
Implementation -> HOW TO … Guides -> Guide
List BW 3.x
 SAP AG 2003, Open Hub, B. Katis 36
 Summary
37
 Openness to extract data from BW
 All BW data objects are supported for
extraction
 Delta tracking for each target system
 Scheduling and central monitoring

 SAP BW can serve as an enterprise

information hub (EDW) and feed data
to any downstream system

 SAP AG 2003, Open Hub, B. Katis 37

 Questions
38

Q&A

 SAP AG 2003, Open Hub, B. Katis 38