Monday, 13 May 2013

Full/Delta/Initialize delta update methods

Introduction

Update method is used to get the updated data coming from the source system to BI system at Info package level. We can set update methods in the update tab of the info package.

The update methods in the info package are:

1. Full Update
2. Delta Update
3. Initialize Delta Process
    (I) Initialize with data transfer
    (II) Initialize without data transfer
    (III) Early Delta Initialization

1.Full Update

Full update extracts the full data from source system to PSA in BI7 every time. 

2. Delta Update

Delta update extracts delta records only from the BW delta queue in the source system to BI system.

We must initialize the delta in order to get delta records, otherwise it is not possible to load delta records.

The following are the 4 delta types for the data source in the system.

F: Flat file provides the delta
E: Extractor determines the delta, Ex: LIS, COPA
D: Application determines the delta, Ex: LO, FI-AR/AP
A: Use ALE change log delta

Note: We can know the delta properties from ROOSOURCE table in the source system with SE16 transaction code.

3.Initialize Delta Process

To get the delta records, one must initialize the delta process. While initializing the delta process, the system will generate a flag: Initialize option for the source system in (scheduler menu of info package) BI and BW delta queue per the data source in the source system (RSA7). This enables the time stamp mechanism.

Initialize with data transfer

If you select this option, It extracts the init data from source system to BI system and allows delta functionality.

Steps for initialize with data transfer

Lock the users in the source system 
Delete the contents of the setup tables for the specific application component in source system(T code: LBWG). 
Fill the setup tables (SBIW or OLI*BW, use 1,2,3...in place of * according to the application ). 
Run the info package with initialize with data transfer. 
unlock the users in the system 

Note: This is very time consuming process, because we need to lock the users until data reaches to the BI system.This effects the client business.

Initialize without data transfer

In some cases, init is successful but someone has deleted the init flag. In order to set the flag again to perform the delta load without disturbing the data, we execute IP with this option.

Steps for initialize without data transfer

Lock the users in the source system 
Delete the setup tables content for the specific application component. 
Fill the setup tables 
Run the IP with the option: Initialize without data transfer. 
Unlock the users in the source system 
Load data to BI system using repair full request info package 

Note: In this method, after data is loaded to setup tables we can unlock the users in source system. this is better option than initialize with data transfer option.

Early Delta Initialization

In this option, we can do the delta initialization before filling the setup tables.So that users can post the documents when we are filling the setup tables.We will get the posted records in the next delta run

Steps for early delta initialization

Run the Info package with early delta initialization option.This will enable the BW delta queue and setup the time stamp for delta in the source system. 
Delete the setup tables for the application component 
Fill the setup tables 
Load the setup table data using repair full request (scheduler menu option of info package) info package 

How to check whether the data source supports early delta initialization or not?

Go to SE16 in ECC, give table name: ROOSOURCE and enter 
In the next screen give data source like 2lis_02_sdr(purchase document header data source) name and enter 
if field ZDD_ABLE has a value 'X', then the data source supports early delta initialization 
If the filed has space, then the data source does not support early delta initialization.

Friday, 10 May 2013

Difference between V1, V2, V3 updates

V1 Synchronous update - Used for LIVE tables, after the records get updated system will send an acknowledgement. This degrades processing performance.

V2 Asynchronous update – LUW's will be Updated in front end without any acknowledgement. 

V3 Asynchronous with background updating – Updating happens in Background.

We use this concept in LO Extraction update modes.

Direct delta update mode uses V2 update. Recommended only when less number of records are there.

Queued delta is recommended for most of the cases and it will use V3 update. LUW’s will be updated to Extractor queue (LBWQ) in the form of tokens (pointers). We need to run a background job (V3 collective run) to push the data to delta queue from LIVE tables. All the records will be moved at once so no problem with sequence.

Unserialized V3 update also uses V3 update, only recommended when sequence of data is not important. DSO is not recommended as target when we use this update. 

Friday, 3 May 2013

Common Issues with Open Hub

1. Error message: 'Destination not supported' (Error Code RSBO 102)


when creating an open hub destination

Firstly the corrupt Open Hub destinations need to be repaired. To do this you need to check the table RSBOHDEST, for all Open Hub Destination entries where the field DESTYPE is initial/empty or is equal to 'FILE', you must change the DESTYPE for such entries to TAB in the table RSBOHDEST. TAB must be selected because it is not possible to select another valid DESTYPE in the table. When you no longer have the error message 'Destination type is not supported' you can change the destination type to what it should be in the maintenance for the Open Hub Destination in RSA1.

For the users that worked with Open Hub and have the problem that they cannot access RSA1 (not supported (RSBO102) error message), there should be an entry(for each user) in the personalisation table RSAWBN_USR_TREE with the field AWBUSER = to the name of the user ID that has the problem and the field AWBTREE = DEST. You need to delete the entries returned for this selection on the fields AWBUSER and AWBTREE only for the User ID's that have the problem from the table RSAWBN_USR_TREE and the problem should be resolved.

2. Errors when sending data to a 3rd party Open Hub Destination 

Message no. RSBO523 SYSTEM_FAILURE with function RSB_API_OHS_3RDPARTY_NOTIFY and target system x 
Message no. RSBO899 Bean RSB_API_OHS_3RDPARTY_NOTIFY not found on host x, ProgId=x: Object not found in lookup of x 
Message no. RSBK241 Error while updating to target x (type Open Hub Destination)
When you execute the DTP for OHD, the system stores the data in a DB table 

The 3rd party tool is notified with the Function Module RSB_API_OHS_3RDPARTY_NOTIFY, this function has to be implemented by the 3rd party tool, not in the BW system

To resolve this issue;

Check if the function exists on the 3rd party tool using "Extras" --> "function list" after you select the destination in SM59

Implement the necessary function on the 3rd party tool

If you require assistance to implement the function on the 3rd party system, please contact the relevant 3rd party support desk.

Some useful T-Code for BI performance tuning

T-CodeDescription
SM66Global Work Process Overview
ST02Tune Summary
ST06System monitor
STADSAP workload
ST05SQL Trace
SE30ABAP Trace
ST12Single transaction analysis(including ST05/ST30)
RSMOBW Load monitor
DB02DB Load overview
ST04DB Performance snapshot
RSBATCHBI Background management
RSODSO_SETTINGSMaintenance of runtime parameter of DSO
RSRVAnalysis and repair BI Objects
ST03Workload in system
RSRTQuery Monitor
RSRTRACEConfigure Trace Tool