1. SAP Business Information Warehouse (SAP BW) PART 3 (Data Staging)
May 2004
Author: Arthur X. Wang

2. SAP Business Information Warehouse (SAP BW)
SAP BW Architecture
Source Layer
SAP BW layer
Presentation layer
How to write ABAP routines for ETL
Warehouse Management
Data Marts and Open Hub Services
Practice Test

3. SAP BW Technical Architecture
Third-Party Tools
BEx Analyzer (Excel)
BEx Browser (Web)
SAP GUI (infoSetQuery)
PRESENTATION LAYER
OBDO
OLAP BAPI
OLAP BAPI
OLAP BAPI
ADMINISTRATOR WORKBENCH
OLAP Processor
BW SERVER
Database & Application servers
Metadata
Repository
ODS
infoCube
Data Target
Update Rules
Master Data Tables
(/H/ A/ /T, etc)
Communication Structure
infoSource
PSA
Transfer Rules
Transfer Structure
Transfer Structure
Replication
Transfer Structure
SOURCE SYSTEM
Extract Rules
Data Source
Extract Structure
ALE TRFC
RFC & ALE TRFC
Staging BAPI
Metadata
R/3 Master
Attributes
Text
Hierarchies
R3 Application
BW ODS Cube
Metadata
R/3 Master
Data Providers
Flat File
Master Data
Other ETL tools
SAP R/3 Source System
Non-SAP R/3 Source System

4. SAP BW Architecture Presentation Layer BW Server Source System
Report definition and web reporting
Data Analysis in BEx Analyzer and Web browser plus integration of analytical applications into mySAP enterprise portals
Organization of reports
BW Server
SAP BW database server
Metadata
Staging engine
Application server
OLAP processor
Administrator Workbench
Data management
Monitoring
Scheduling
Data extraction
SAP BW extractors in mySAP.com components
Openness to external system
Integration of extraction, transformation, and loading (ETL) tools.
Source System
SAP OLTP source system
Non-SAP OLTP source system

5. Communication Technologies in SAP BW
API (Application Programming Interface)
Common set of parameters needed to connect the communication between programs.
Interfacing source system and data access software (BEx) with BW.
In SAP BW, APIs are closed to third-party programs.
BAPI (Business Application Programming Interface)
Methods to expose functionality embedded within SAP BW.
Usually using existing ABAP functions, such as function modules, transactions, and dialog modules
Open to third-party software.
Two Types of BAPIs in SAP BW:
Staging BAPI: facilitate the integration of non-SAP R3 data in SAP BW.
Data Access BAPI: use with ODBO to support the access and analysis of data from SAP BW with external methods to complement SAP BW BEx reporting.
SAPI (Service Application Programming Interface)
An SAP-internal component that is delivered as of Basis Release 3.1i
Between mySAP.com components and SAP BW

6. Communication Technologies in SAP BW
ALE( Application Link Enabling)
Used to extract data from SAP and non-SAP source system into BW.
Communication between logical systems. (The logical systems can be SAP R3, SAP R2 or non-SAP systems)
EDI (Electronic Data Interchange)
Communication between SAP R/3 , SAP R/2 and non-SAP system.
IDOC (Intermediate Document)
SAP standard format for electronic data interchange between systems.
In SAP BW, IDOC is a data container for data exchange between SAP systems based on ALE or between SAP systems and non-SAP systems based on EDI.
The limit of file size is 1000 bytes
Data can not loaded into PSA using IDOCs (ALE)
TRFC ( Transactional Remote Function Call)
An SAP interface protocol.
Used to extract data from source system to BW.
TRFC supports a maximum of 1962 bytes and 255 data base fields.
Data can be stored in PSA.
improved performance when loading.
API to access data stored in the ODS (read and update)
Possibility of synchronizing infoSources.

7. Communication Technologies in SAP BW
DB Connect
A tool to allow data access from remote relational database management system(DBMS).
Be able to access Oracle, MS SQL server, DB2, Sybase, etc. (Not MS Access)
XML (eXtended Markup Language)
XML-formatted documents can be sent to SAP BW through its staging engine.
XML data load process is designed to move small datasets using Simple Object Access Protocol(SOAP) services provided with the SAP Web Application server.
ODBO (Object Linking and Embedding DB for OLAP)
A set of Component Object Model(COM) objects and interfaces that extends OLEDB to provide access to multidimensional data structure.
Communication between providers and consumers of multidimensional data.
Open to third-party vendor and customer developers.
RFC (Remote Function Call)
An interface technique/ tool that enable you to call and execute predefined functions in a remote system or even in the same system.

8. Communication Technologies in SAP BW
Data Transfer
Data Access
ODBO X
BAPI
Staging BAPI
Data Access BAPI
ALE / EDI
Using IDOC
IDOC
Using ABAP
TRFC
XML
DB Connect

9. Source Layer Source Systems Data Source (Source) SAP Source System
SAP R/3 (Transaction data, master data and metadata)
Other SAP BW systems (as data mart)
SAP supplied “mySAP” and new products,such as APO, CRM,SEM, etc…
Non-Sap Source System
Flat files
Third-Party source systems
Information providers.Such as A.C. Nielsen, Dun & Bradstreet
Extractor providers, such as infomatica, etc.
OLTP/Legacy systems (e.g. Sibel, PeopleSoft, custom databases, etc.)
SAP R/2
Data Source (Source)
A collection of data fields.
Describes a type of infrastructure that allows the transport of information between an inbound data source (e.g. OLTP, flat file, etc) and SAP BW system
Combination of extract and transfer structure of the source system (OLTP) and the transfer structure on SAP BW.

10. Source Layer Extract Structure Extract Rule
A record layout of infoObjects
No extract structure required for flat files on the source system side.
Extract Rule
Used to define how the data will be moved from extract structure to transfer structure.
Transfer Structure (Source System)
A record layout of selected data fields from extract structure of the source system.
Link to infoSource via transfer rules
Not required for flat file upload.
Replication
A process to create the same transfer structure in SAP BW and make SAP BW aware of a specific data source.
Not required for flat file DataSource.

11. SAP BW Layer SAP BW Database server Application server
Metadata
Staging engine
Application server
OLAP processor
Administrator Workbench
Data management
Monitoring
Scheduling
Data Extraction
SAP BW extractors in mySAP.com components
Openness to external systems
Integration of extraction, transformation, and loading (ETL) tools.

12. Components in SAP BW Layer
DataSource
infoSource
Transfer Structure
Transfer Rules
Communication Structure
Update Rules
Data Target
ODS
PSA
Master Data Table
Metadata Repository
OLAP processor

13. SAP BW Layer DataSource(Replica) infoSource Application component
Refer to both extract structure and transfer structure of both source layer(OLTP) and BW systems
infoSource
A collection of infoObjects that logically belongs together as a unit.
Equivalent of a communication structure
Two types of infoSource
Master Data (Attribute, Text and Hierarchy)
Transactional Data
Relationship of infoSource with other SAP BW objects:
infoSource 1:1 application component
infoSource 1:M DataSources
infoSource 1:M Source Systems
Application component
A folder in SAP BW administrator Workbench (AWB) used to regroup infoSource objects that are logically related.

14. SAP BW Layer Transfer Structure (Target) Transfer Rules(Target)
For flat and non-SAP source systems
Manually defined on SAP BW side to match the data fields in source system
For Master Data, data field names are defined other than infoObjects.
For SAP source systems
Automatically created by replication.
Copied from the transfer structure from source system
Transfer Rules(Target)
Used to define how the fields of transfer structure are assigned to the infoObjects of communication structure.
Connect transfer structure and communication structure.
There are 4 types of transfer rules:
Field to Field
Fixed value
Formula
Local transfer routine using ABAP.

15. SAP BW Layer Communication Structure Update Rules
A record layout of infoObjects that defines the data provided to the infoCube.
Independent of source system.
Contains all the infoObjects that belong to an infoSource
One communication structure can have multiple DataSources.
Update Rules
Used to define the way in which data from an infoSource are mapped/transferred and loaded into the characteristic and key figures fields of a particular data target.
Types of update rules:
Field to field
Routine using ABAP
Automatic reading of master data attribute of a characteristic of the infoSource
Table look-up
Return table
Start Routines ( for more complex computation)
For characteristic only, there are two more update rule types:
Constant
Initialization value

16. SAP BW Layer Data Target ODS
The object on which transaction data are to be moved on the SAP BW system.
Can be infoCube or ODS
There are four methods to update the data targets in SAP BW:
Update PSA, then data target
Update PSA and data targets in parallel.
Update PSA only. (Skip infoCube or ODS)
Update data target only (skip PSA).
ODS
An optional component in SAP BW.
An intermediate store for data consolidation, cleansing and staging purposes.
Merging data from different infoSources
To satisfy queries that require more detailed data than stored in the infoCube
Contains non-aggregated detailed data.
Overwrite capability for key figures and non-key characteristics.
Ability to drilldown to get more details from infoCube to the ODS using RRI(Report-to-report) interface.
Delta upload is supported as follows:
* ODS to ODS * ODS to infoCube * ODS to PSA

17. SAP BW Layer

18. SAP BW layer PSA (Persistent Staging Area)
A holding area of raw data (master & transactional).
Contains detailed requests in the format of the transfer structure.
Contain data in original context and format. (inbound data go to PSA before any transformation can take place)
Data modification in PSA is allowed except for record deletion.
Addition of data to PSA is possible, but there is no overwrite capability in the PSA
IDOC can not use PSA. And it is not possible to use PSA to load hierarchy data.
You can NOT report against the data in PSA using standard reporting tools..
The architecture of PSA is based on the following:
SAP BW can have multiple PSA if necessary, but only one PSA per transfer structure.
Updates to PSA and infoCube(s) can run sequentially or in parallel.
Data in PSA are based on transfer structure. (not transformed by the transfer rules)
PSA is defined according to the DataSource and source system.
PSA is source system dependent.
PSA uses the key fields request number, packet number, and record number (Request number is not visible except in the change log)
PSA Partitioning is supported as of release 2.0B. Partitioning of PSA needs to occur before data are loaded into it.

19. SAP BW layer Metadata Repository
Business and technical metadata.
Business metadata include definitions, descriptions, and rules used for reporting.
Equivalent of data element and domain in SAP R/3`s Data Dictionary.
Where data are referenced in Sap BW (by default)
Structure
Transact ion Data
Master Data (Attr.)
Master Data (Hier.)
Master Data (Text)
Other
Communication X
Transfer Structure
PSA
ODS
infoCube
BDS(Business Document Service)
Doc., Web templates, etc.
MetaData Repository
Metadata
BI table (/m)
BI table (/t)
BI table (/h)
Master tables (/p,/q,/x,/y)

20. Presentation Layer Presentation layer is used for:
Reporting definition and web publishing
Data analysis in BEx Analyzer and web browser plus integration of analytical applications into mySAP Enterprise Portals
Organization of reports.
Presentation layer includes:
Business Explorer (using OLAP BAPI)
BEx Browser
BEx Analyzer (Including BEx Map-GIS)
SAP GUI (through infoSet queries)
Web Browser
Third-Party tools (using ODBO or OLAP BAPI)

21. Presentation Layer

22. Data Staging Process What is data staging? Staging Scenarios:
The process of extracting and transferring cleansed data from the transfer structure to the communication structure using transfer rules
Staging Scenarios:
Direct Staging
Update from Master Data into an infoObject without using Update Rules
Data Targets: Only for Master
Attributes
Text
Hierarchies (No transfer rule applied)
Flexible Staging
Update into any data target using communication structure and update rules
Data Targets:
InfoCube
ODS
infoObject(Attributes and Text)

23. Staging Scenarios Differences between master and transaction data
Master Data
Transaction Data
PSA usage
Possible
Storage
Master tables
infoCube, ODS, PSA
Transformation & Aggregation
Usually NOT required
Usually required
Staging Scenario
Direct Staging & Flexible Staging
Flexible Staging
Transfer Structure
Define Data Field name (flat file)
Define infoObject

24. Interfaces for Data Extraction
BW Service Application Programming Interface (SAPI)
An SAP-internal component that is delivered as of Basis Release 3.1i
Between mySAP.com components and SAP BW
Business Application Programming Interface (BAPI)
Methods used for structured communication
Between SAP BW and external systems
Both Data providers and ETL tools use this interface
DB Connect
A tool to allow data access from remote relational database management system(DBMS).
Be able to access Oracle, MS SQL server, DB2, Sybase, etc. (Not MS Access)
FILE
CSV
ASCII
Simple Object Access Protocol (SOAP)
To read XML and store it in a delta queue in BW. The data can then be processed further with a corresponding DataSource and SAPI.

25. ABAP Programming for ETL
What is Exits
General ABAP Syntax and Data Types
Program Structure for Update Rule
A Sample Program of Update Rule
Program Structure for Transfer Rule
A Sample Program of Transfer Rule
ABAP Workbench Tools
Sample Report Program

26. What is Exits? SAP Exits User Exits Customer Exit Start Routine
An SAP exist is an enhancement technique that allows you to add additional functions to the SAP standard code and programs.
User Exits
A user exit is a point in a SAP program supplied by SAP where an ABAP program can be called.
Customer Exit
A customer exit is a point in an SAP program where you can add a non-standard custom enhancement.
Start Routine
A user exit that can be executed before update rule starts.
Can be used to generate internal tables
No return value in the routine

27. General ABAP Syntax ULINE. TABLES bw_carrier.
DATA wa_bw TYPE bw_carrier.
PARAMETERS pa_car TYPE scarr-carrid.
START-OF-SELECTION.
* Sample program to read data from database table SCARR
SELECT SINGLE * FROM scarr
INTO CORRECPONDING FIELDS OF wa_bw
WHERE carrid = pa_car.
IF sy-subrc = 0.
MOVE-CORRESPONDING wa_bw TO bw_carrier.
CALL SCREEN “Process screen 100
MOVE-CORRESPONDING bw_carrier TO wa_bw.
WRITE wa_bw-carrid COLOR COL_KEY.
ULINE.
WRITE:/ wa_bw-carrname,
wa_bw-currcode.
ENDIF.

28. Data Types in Program
TYPES: <user_defined_type> TYPE <type>.
DATA: <data_object> TYPE <type>.
Pre-defined types:
C: Character
N: Numeric Text
D: Date (YYYYMMDD)
T: Time(HHMMSS)
X: Byte(heXadecimal)
I: Integer
P: Packed Number
F: Floating Point Number
STRING: Character String
XSTRING: String of bytes (X String)

29. Data Declaration TABLES: <table-name>.
DATA: <varname> LIKE <object-name>.
DATA: <varname> TYPE <type>.
DATA <itab> TYPE <itabtype> |WITH HEADER LINE|
DATA: BEGIN OF <itab> OCCURS 0,
FLD1(X1), ``X1 is the length of field …
FLDn(Xn), ``Xn is the length of field
END OF <itab>.
TYPES: <User-defined-type-name> TYPE <type>.
CONSTANTS <constants> TYPE <type> VALUE <literal>.
PARAMETERS: <Varname>.

30. Program Structure for Update Rule
PROGRAM UPDATE_ROUTINE.
*$*$ begin of global - insert your declaration only below this line *-*
* TABLES: ...
* DATA: ...
*$*$ end of global - insert your declaration only before this line *-*
FORM compute_data_field
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING COMM_STRUCTURE LIKE /BIC/CS2LIS_01_S001
RECORD_NO LIKE SY-TABIX
RECORD_ALL LIKE SY-TABIX
SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BIC/VSDDEMO2T-CRMEM_CST
RETURNCODE LIKE SY-SUBRC
ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update *
*$*$ begin of routine - insert your code only below this line *-*
* fill the internal table "MONITOR", to make monitor entries
* result value of the routine
RESULT = .
* if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
* if abort is not equal zero, the update process will be canceled
ABORT = 0.
*$*$ end of routine - insert your code only before this line *-*
ENDFORM.

31. Program Structure for Transfer Rule
PROGRAM CONVERSION_ROUTINE.
* Type pools used by conversion program
TYPE-POOLS: RS, RSARC, RSARR, SBIWA, RSSM.
* Declaration of transfer structure (selected fields only)
TYPES: BEGIN OF TRANSFER_STRUCTURE ,
* InfoObject 0WBS_ELEMT: CHAR
POSID(000024) TYPE C,
…. ….
END OF TRANSFER_STRUCTURE .
* Global code used by conversion rules
*$*$ begin of global - insert your declaration only below this line *-*
TABLES: /BI0/PWBS_ELEMT.
DATA: ZPtype like /BI0/PWBS_ELEMT-PS_PRJTYPE, "project type
*$*$ end of global - insert your declaration only before this line *-*
FORM COMPUTE_/BIC/ZPW_WACT
USING RECORD_NO LIKE SY-TABIX
TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
G_S_MINFO TYPE RSSM_S_MINFO
CHANGING RESULT TYPE /BIC/OIZPW_WACT
G_T_ERRORLOG TYPE rssm_t_errorlog_int
RETURNCODE LIKE SY-SUBRC
ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel datapackage
*$*$ begin of routine - insert your code only below this line *-*
… INSERT YOUR OWN CODE …
* returncode <> 0 means skip this record
RETURNCODE = 0.
* abort <> 0 means skip whole data package !!!
ABORT = 0.
*$*$ end of routine - insert your code only before this line *-*
ENDFORM.

32. ABAP Report Program Structure
REPORT <Program-Name>.
Data Declaration
TABLES: <table name>.
TYPES: <user-defined-type> TYPE <type>
DATA: <data-object> TYPE <type> , … , <Varname> like <data-object>.
Selection Screen layout definition
SELECTION-SCREEN BEGIN OF BLOCK BLK1 WITH FRAME TITLE TEXT-S01.
PARAMETERS: P1 LIKE DEFAULT `Default Value`, … … Pn LIKE DEFAULT `Default Value`.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: xlist AS CHECKBOX DEFAULT ` `.
SELECTION-SCREEN COMMENT X1(Y1) TEXT-T01. ``X1 = cursor position, Y1=length …
SELECTION-SCREEN COMMENT Xn(Yn) TEXT-T0n. ``Xn = cursor position, Yn=length
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK BLK1.
… …
SELECTION-SCREEN BEGIN OF BLOCK BLKn WITH FRAME TITLE TEXT-S0n.
SELECTION-SCREEN END OF BLOCK BLKn.
INITIALIZATION.
AT-SELECTION.
START-OF-SELECTION “Program Main Body
PERFORM <sub-program>
FORM <sub-program>.
Local Data Declarations.
… …
ENDFORM.

33. Create Custom Table Tcode: SE11 Database Table Name: Zxxxxx
Delivery Class: C
Data Browser/Table View Maint: Display/Maintenance Allowed
Fields, Data Elements and Keys
Maintain Technical Setting:
Data Class: APPL1
Size Category: ( 0 – 68,000 )
Buffering: Not allowed.
Activate
Table Maintenance: Tcode: SE16

34. ABAP Workbench Tools ABAP Editor: SE38 ABAP Dictionary: SE11
Function Builder: SE37
Class Builder: SE24
Object Navigator: SE80
Menu Painter: SE41
Screen Painter: SE51
Debugger: /H

35. Data Staging Exercises: Practice Test
Create a infoSource for flat file upload
Write ABAP routines in transfer rules and update rules

36. Warehouse Management Administrator Workbench (AWB)
Scheduler (infoPackage)
Data Load Monitor
Data Flow
Data Browsing
Process Chain
infoCube Compression
infoCube Rollup
infoCube Reconstruction
Performance Aspect for data loading
BW System Landscape
Delta Type, Delta Methods and Delta mangement

37. Administrator Workbench (RSA1)

38. Scheduler (infoPackage) – (1)

39. Scheduler (infoPackage) – (2)

40. Scheduler (infoPackage) – (3)

41. Scheduler (infoPackage) – (4)
Scheduling Options

42. Job Overview (SM37)

43. Job Overview (SM37)

44. Data Load Monitoring

45. Data Flow

46. Data Browsing

47. Process Chain (RSPC)

48. infoCube Compression
A process to delete request ID from cube and save disk space.
Maximum of 1000 data packages per infoCube (BW 2.0B +)
When an infoCube is compressed,
the content of the original tact table /BIC/F*** is compressed and copied in the /BIC/E***
After compression:
The Original /BIC/F*** table is emptied.
Two physical fact tables coexist: /F and /E table (Compressed version)
Logically there is still only one fact table per infoCube
Future data requests are automatically directed to the /BIC/E*** table
An Irreversible process.
Use ‘Zero elimination’ to delete records with ZERO values.

49. infoCube Compression

50. infoCube Rollup

51. infoCube Reconstruction

52. Performance Aspect for data loading
Techniques and guidelines to optimize the data load process:
Always load master data first
Drop the secondary index before loading and create it after data load is completed
Load data in parallel. (Except for PSA data)
Loading data in the PSA first, and then load data from PSA into data targets.
When loading large quantities from flat files, it is recommended that you break the files into several parts. These files can be loaded into SAP BW.
Sort data to be loaded beforehand.
Adjust IDOC-Related parameters.
Change the buffering of the number range objects (sequence number)
Update the database statistics for cardinality information needed for the query optimizer to best query the execution path.
Avoid reading files fro tapes; instead copy them to disk first.

53. Performance Aspect for data loading
Performance of a Data Warehouse
Data Extraction Time
Data Transformation Time
Data Delivery Time
Data Load Time
Backup and Recovery Time
Network Topology
Query Complexity
Number of Users
Data Scrubbing Time
The techniques to improve SAP BW operation system:
Table Partitioning
infoCube Compression
Data Archiving

54. BW System landscape SAP BW Development SAP BW QA SAP BW Production
SAP R/3 Development
SAP R/ QA
SAP R/3 Production
RFC
CTO: Correction and Transport Organizer
CTS
CTS: Change and Transport System
TMS: Transport and Management System
* CTS and TMS are two key components of CTO.

55. Data Mart What is Data Mart? Data Mart Architecture A local warehouse.
A warehouse with restricted scope of content
Support for analytical processing
Serving a single department, part of an organization, andéor a particular data analysis problem domain
Data Mart Architecture
Dependent Data Marts
Independent Data Marts
(Data marts sourced by a data warehouse)
(Data warehouse sourced by data marts)
Source 1
Source 2
Source 3
Source 1
Source 2
Source 3
Data Warehouse
Data Mart 1
Data Mart 2
Data Mart 1
Data Mart 2
Data Warehouse
End Users
End Users
End Users
End Users

56. Open Hub Service What is Open Hub service? What is infoSpoke?
A SAP BW technology that is used to share data in SAP BW with non-SAP data marts, analytical applications, and other applications.
To retrieve actual data and corresponding metadata from infoCube and ODS objects.
Targets:
Flat file (local or application server)
SAP transparent table
What is infoSpoke?
The central object of Open Hub services.
Used to define the data to be transported, and identify target system.
Selection criteria can be reused.
Support full and delta extraction.
Can be monitored.

57. How to implement infoSpoke
RSA1 – Modeling - Tools – Open Hub Service – Create InfoSpoke

58. Use BAdi to transform data in infoSpoke
Example (T-Code: SE19)
In the following implementation, a counter OHCOUNT is added to the extracted data of InfoSpoke MYSPOKE. To do this, the field OHCOUNT was added to the target structure /BIC/CZMYSPOKE in the DataDictionary.
method if_ex_openhub_transform~transform .   data: l_count type sy-tabix,   l_s_data_in type /bic/cymyspoke,   l_s_data_out type /bic/czmyspoke.   data l_dummy.   message i899(rsbo) with 'exit started' into l_dummy.   i_r_log->add_sy_message( ).   clear e_t_data_out.   loop at i_t_data_in into l_s_data_in.     move-corresponding l_s_data_in to l_s_data_out.     l_s_data_out-ohcount = sy-tabix.     insert l_s_data_out into table e_t_data_out.   endloop.   message i899(rsbo) with 'exit finished' into l_dummy.   i_r_log->add_sy_message( ). endmethod.

59. Delta Management What is Delta management? Delta Management Issues:
An update method used for the a very large amount of data.
Based on change log.
Delta Management Issues:
Delta Queue
Delta Type
Update Method
Record Mode
Delta Features

60. Delta Queue and Delta Types
Storage for new or changed records on a BW Source System “Queued” for upload to BW
Resides in the Source System (Can be another BW system)
XML Data Sent to DQ via HTTP
Delta Queue loading method:
At the time of the transaction (Delta type D)
At a later date than the transaction (V3 job) (Delta type D)
At the time the extractor job is called by BW (Delta type E)
Delta Type:
F: Flat File provides Delta
A: Use ALE Change pointer and Change log for Delta master Data Delta Load
D: Application determines Delta using Delta Queue
E: Extractor Determines Delta

61. Update Modes & Update methods
- Full Update:
- Delta Updates
- Initialization
- Delta
- Repeat Delta (Send current delta records + last delta records)
Update Methods
Full Update
Initialization – reset
No update
Delta Update

62. Extract Structure / PSA Data Targets Update Method
Record Modes
Used for source system to identify the changes to transaction data.
OLTP System
Extract Structure / PSA
Order # 720
Part#: M-01
Quantity 10L
Ord
Part#
QTY UN
720
M-01 10 L
Data Targets Update Method
Changed to 8
Before Img
720
M-01
-10 UN 8 L
Cube
Add
Order # 720
Part#: M-01
Quantity 8L
ODS
Add / Overwrite
After Img
Cube
Not Allowed
After Img
720
M-01 8 L
ODS
Overwrite
Order deleted
Add. Img
720
M-01 -2 L
Cube
Add
ODS
Add Only
Cube
Not Allowed
Order # 720
Part#: M-01
Quantity 10L
Del. Img
720
M-01 10 L
ODS
Overwrite
Rev. Img
720
M-01
-10 L
Cube
Add
ODS
Add / Overwrite

63. ODS Review: Overwrite of Non-key fields
Automatically creation of delta records to feed other targets
Active Data
Doc#
Status
Item
QTY
1000 O 1 10
Original Data in Data Target (Cube)
Doc#
Status
Item
QTY
1000 O 1 10
1000 D 1 8
Changed Log
Activating the Data in Delta Queue
Data in Delta Queue
Doc#
Status
Item
QTY
1000 O 1
-10 D 8
Doc#
Status
Item
QTY
1000 D 1 8
In coming Data in PSA
Doc#
Status
Item
QTY
1000 D 1 8

64. Central Delta Management: Features
Metadata tables
ROOSORCE in source system
RODELTAM in BW
Multiple initialization of delta
Scheduler->Initialization options for source system
Repair Request
Scheduler -> Repair Full Request (Indicate this request is to “repair” the target)
Extractor Checker : RSA3
Delta Queue Monitor: RSA7

65. Data Staging Practice Test & Suggested Exercises
Complete 30 simulated questions for data modeling
Load master data from flat file
Create infoSource for master data
Load transactional data from flat file
Create infoSource for transactional data
Write ABAP program in transfer rules and update rules
Create a infoPackage to load data from flat files
Create a Process Chain
Write a ABAP Report program