SAP Business Objects 4.0 (Information Design Tool -Tutorial4)

Creating a Universe using IDT -T4
Delegate Measure, Loops (Aliases and Contexts) and Predefined Filters

Information Design Tool -Tutorial4

SAP Business Objects 4.0 (Information Design Tool -Tutorial3)

Creating a Universe using IDT -T3
Working with Business Layer?

Information Design Tool -Tutorial3

SAP Business Objects 4.0 (Information Design Tool -Tutorial2)

Creating a Universe using IDT -T2
How to create a Data Foundation Layer?

Information Design Tool -Tutorial2

 

SAP Business Objects 4.0 (Information Design Tool -Tutorial1)

Creating a Universe using IDT -T1 
How to create a new project and enable connection to a data source?

How to perform LO extraction from SAP R/3 to BW system?

**check whether your Datasource is active and in accordance with the requirements “TCode LBWE”**

Step1:-

Transaction code “RSA3”

Check whether the data is updated for the Data Source

Transaction Code “LBWG”

Delete data in setup table by giving the correct application name.

** Check whether the Datsource is already extracting data in to BW. If the Datasource is extracting the data then we need to check the Setup tables (“SE11” Technical name is ‘SETUP’, Extraction Queue (LBWQ), Update tables (SM13), Delta Queue (RSA7) etc. If data exists in any of these TCodes we need to check whether we need these data in BW or not. If we not need the data delete it using “LBWG”.**

Transaction Code “SBIW”

Navigate to “Settings for Application Specific Data Source (PI)” >> ” Logistics” >> ” Managing Extract Structures” >> ”Initialization” >> “Filling the Setup Table” >> “Application Specific Setup of Statistical Data” >> “Execute for application”

[**or one can directly use the TCode OLI^^BW (^^based on your application)**]

In the next screen give name to the run and execute. Now all the available records from R/3 will get updated to Setup tables

** Only Full/Delta initialization loads will move to Setup tables**

Step2:-

Transaction code “RSA3”

Check whether the data got updated.

Transaction code “LBWE”

Check whether the update mode for DataSource is “Unserialized V3”

**Delta Load data flow differs with various update methods, there are three delta update methods

1.      “Queued Delta”:- Data will move to Extraction queue (“LBWQ”) and then run collective update to move the data to Delta Queue (“RSA7”).

2.      “Direct Delta” :- Data will move to RSA7 directly

3.      “Unserialized V3” :- Data will go to Update tables (“SM13”), then will run collective update to move the data to RSA7 **

Step3:-

Login to BW system and initialize the delta process by scheduling the corresponding InfoPackage. All the data that is available in the setup tables are now loaded to data targets. **First time process**

Transaction code “LBWE” (R/3)

Change the update mode for corresponding Data Source to “Direct/Queue delta”. Data will bypass SM13 and directly go to delta queue in RSA7.

** Only Delta update data moves into RSA7/LBWQ **

Transaction code “RSA7”

Queue will be marked in green. Once the new records are updated one can immediately see the records in RSA7.

Go back to BW system and create new infopackage for delta load and schedule the load.

Cross check the data in Data target

ABAP Dictionary Objects

It’s a type of metadata repository that is used by BW data structures, and connects to all applications around the system. BW programs can access the ABAP dictionary using "Structured query language" (SQL). When the ABAP dictionary is accessed, the basis system translates the open SQL commands to database specific commands.

Transaction code used is “SE11”

(Fig: 1)

Basic elements are Domains, Data Elements and Tables

Domains:-

Define basic elements having a defined data type and data length (eg: Customer Number). All further ABAP dictionary elements will be based on defined domains.

A Customer number is defined as a 10 digit alpha numerical field by domain /BI0/OCUSTOMER with the data type char and length 10 and Master data value table as /BI0/MCUSTOMER.

(Fig: 2)

Data Elements:-

..Defined as description layer over the domains. Each data element refers specifically to a domain, and each domain can be used by several data elements. Data element contains descriptive data that can be used as a header when displaying field content. Eg: Customer number usually mapped as one of the partner roles such as Ship- To party, Sold-To party etc, where each refers to the domain customer number.

(Fig: 3)

Tables:-

A structure of several fields is defined as a table. All the fields of a structure need to be defined by a data element. Only field name is shown in the table. Within the table a data element can be used repeatedly. There are two types of table in ABAP dictionary; Transparent tables (option to store data in database and is created automatically) and Structures (they can be reused in programs as preconfigured type declarations)

(Fig: 4)

Step by Step Procedure to Extract Data from R/3 to BI 7.0 using Query

This article demonstrates a step-by-step process for doing generic extraction from R3 into BI using Infoset query. It also describes the creation of User Groups,Infoset query and BI objects like InfoObjects, DTP, Transformations and also includes the steps to install Objects from BI Content.
click here