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

Virtual KeyFigures/Characteristics

Need for Virtual KF

When we need to commit values during query execution and if the syntax is too complex to introduce it in CKF/RKF/Formula; and in a scenario where we don’t want to go for Data Provider remodeling to introduce a new KF

This will make the report more flexible and dynamic.

Virtual Key Figure will be defined inside the data provider as metadata and won’t contain any physical value.

How to create one?

Same ways as you create any other basic KF or characteristics.

Goto RSA! ->  Select InfoObjects -> Select your Catalogue -> Create a new Keyfigure/Char -> Description/Technical name define it as a virtual KF/Char -> Save it -> Goto to your infoProvider-> Insert the newly created KF -> Goto your Query Designer introduce the new object

In normal case you need to implement a BADI to insert values to virtual KF.

Check Links below;

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e051fda8-71a9-2a10-ac9e-8d17414a8c8c

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3506

SAP BW 3.5 Function Details

This document can be used as a handbook for understanding SAP BW 3.5 objects/functionalities. Click the link below
SAP_BW_3.5_Functoin_Detail

Inconsistent ODS/Infocube during data updation

Back in 2007 I faced an issue with inconsistent ODS object. We were not able to activate some queue requests, And considering data reloading was a herculean task.

The error message was similar to one below;

“DSO XXX inconsistent; request REQU_XXX only exists in RSODSACTREQ”

“ODS Activation failed with status :5”

We faced a similar scenario today, that’s why I thought about noting this down. You will get ample material in internet explaining about this.

One solution is to delete the request from request queue (manage screen) and also from the table RSODSACTREQ (Activation table of M-requests to change-log requests) and try to activate the data in ODS.

Or

Use Transaction RSRV (Analysis and repair for BI objects) -> All Elementary Tests-> ODS Objects -> Check the Status of the Generated Program of a Data Store Object -> give  ODS name->Execute.

 If it fails, then click Correct Error Tab & execute again. Check once more and activate ODS object