OBIEE 11G Installation & Best practices BAPI access for SAP/BW data sources

(Special thanks to Roxane Wiart from Oracle)

Table of Contents

1. GLOBAL ARCHITECTURE. 3

2. COMMUNICATION LAYER. 4

3. SUPPORTED ENVIRONMENT. 6

3.1 OTN.. 6

3.2 DATA SOURCES SAP BW... 6

4. INSTALLATION AND CONFIGURATION.. 8

4.1 SAP/BW CLIENT LAYER. 8

4.2 ORACLE BI SAP BAPI ADAPTER. 9

4.3 WINDOWS PATCH OS SECURITY. 10

4.4 WINDOWS VARIABLE ENV.. 10

5. SAP USER HABILITATIONS. 11

6. ADMIN TOOL IMPORT METADATA.. 12

6.1 CREATE THE CONNEXION.. 12

6.2 SELECT THE SAP DATA SOURCES. 14

6.3 WORK WITH SAP DATA HIERARCHIES. 15

6.4 WORK WITH AGGREGATION RULES. 17

6.5 VIEW MEMBERS. 17

7. OBSERVATIONS/BEST PRACTICES. 18

7.1 SAP RFC INI FILE. 18

7.2 RPD AND TIME SERIES. 18

7.3 FILTERS IN OBI ANSWER. 18

7.4 SAP/BW QUERY VOLUME. 18

7.5 SAP/BW QUERY EXPORT. 18

7.6 SAP/BW DATE IN RPD.. 18

8. TROUBLESHOOTING.. 19

8.1 NETWORK CONNECTION.. 19

8.2 SAP NW RFC SDK CLIENT LAYER. 19

8.3 LIMITATIONS OF NUMBERS OF MEMBERS. 20

8.4 CONFIG FILES OBI 20

8.5 KNOW ISSUES ON SAP BW... 20


1. GLOBAL ARCHITECTURE

INTRODUCTION SAP/BW DATA SOURCES SYTEM

SAP/BW integrates with BI tools via MDX (Multidimensional Queries), MDX is the de facto industry standard to query OLAP servers.

SAP/BW Server includes an MDX processor to directly query any BW INFOCUBE and INFOQUERY

SAP/BW supports multiple protocols to submit MDX requests:

With OBI EE 11g, both the XMLA adapter and the BAPI adapter are supported


2. COMMUNICATION LAYER

2 components OBI need to access SAP/BW

font-family: "Arial","sans-serif";" lang="EN-US">The admin tool (client admin layer) and BI server services (web query)

The configuration is the same for these 2 components if the solution is deployed on separate machine

The BW (Business Warehouse) datasources from BW SERVER available in obi :

  • SAP/BW INFOCUBES
  • SAP/BW InfoProvider
  • SAP/BW MultiProvider
  • SAPBW Infoquery

You can connect to SAP/BW data sources using either the XMLA connection type, or the SAP/BW Native connection type (BAPI). SAP/BW Native connections might not be available on certain platforms.


To connect to SAP/BW data sources using the SAP/BW Native connection type, you must first download the BAPI Adapter for OBI Package from the Bristlecone Web site and Then, follow the configuration instructions in the Readme provided with the download.

No reconfiguration steps are required to connect to SAP/BW over XMLA.

Communication layer with BAPI connection type between OBI client and SAP/BW server:


3. SUPPORTED ENVIRONMENT

3.1 OTN

All the last supported requirements are available on oracle OTN site:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

3.2 DATA SOURCES SAP BW

For the SAP/BW data sources: In the XLS file, go to the Tab, and check the level SAP/BW certified:

Level of SAP/BW sources supported versions (Q1 CY13):

BI 11.1.1.5+

SAP/BW 7.0 SP17+

BI 10.1.3.4.1

SAP/BW 3.5 SP 20+

SAP/BW 7.0 SP17+

N.B:

Variable Support

Variables are parameters to BW queries to filter members and other objects

The BI Server supports the following variable types

Characteristic

Hierarchy

Numeric

The BI Server will rewrite filtered requested to use variables, example:

Logical Query:

SELECT Material."Material Level 01" saw_0, "0SD_C03/Z0SD_C03_Q001"."Gross weight in kg" saw_1 FROM "0SD_C03" WHERE Material."Material Level 01" = 'CD ROM Drive' ORDER BY saw_0

MDX Query:

With

set [0MATERIAL2] as ' hierarchize ({{[0MATERIAL].[LEVEL00].members},{[0MATERIAL].[LEVEL01].members}})'

set [Axis1Set] as '{[0MATERIAL2]}'

member [Measures].[MS1] as '[Measures].[D5NXUO6GTYVLD646QLP8RR9EF]'

select

{[Measures].[MS1]} on columns,

NON EMPTY {[Axis1Set]}properties MEMBER_UNIQUE_NAME, PARENT_UNIQUE_NAME on rows

from

[0SD_C03/Z0SD_C03_Q001]

SAP VARIABLES [0P_ITEM] INCLUDING [0MATERIAL].[R-1180]

For 11.1.1.6 specifically (Please see http://www.bristleconelabs.com/edel/docs/obia/11.1.1.6/Release%20Notes%2011.1.1.6.txt ):

Bcone BAPI Adaptor Release Notes

========================================================

This is a release note for Bcone BAPI Adaptor version 11.1.1.6.

About Bcone BAPI Adaptor

========================================================

Bcone BAPI Adaptor is a customized wrapper over NW RFC SDK. A Client that wants to call BAPI functions using Bcone BAPI Adaptor needs to load “BconeAdaptor.Dll”. Bcone BAPI Adaptor can be loaded dynamically or linked statically to the client.

About this Release

========================================================

This release has some additional features for OBIEE. This release of Bcone BAPI Adaptor supports OBIEE version 11.1.1.6.2 BP1 and later.

Changes/Fixes

========================================================

This is a full release of Bcone BAPI Adaptor. In this release following features have been added.

1) GetMembers API of NW RFC SDK has been added.

2) GetStructures API of NW RFC SDK has been added.

3) Improved error handling is implemented with this release.

4) NW RFC SDK calls have been made safer.


4. INSTALLATION AND CONFIGURATION

4.1 SAP/BW CLIENT LAYER

This layer is a Full SAP step

Connect to SAP marketplace Web site (customer login needed).

Go to the

-> Support Packages and Patches - Entry by Application Group

-> Additional Components

-> SAP NW RFC SDK

-> SAP NW RFC SDK 7.20

-> <platform> (for the OS BI server target)

-> NWRFC_1-20004xxx.SAR

and download the last pack for the SAR package (level 5 au 30/06/2011)

If the deployment includes several types of Os (32/64 bits), download all the SAR needed.

If the Admin tool is on the same machine of the full OBI installation on 64, only 64 bits libraries can be download.

Unzip the SAR package with the SAP CAR tool. If the server doesn’t have this exe, download it from the sap marketplace web site

Once unzip, the contain of the SAP NW RFC SDL layer is in a folder « nwrfcsdk »

Example on windows here:

Some Os need additional parameters in the file: SAPRFC.ini

Copy the saprfc.ini from the demo folder and put in the folder nwrfcsdk

Open and modify it regarding the SAP/BW customer login parameters


4.2 ORACLE BI SAP BAPI ADAPTER

Download the BAPI Adapter for OBI Package from the Bristlecone Web site at: http://www.bristleconelabs.com/edel/OBIEE_BAPIAdaptor_download.asp

Select the BAPI needed regarding the OS and the Bristlecone documentation:

Unzip the BconeAdaptor zip files on obi machine

For 32 bits os : 1file = BconeAdaptor.dll

For 64 bits os: 2 files = BconeAdaptor.dll + BconeAdaptor.lib

Copy/Paste this contents in a folder (the same or not of the SAP SDK in previous step: nwrfcsdk)

Example on windows:


4.3 WINDOWS PATCH OS SECURITY

Depends of the Os, a level patch security windows is mandatory.

This is specified in the documentation PDF Bristlecone: BAPI Adapter Bristlecone Components Installation and Configuration Readme.pdf

Download the exe file from Microsoft site and execute the patch Os level and execute

4.4 WINDOWS VARIABLE ENV

In the Os variable system configuration, add the folders "bin" and "lib" for the « nwrfcsdk » in the Path variable:

Depend of the Os, a variable need to be created:

In the Os variable system configuration Create an environment variable RFC_INI with the value of the patch of file rfc.ini folder location


5. SAP USER HABILITATIONS

Some specifics habilitations must be attribute to the user sap for OBI in order to access and import the metadata SAP/BW and use the BAPI connection.

On the sap system, check the technical authorization on the S_RFC object : "Contrôle des authorisations lors de l'accès RFC" (French version)

- ACTVT : 16

- RFC_NAME : RFC1, RSOB, SDIFRUNTIME, SYST

- RFC_TYPE : FUGR

This is mandatory for any access to SAP/BW from OBI BAPI

Optionnal step: for trace user activity connection between SAP/BW server and the client BAPI :

Object S_RS_RSTT "Objet d'autorisation pour outil Trace RS" (french version)

- ACTVT : 01, 02, 03

- RSTTBOBJ : AUTHTRACE, TRACE

- USER : <compte communication>

Analytics BI Authorizations BI (on the data):

Object S_RS_AUTH "Autorisations analyse BI dans rôle" (French version)

- BIAUTH : <autorisation analytique>

  • Put 0BI_ALL if no analytic restriction are required, or create a specific authorization on the functional area.

BI Authorizations on the objects :

Object S_RS_COMP "Business Explorer - composantes" (French Version)

- ACTVT : 03, 16

- RSINFOAREA : <Domaine d'application>

- RSINFOCUBE : <InfoCube>

- RSZCOMPID : $<InfoCube>, <Requête>

- RSZCOMPTP : REP

  • For a query Access, put the same authorizations as the query was executed by SAP BI.

  • For a direct Infocube access, the SAP system check the query as a „pseudo query named :
    $<Infocube>
    (field RSZCOMPID).
    If the all the list of SAP Infocubes need to be access by OBI Admin tool, the field RSINFOCUBE need to be SET with “$*” value else, put the Infocubess named available.

Objet S_RS_COMP1 " Business Explorer - Composantes: Extension du propriétaire" (french version)

- ACTVT : 03, 16

- RSZCOMPID : $<InfoCube>, <Requête>

- RSZCOMPTP : REP

- RSZOWNER : <Propriétaire des requêtes>

  • Complement to S_RS_COMP. Allow to limit access to query regarding owner of the query. If no restriction is necessary, put the “*” value in the field RSZOWENER and the same values as S_RS_COMP in the other field.


6. ADMIN TOOL IMPORT METADATA

6.1 CREATE THE CONNEXION

Define the connection to SAP BW:

See also: http://docs.oracle.com/cd/E23943_01/bi.1111/e10540/datasource.htm#CACEJJHC

Provide the following information:

■ System IP or Hostname: The host name or IP address of the SAP data server. This field corresponds to the parameter as host in the SAP/BW connect string.

■ System Number: The SAP system number. This is a two-digit number assigned to an SAP instance, also called Web Application Server, or WAS. This field corresponds to the parameter sysnr in the SAP/BW connect string.

■ Client Number: The SAP client number. This is a three-digit number assigned to the self-contained unit called Client in SAP. A Client can be a training, development, testing, or production client, or it can represent different divisions in a large company.

This field corresponds to the parameter client in the SAP/BW connect string.

■ Language: The SAP language code used when logging in to the data source (for example, EN for English or DE for German). This field corresponds to the parameter lang in the SAP/BW connect string.

■ Additional Parameters: Additional connection string parameters in the format param=value. Delimit multiple parameters with a colon. This field is optional.

■ User Name: A valid user name for the data source.

■ Password: The corresponding user password. The password is case-sensitive.

The first five fields constitute the elements of the SAP/BW connect string, in the format:

ashost=value:sysnr=value:client=value:lang=value:additional_param=value

For example:

ashost=10.30.0.19:sysnr=00:client=100:lang=EN

NOTA or TEST XMLA connection:

URL This property is only displayed for XMLA data sources. Specify the URL to connect to the XMLA provider. This URL points to the XMLA virtual directory of the computer hosting the cube. This virtual directory must be associated with msxisapi.dll (part of the Microsoft XML for Analysis SDK installation). For example, the URL might look like the following:

http://<ServerName>/xmla/msxisap.dll

The authorization and connection information on sap system must be check if the connection failed.


6.2 SELECT THE SAP DATA SOURCES

Select the data sources (infocubes, query cubes)

Depend of the connection parameter and the data sources, the metadata import dont generate the same thing.

If the language is unknown, the technical names from the SAP/BW catalog are imported

Example : data sources Infocubes with LANGAGE = EN

Example : data sources Query cubes with LANGAGE = FR :


6.3 WORK WITH SAP DATA HIERARCHIES

Check any update from the repository admin documentation e10540.pdf

For SAP/BW data sources, all hierarchies default to fully balanced hierarchies on import. The hierarchy type for two-level hierarchies (which typically correspond to characteristic primary hierarchies) should not be changed. Review all SAP/BW multi-level (external) hierarchies to determine whether any are parent-child hierarchies, and set them to Value as needed.

Working with Cube Variables for SAP/BW Data Sources

In SAP/BW data sources, cube variables are used as a means of configuring queries. Cube variable objects are imported into the Physical layer when metadata is imported from Querycubes/Bex Queries in SAP/BW data sources. Typically, you do not edit these objects directly except to keep them synchronized with the Bex queries in the data source, and except to specify overrides for key characteristics values. The Cube Variables tab of the Cube Table dialog lists the cube variables for the given cube table, along with the cube variable caption. Double-click a cube variable to see more detailed information, or click the Add button to define a new cube variable.

Description of the properties of CUBE VARIABLES for SAP/BW data sources. See your SAP/BW documentation for additional information.

Properties

Description

Name

Name of the cube variable.

Caption

A description (label or caption) associated with the cube

variable, mainly used for display purposes.

Variable Type

The type of cube variable. Variable types include:

■ SAP_VAR_TYPE_MEMBER: A placeholder for a selection for MEMBER_UNIQUE_NAMES.

■ SAP_VAR_TYPE_HIERARCHY: A placeholder for a HIERARCHY_UNIQUE_NAME.

■ SAP_VAR_TYPE_NUMERIC: A placeholder for a numeric value in formulas.

Selection Type

The selection type of the cube variable, for cube variables of type SAP_VAR_TYPE_MEMBER.

Selection types include:

■ SAP_VAR_SEL_TYPE_VALUE: The variable is replaced by a single value. Cube

variables of type NUMERIC must have this selection type.

■ SAP_VAR_SEL_TYPE_INTERVAL: A placeholder for an interval.

■ SAP_VAR_SEL_TYPE_COMPLEX: A placeholder for a complex selection.

Entry Type

Indicates whether replacing variables is optional or mandatory.

Entry types include:

■ SAP_VAR_INPUT_TYPE_OPTIONAL: Specifying a value is optional for this variable.

■ SAP_VAR_INPUT_TYPE_MANDATORY: You must specify a value for this variable.

■ SAP_VAR_INPUT_TYPE_MANDATORY_NOT_INITIAL: You must specify a value for this variable. An initial field is not a valid entry.

Reference Dimension

This column contains a DIMENSION_UNIQUE_NAME for the

parameter type SAP_VAR_TYPE_HIERARCHY.

Reference Hierarchy

This column contains a HIERARCHY_UNIQUE_NAME for the

variable type SAP_VAR_TYPE_MEMBER.

Default Low

This property contains a default value for the variable or is zero.

Default High

This property contains a default value for the variable or is zero.

This property is only important for variables with the selection

type SAP_VAR_SEL_TYPE_INTERVAL and SAP_VAR_SEL_

TYPE_SELECTION.

Override Default Low

Provide a default value for the cube variable in this field if the Default Low is zero.

You must specify a value for this property for mandatory variables that do not specify a default value.

Override Default High

Provide a default value for the cube variable in this field if the Default High is zero.

You must specify a value for this property for mandatory variables that do not specify a default value.


6.4 WORK WITH AGGREGATION RULES

Informations from: Oracle® Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition 11g E10540-02

http://docs.oracle.com/cd/E23943_01/bi.1111/e10540/busmodlayer.htm#BIEMG1335

Defining Aggregation Rules for Multidimensional Data Sources : By default, when you import SAP/BW (and some other multidimensional cubes) into the Physical layer, Oracle Business Intelligence cannot read the aggregation rules set within the data source. Because of this, the measures are imported automatically with the default aggregation rule of External Aggregation. Note that this rule is only available for multidimensional data sources.

External Aggregation means that the Oracle BI Server is not aware of the underlying aggregation rule for the specific measure and will not compute it internally. Instead, the Oracle BI Server will always ship the query to the underlying multidimensional data source for aggregation.

Because the underlying data sources are extremely efficient, pushing the aggregation rules down to the data source ensures that the Oracle BI Server returns the results without adding any additional overhead in processing. However, it is recommended that you update the aggregation rule for each measure in Oracle Business Intelligence with the corresponding aggregation rule defined in the data source. Doing so ensures that the Oracle BI Server can do additional computations when needed. There is no query performance impact, since the Oracle BI Server still pushes down optimized queries wherever possible.

6.5 VIEW MEMBERS

View Member values feature in the physical layer is only available ON LINE repository Mode


7. OBSERVATIONS/BEST PRACTICES

7.1 SAP RFC INI FILE

The "saprfc.ini" file is not use on Windows 2008 Os configuration. The step to define the Os variable RFC_ini is not mandatory in this case.

7.2 RPD AND TIME SERIES

In RPD, OBI cannot use directly Times series functions (Ago, ToDate) because SAP/BW do not store Data in date format. In the RPD, its necessary to define first some CAST or transformation function on the data source column and after use them in derived with time series functions

7.3 FILTERS IN OBI ANSWER

In Answer, use filter on characteristic key, not on display attribute (Display attribute cannot be filtered on SAP BW)

7.4 SAP/BW QUERY VOLUME

Define little SAP/BW query on the physical layer (and federated them in the logical/presentation layer) and not a big SAP/BW query. This is for limiting the number of joins between SAP/BW (data values) and the Extensions tables (data properties).

7.5 SAP/BW QUERY EXPORT

During import metadata step in the Admin tool, the list of query cube is empty or partial. Only Infocubes are visible. The query cubes (create in SAP Bex Query Designer) are only visible from other BI tool if during saving process the checked box called "allow External Access to this query" is checked. Once this option is saved in the SAP Bex query designer, the query is visible in Admin tool.

In SAP BEX : this option is setting in the tab: release OLEDB for OLAP, QUERY PROPERTIE, advanced Tab.

7.6 SAP/BW DATE IN RPD

In order to use time series function, it’s necessary to work with Admin tool functions on Date field column from SAP.

Why? all the Date information in SAP/BW are stored in VARCHAR format and not in date format. All Values need to be converted in Date format before to call date function in OBI Admin tool.

Example of syntax:

CAST ( SUBSTRING( CAST ("ZMHCMES1/ZHCM_ZMHCMES1_ESS_ERC_STAT1"."Calendar day"."Calendar day Level 01" AS VARCHAR ( 20 )) FROM 7 FOR 4) || SUBSTRING( CAST ("ZMHCMES1/ZHCM_ZMHCMES1_ESS_ERC_STAT1"."Calendar day"."Calendar day Level 01" AS VARCHAR ( 20 )) FROM 6 FOR 1) || SUBSTRING( CAST ("ZMHCMES1/ZHCM_ZMHCMES1_ESS_ERC_STAT1"."Calendar day"."Calendar day Level 01" AS VARCHAR ( 20 )) FROM 1 FOR 3) || SUBSTRING( CAST ("ZMHCMES1/ZHCM_ZMHCMES1_ESS_ERC_STAT1"."Calendar day"."Calendar day Level 01" AS VARCHAR ( 20 )) FROM 4 FOR 2) AS DATE )


8. TROUBLESHOOTING

8.1 NETWORK CONNECTION

Before any installation process, check the physical connection between machines

=> launch a command line : Telnet 32xx (xx for the number SAP/BW system)

By default the SAP/BW system number is 01, so telnet TCP/ IP address (or host machine) 3201

If error appears on this step: no connection will be possible. The issue can be the TCP/IP resolution with firewall in place between obi and sap layer. Check the open ports

If a black screen appear: the communication layer is ok.

8.2 SAP NW RFC SDK CLIENT LAYER

The connection between obi is done by the nw rfc sdk client.

The test is to check this SAP layer communication between the nw rfc dsk client and server

For this, try to execute in line mode the STARTRFC.exe from the nwrfcsdk\bin folder with the connection parameters to sap bw

If the above error occurs:

- Check the bin folder and the existing file

- Check the load of dll from the Os (reboot can help)

- Check the correct libraries installed (32/64 rfc sdk)


8.3 LIMITATIONS OF NUMBERS OF MEMBERS

During the filter creation in answer, the tool can limit the context regarding the volume of data in the filter and the users have a message for information

8.4 CONFIG FILES OBI

Check the parameters in the 2 files :

- DBFeatures.INI

MW_HOME\instances\instancex\config\OracleBIServerComponent\coreapplication_obis1

- NQSConfig.INI

MW_HOME\instances\instancex\config\OracleBIServerComponent\coreapplication_obis1

For number of members in section or export to excel, modify the file :

- Instanceconfig.xml

MW_HOME\instances\instancex\config\OracleBIPresentationServicesComponent\coreapplication_obips1

8.5 KNOW ISSUES ON SAP/BW

  • In multidimensional once you import the cubes/BEX query, its a black hole, there is not much you could do it on physical layer like alias renaming etc.

  • Re-importing of BEX/Multi provider could possibly change the column ids, hence resulting recreation of BMM, Presentation layer followed by re-creation of reports

  • Presentation variables cannot be used on the key columns, as they generate in correct MDX

  • Filters On Non Key Columns are NOT added to MDX Query see note :1288595.1 on Oracle Support

  • After importing BW-SAP cubes or BEX, all the non integer columns get converted to varchar data types

  • Due to non-availability of date data type, date functions like ago, today cannot be used.

  • In some of the cases OBIEE creates sub-optimal queries.

  • Using SAP BI unable to pass Filter Selection [ID 942641.1] (Modified 06-10-2011 obi 10, ok 11) : The following solutions is suggested as a resolution to pass the filter parameters along with the query to SAP BI. The following changes were made to the NQSCONFIG.ini file. Under MDX_MEMBER_CACHE section, it was suggested to change the Enable Cache = YES.

Comments:

Hi, many thanks for this note is really interesting.

I just have a question, there is a note into support.oracle.com where describe this information and attach a document like pdf or Word, in order to discuss this implementation with my customers, just sometimes is better disscuss over a document than blog.

Many thanks for your replay

Posted by guest on January 18, 2013 at 05:27 PM SGT #

Hi,

OK, I agree with you and will attach a PDF right now...On My Oracle Support, we still need to make it posted.

Posted by Olivier Bennardo on January 18, 2013 at 11:52 PM SGT #

Hi Olivier, could you share the Note ID from support.oracle.com. i was looked for the article but without success.

Many thanks again

Posted by guest on January 26, 2013 at 10:36 PM SGT #

Done, you should have it now. Let me know if you cannot find it on My Oracle Support.

Posted by Olivier Bennardo on January 27, 2013 at 02:54 AM SGT #

Nice Post Olivier Bennardo

Posted by Yogesh Patil on March 07, 2013 at 09:22 PM SGT #

Hi Olivier,
thank you very much for providing theis valuable collection of pitfalls, hints and bugs and workarounds.
May these infos prevend harm and frustration from the brave heros using ODI with SAP-BW. Good luck to all of these fighters.

Posted by guest on March 15, 2013 at 01:46 AM SGT #

Does anybody know when Bristlecone site (with BAPI adapters) will be available?

Is any other place to find them (adapters)?

Posted by guest on June 24, 2013 at 07:15 PM SGT #

Hi all,

We had communications with Bristlecone, which indicated that their web site had been in critical maintenance, hence why the web site was unavailable for a while.
It is now back to normal! Sorry for the convenience, and happy download and installation using OBIEE and SAP/BW drivers!!

Posted by Olivier Bennardo on July 08, 2013 at 06:13 PM SGT #

Took me time to read all the comments, but I really enjoyed the article. It proved to be Very helpful to me and I am sure to all the commenters here! Its always nice when you can not only be informed, but also entertained! Im sure you had fun writing this article.
<a href="http://www.magnifictraining.com/">Hadoop training</a>

Posted by magnific training on August 03, 2013 at 08:03 PM SGT #

Olivier,
Nearly a month ago it started to be available again. We also contacted with Bristlecone. Finally we downloaded and installed these drivers. Now we are testing how such configuration works and where are any restrictions.
Thanks

Posted by guest on August 03, 2013 at 08:16 PM SGT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

A blog focused on Tips & Tricks about Oracle Business Intelligence (OBI), Oracle Exalytics and Oracle Enterprise Performance Management (EPM) products.
[Blog Admin: ahmed awan]

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today