Wednesday 26 November 2014

Date Format Configuration in Obiee11g

Date Format Configuration

1. Backup localedefinitions.xml file in the directory
ORACLE_HOME\bifoundation\web\
display\
Ex - \OBIEE\app\fmw\Oracle_BI1\bifoundation\web\display\localedefinitions.xml
2. After taking a backup of Existing localedefinitions.xml file and Find
dataShortFormat and change the date Format according to your 
Requirement
there are many date Format like
For example I want Date format like 09-Apr-2013
I am changing it to dd-MMM-yyyy 

Note -  There are Multiple Languages in localedefinitions.xml file.Change it according to Requirement

Save the file and re-start all of the BI Services through Enterprise Manager.

Tuesday 25 November 2014

Oracle logo change in Login and Home Page of OBIEE 11g

Oracle logo to Company Logo

Rename your Company Logo to oracle_logo.png and Replace the oracle_logo.png in below Locations
Note : Company Logo should be < 1KB and also Width = 119 and Height = 25


/OBIEE/app/fmw/user_projects/domains/un_bifoundation_domain/servers/bi_server1/tmp/_WL_user/analytics_11.1.1/7dezjl/war/res/sk_blafp/b_mozilla_4
/OBIEE/app/fmw/user_projects/domains/un_bifoundation_domain/servers/bi_server1/tmp/_WL_user/analytics_11.1.1/7dezjl/war/res/sk_blafp/login
/OBIEE/app/fmw/Oracle_BI1/bifoundation/web/app/res/sk_blafp/b_mozilla_4
/OBIEE/app/fmw/Oracle_BI1/bifoundation/web/app/res/sk_blafp/login
/OBIEE/app/fmw/instances/instance1/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/analyticsRes/sk_blafp/b_mozilla_4
/OBIEE/app/fmw/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp/_WL_user/analytics_11.1.1/7dezjl/war/res/sk_blafp/b_mozilla_4

/OBIEE/app/fmw/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp/_WL_user/analytics_11.1.1/7dezjl/war/res/sk_blafp/login

After the replacement of the images cache from Administrative tool should be removed.
Manage>cache>Edit>select all>purge
 Then go to Presentation services and clear the cache and reload server metadata.
Administration>Manage Sessions>Cancel Running Request and Close all Cursors>back>Reload files and Metadata.
Clear all browser history and cache.
Try opening the Analytics url you should see the new logo. If not restart the BI server and then try it.


Thanks

E-mail Configuration (Scheduler) in OBIEE 11g

Configure Email settings:

1. Login to Fusion Middleware Control Enterprise manager (http://yourservername:7001:/em) using Admin user credentials


2. Navigate to Mail tab (Business Intelligence > coreapplication > Deployment>Mail


3. Click Lock and Edit Configuration to enable changes to be made.

4. Complete the elements with the following information.



• SMTP Server – SMTP server of your email (e.g. mail.gmx.com)
• Port – Port of the SMTP server (e.g. 25)
• Display name of sender – Any name(e.g.Oracle Business Intelligence)
• Email address of sender – Sender’s email address (e.g. obiee@gmx.com
• Username – Same as the sender’s email (e.g. obiee@gmx.com)
• Password – password of your email
• Confirm password – confirm the same password as above
• Number of retries upon failure – any number
• Maximum recipients
• Addressing method To, Blind Copy Recipient (Bcc) – if you want to receive a BCC, select it.


Note: If you search a free smtp service, the site Gmx.com is reported as offered a free smtp server which work without the need to upgrade to a professional account as for instance Google and Yahoo ask for.

smtp server : mail.gmx.com
port : 25


5. Click Apply, and then click Activate Changes.


6. Return to the Business Intelligence Overview page and click Restart.

Creating an Agent to send mails:

Since we are going to configure just to test the email settings we did in the above, we create this agent as simple as possible.

Login to OBIEE Web (http://yourservername:7001/analytics)
1.Click New in the Global header and then select Agent and Actionable Intelligence




2.In the General tab set the Priority as Normal




3.In the Schedule tab and then select Once from the Frequency list box.


4. In the Delivery content tab, select the content you want to deliver clicking the Browse button.



5. In the Recipients tab, add emails (you can add external users mails as well) whom do you want to receive a mail with delivery content.




6.In the Destinations tab,select the destinations which include user dashboard and email.




7. Save the agent and Run it.You will be able to run the agent only after saving it. Click the icon shown below for running the Agent.


If it runs successfully recipient get the mail with pdf attachment (we selected pdf format in the Delivery content tab).


Issues faced while doing this:



I had given 2 recipients.The report alert was being delivered only to the dashboard of the user.The report was not delivered to the mail.The issue came because i tried to send using gmail,yahoo mail etc..
Solution:
Select the SMTP server as gmx or give your company SMTP server.

Thanks

Monday 8 September 2014

How to Increase row limit to Display/Export to Excel from Analysis

To Export more than 6500 OBIEE 11g records to Excel, perform the following steps:

1. Backup Instanceconfig.xml file from location:
\instances\instanceun\config\OracleBIPresentationServicesComponent\
coreapplication_obips1\instanceconfig.xml
2. After taking a backup of Existing instanceconfig.xml file and add/update the below xml code in your instanceconfig.xml file.

- specifies the maximum number of cells to be displayed in a view; it must be specified separately for each view type and is applicable to Table and Pivot views. The default is 50,000. The MaxCells should be equal to MaxVisibleColumns (in a pivot view) multiplied by the MaxVisibleRows.

- specifies the maximum number of pages included in a view when it is exposed via a Dashboard; the default is 1000.

- Applicable to the narrative view, or ticker, this element specifies the maximum number of records that can be processed to create a view; the default is 40,000.

> - specifies the maximum number of view prompts (or pages in a PDF) to be displayed for a Chart, Table or Pivot; the default is 1000 Pages.

- specifies the maximum number of rows to be displayed in a chart, pivot or table; the default is 500.

- specifies the maximum number of sections to be displayed in a chart, pivot or table; the default is 25 sections.

- specifies the maximum number of columns displayed in a chart of pivot table; the default is 300.

- specifies the default number of rows to display in a view. It can be applied to a Narrative, Pivot, Table or Trellis; the default is 25. This number should not exceen MaxVisibleRows.

- specifies the maximum number of rows to display in a view when it is exposed via a Dashboard. Applicable to a Pivot or Table, the default is 100.

- specifies the maximum number of rows included in a view when it is exported, such as a PDF or Excel export. It is applicable to a Pivot or Table and the default is 65,000.

- specifies the maximum amount of data sent to the browser for a chart. It is not relevant to any other view object.

Cube settings affect the display and processing of data in pivot tables and charts. Cube settings are listed within their own element tags, cube. In this way they are different to other tags that are largely reused between different elements.

 - specifies the maximum number of records returned for a view to then process. The default is 40,000 records.

 - specifies the maximum number of data cells that can be populated in a view; the default is 120,000 cells.

3. Save the file and re-start all of the BI Services through Enterprise Manager

OBI Mobile App Designer Installation

OBI Mobile App Designer Installation

The Oracle BI Mobile App Designer complements BI Mobile HD and is packaged with BI Foundation Suite and the BI Mobile option to OBIEE at no additional cost.
Follow the below steps to install Oracle BI Mobile App Designer:

1.     Prerequisites For Mobile Apps:

Download the required Patch for Mobile Apps:
  • Patch 16556157: OBIEE 11.1.1.7.1 [If your version of Oracle BI EE is not 11.1.1.7.1, download OBIEE BUNDLE PATCH 11.1.1.7.1 from My Oracle Support].
  • Patch 17004920 To support Oracle BI Mobile App Designer with Oracle BI Web Catalog, Apply OBIEE 11.1.1.7.1 MLR
  • Patch 17220944 - Download Oracle BI Mobile App Designer patch 17220944 from My Oracle Support, enabled through extending the OBIEE Weblogic domain

2.      Installation Steps:

1.      Stop All OBIEE 11G services (Weblogic Admin Server, Managed Server and OPMN services)
2.      Apply OBIEE 11.1.1.7.1 MLR Patch 17004920 using OPatch utility.
3.      Apply OBI Mobile App designer Patch 17220944 using OPatch utility.
4.      Deploy the OBI Mobile App Designer (MAD) manually using WebLogic configuration assistant as shown in below:
Open Command prompt window and Navigate to MW_HOME>\Oracle_BI1\common\bin\
Run ‘config.bat’ to start the Weblogic configuration assistant tool.
On welcome screen, select ‘Extend an existing Weblogic domain‘ and click Next.
Choose the domain to extend, for example: bifoundation_domain
Choose Extend my domain using an existing extension template and Set the Template Location to: <MW_HOME>/Oracle_BI1/common/templates/applications/oracle.bimad_template_11.1.1.jar
On Configuration summary, review the deployment details and click “Extend” button.
Upon successful configuration, you see the following screen. Click “Done” to close this window.
Great. This concludes the OBI MAD application deployment in our OBIEE 11G application. Now we need to update the Security Configurations for OBI MAD. This is mandatory step to use OBI MAD in OBIEE 11G presentation services.

3.     Update Security Configuration for Oracle BI Mobile App Designer:

This is a Python script to update the OBIEE 11G domain (bifoundation_domain) system JAZN file (system-jazn-data.xml) with the security grants required for BI Mobile App Designer. This step is required only the first time you apply the patch.
Navigate to <MW_HOME>\Oracle_BI1\bifoundation\install and run the command: <MW_HOME>\Oracle_BI1\common\bin\wlst.cmd addMADCodeGrants.py t3://<hostname>:7001 <weblogic_Admin_Username>
After successful execution, Start All OBIEE 11G services (Weblogic Admin, Managed servers and OPMN)
Once the services are started, Login OBIEE 11G analytics (http://hostname:9704/analytics)
Right after, you logged into OBIEE 11G, click the ‘New’ Menu. In this you will see a new application category called “Mobile Application” and you see the “Mobile App” module. Click on that to start design and developing the reports.

4.     Creating Basic Mobile App

In the left navigation pane, under Create, click Mobile App to start the Mobile App Designer.
The Create App dialog box is displayed. Under "Choose Target Device Type," select Tablet.
On the next page, select the data source:
  1. Under "Choose a data source for your App," select BI Subject Area.
  2. In the Subject Area drop-down list, select Sample Sales Lite.
Click Save to open the Save As dialog box.
Save the app as OBE_Demo in My Folders, and then click OK.
Open the OBE_Demo Mobile App report. Notice that the data source elements are listed in the navigation pane on the left side of the designer. You can drag and drop columns from the data source to the workspace to build the elements of your application.
Notice that the pages of the presentation are displayed in a sidebar, similar to presentation programs such as Power Point or Keynote. By default, a new app contains only a cover page.
You can add pages to your app using either the provided layout options, or you can insert a blank page and design a custom layout. In the following steps, you add a page with a bar chart that shows revenue by quarter, a pie chart that shows revenue by organization, and a table that shows revenue detail by quarter, product type, and product.
On the Insert tab, select New Page > 3 Cells.
Creating Chat View in Mobile Apps
A second page is added to the app. Select the first cell.
In the ribbon, click the Insert tab, and then click Chart.
Note: You can also drag and drop the chart icon from the ribbon to a cell in the layout pane.
Specify the subject area columns to define the chart:
  1. From the Sample Sales Lite hierarchy, drag Per Name Qtr (located under Time) to the Label area of the chart.
  1. From the Sample Sales Lite hierarchy, drag Revenue (located under Base Facts) to the Value area of the chart.
Resize the chart and hide the chart legend
  1. Drag the resize handle on the lower right corner of the chart to resize the chart to fit the cell.
  1. On the ribbon, click the Chart tab, and then select Legend > No Legend.
The legend is removed from the chart.
Next, insert another chart. On the Insert tab, drag and drop the Chart icon to the second cell in the layout grid.
Specify the subject area columns to define the chart:
  1. From the Sample Sales Lite hierarchy, drag Revenue (located under Base Facts) to the Value area of the chart.
  1. From the Sample Sales Lite hierarchy, drag Organization (located under Offices) to the Label area of the chart.
  1. In the chart, drag Organization from the Label area to the Series area to view the Organization data as a series instead of individual bars.
On the Chart tab, select Chart Types > Pie > Pie to change the chart display type.
The following chart types are available:
  • Area
  • Bar (default)
  • Bubble
  • Line
  • Pie
  • Circular
  • 3D Graphs
  • Funnel
Drag the resize handle to resize the pie chart to fit the cell.
Next, insert a table. On the Insert tab, drag and drop the Table icon to the third cell in the layout grid.
Creating Table View in Mobile Apps
Drag the following columns from the data source to the table:
  • Per Name Qtr (located under Sample Sales Lite > Time)
  • Product Type (located under Sample Sales Lite > Products)
  • Product (located under Sample Sales Lite > Products)
  • Revenue (located under Sample Sales Lite > Base Facts)
Customize the table formatting
  1. Double-click the column header Per Name Qtr to edit the header. Replace Per Name Qtr with Quarter.
  1. Drag the column edges to resize the table columns.
  1. Select the data in the Revenue column to display the Column tab in the ribbon.
  1. On the Column tab, in the Data Formatting drop-down list, select -1,237.57 (Number).
Renaming the Page:
In the Pages list, double-click Page 2 to edit the page name. Replace Page 2 with Analysis.
Notice that when you press Enter, the page header in the layout pane also changes to Analysis.
Click the Save icon to save your app.

Click Preview to open a web preview of your app. Note, you can preview in a new Window too.
If you have a QR Code scanner app on your tablet device, preview the app on your tablet instead of on the web.
  1. Click On Mobile.
  1. The QR code for the app preview is displayed. Use a QR code scanner on your tablet device to scan the code. This opens the app preview on your tablet device. Note: If you do not have a QR code scanner app on your tablet, you can copy the app URL (displayed under the QR code) and e-mail it to your mobile device.
Clicking on an item in the web-based preview is equivalent to tapping the same item when the app is open in a tablet. Because you can also preview your app in a tablet, the instructions for previewing your apps in this tutorial use the verb "tap" instead of "click."


The Analysis page is displayed. Notice that the preview displays your two charts and the table you created.

Friday 27 June 2014

OBI APPS 7963 EXTENSION PACK INSTALLATION AND CONFIGURATION GUIDE



1.     Overview

This document describes the steps to Install and configure the Oracle BI Applications 7.9.6.3
Extension pack alongside a new or existing implementation of Oracle BI Applications 7.9.6.1,
7.9.6.2 or 7.9.6.3. The instructions contained in this document describes how to create the data warehouse schema, install the Informatica mappings, install and configure the DAC containers and merge instructions for the Oracle Business Intelligence Enterprise Edition (OBIEE) RPD. This document only covers the installation and configuration specifics for the Oracle BI Applications 7.9.6.3 Extension Packs, for all other related installation and configurations questions refer to the Oracle BI Applications Configuration Guide for Informatica Power Center Users for the associated BI Applications version which can be obtained on OTN (link) or via the original software Media Pack provided by Oracle.
The Manufacturing Module in the Oracle 7.9.6.3 Extension pack is pre-integrated with Oracle E- Business Suite Manufacturing and the EAM module in Oracle 7.9.6.3 Extension pack is pre- integrated with Oracle E-Business Suite Enterprise Asset Management (EAM) module, as well
as IBM Maximo 6.5.

2.     Pre-Requisites

In order to install the Oracle 7.9.6.3 Extension pack at least one module of Oracle BI Applications versions 7.9.6.1 to 7.9.6.3 has to be installed.

3.     Downloading the Extension Pack

The Oracle Business Intelligence Applications 7.9.6.3 Extension Pack can be downloaded from the Oracle eDelivery site. On downloading, you will get a zip file by name OracleBIA_7963_Extn_Packs.zip. Extracting the zip will give three zip files, each corresponding to extensions for Oracle BI Applications Versions 7961, 7962 and 7963.
For installation, please use the zip file that corresponds to the version of Oracle BI Applications your organization has deployed.  Oracle recommends that all new deployments use version
7.9.6.3.

OBIA Version                                                     Extension Pack Zip

7961                                                                          Oracle7961_Extn_Pack.zip

7962                                                                          Oracle7962_Extn_Pack.zip

7963                                                                          Oracle7963_Extn_Pack.zip


4.     Installation

a)   Preparing the Staging Area

Extract the zip that corresponds to your Oracle BI Applications version using a unzip utility. You will get a folder called ‘Oracle 796x_Extn_Pack’ with the following folder structure. Oracle_796x_Extn_Pack
Informatica
  • SDE_ORAR12_Adaptor_Extn 
  • SDE_ORA11510_Adaptor_Extn 
  • SDE_MAXIMO65_Adaptor_Extn 
  • SILOS_Extn
  • PLP_Extn


DAC
  •   OracleR12Extn .zip   
  •   Oracle11510Extn.zip  
  •   Maximo 65 Extn.zip

 RPD
  • OracleBIAnalyticsApps_Extn.rpd (for 7961 and 7962)
  • EnterpriseBusinessAnalytics_Extn.rpd (for 7963)

Webcatalog  
EnterpriseBusinessAnalytics_Extn.webcat
Unless otherwise noted in this document, the R12 Informatica and DAC folders contain objects that are compatible with Oracle EBS R12, R12.1.1, R12.1.2 and R12.1.3

b)   Backing up the current installation

This section provides backup steps you need to perform before you begin the installation process for the Extension pack.


Rename and copy into a different location your current repositories, Presentation Catalog (formerly known as the Web Catalog) and DAC installation folder from your existing environment. The file names and locations listed below represent the standard names and locations of files that shipped with Oracle BI Applications.
When you back up the DAC Repository, you export the DAC metadata, in XML format (using the DAC's Export tool), into a different database, which can be used later as a reference.

c)    Installing Informatica Workflows

Open the repository in which Oracle BI Applications 796x has been installed. The repository can be opened through the Informatica Repository Manager tool (pmrepmgr.exe)
Create new Informatica folders in the repository with names as below
SDE_ORAR12_Adaptor_Extn SDE_ORA11510_Adaptor_Extn SDE_MAXIMO65_Adaptor_Extn SILOS_Extn
PLP_Extn
Verify the code page of the Informatica Repository. The extension XMLs are shipped

with code page of ‘UTF-8’. If the code page of your repository is different from the above, please change the code page of the extension XML’s to the required code page. You can
do it by editing the REPOSITORY tags of the extension XMLs.

E.g. Open the extension XMLs and in the Repository tag mentioned below the CODEPAGE Attribute need to be   modified to the required code page.
<REPOSITORY NAME="BIApps_QA" VERSION="181" CODEPAGE="UTF-8" DATABASETYPE="Oracle">

Select 'Repository Import Objects' option. Import the xmls from the staging into the respective folders created with the same names in the repository.  Please check in the XMLs during the import process.
For E.g:   XMLs in Staging Area->Oracle_796x_Extn_Pack->Informatica->SILOS_Extn should be imported to the SILOS_Extn folder created in Informatica.

In the Import Dialog Box that follows, you will be presented with a list of folders for importing. Please choose only the folders with the _Extn extension
While importing, you will encounter conflicts for Default Session Configurations and Reusable Transformations like Mapplet, Lookups etc which are referred from Oracle BI Applications folders. Please check the Reuse box for resolving these conflicts

d)   Configuring Informatica Workflows



Configuring the Helper File


Extract the QA_HELPER file from Staging Area-> Oracle_796x_Extn_Pack->Informatica>Config_Files folder and add values for organization_id, collection_element and target_column fields. After adding values save it in the following location in the Informatica server.
INFA_HOME/server/infa_shared/SrcFiles



Assigning the Integration Service


Open Workflow manager to assign an Integration service to the workflows imported into the
Extension folders. You can reuse the integration services created for Oracle BI Applications.


Close all the folders in the repository. Select Assign Integration Services from the Service Menu. In the resulting window, map the folders imported to the appropriate integration service and click Assign.  The following folders need to be mapped to the appropriate integration services.
SDE_ORAR12_Adaptor_Extn SDE_ORA11510_Adaptor_Extn SDE_MAXIMO65_Adaptor_Extn SILOS_Extn

                            PLP_Extn

 





As part of implementing Oracle BI Apps 796x, you would have created a custom container to hold customizations done on Oracle BI Applications. If this is the first time Oracle BI Applications is being implemented, please create a new container as a copy of the source system container that you wish to implement. This is called the Production’ container. The container that is shipped as part of Oracle796x Extension pack is termed as the ‘Extension’ container.
The DAC sub folder under the Oracle796x_Extn folder in the Staging Area contains Extension
Containers. These containers contain extracts from
·         Manufacturing and EAM for R12 and 11510 versions of Oracle E-Business suite
·         EAM for IBM Maximo 65.
Pick the appropriate extension container depending on the version of Oracle E-Business Suite and/or the IBM Maximo that you are running.

Go To Tools -> DAC Repository Management -> Import

Import the Extension Container
Select ‘Logical’ check box only while importing the Extension Container
Now, the repository should have the _Extn container in addition to the other containers.



f)     Configuring the DAC Container



Creating tables in the Data Warehouse
Navigate to Tools->ETL Management -> Configure and select the option Create/Upgrade Data
Warehouse Tables.


In the screen that follows, provide the name of the Extension Container and the data warehouse connection details.



  Creating References
Switch to the production container and create references for the following objects from the
Extension Container as shown in the below screenshot.




·         Reference all the Source system folders
·         Reference all Table definitions.
·         Reference all Index definitions
·         Reference all the Tasks
  After referencing, the table types of source tables for tasks will be missing. Please refer the Extension container for the correct table types and change accordingly. Here is the navigation
Go to Tasks –> Sub tab Source Tables Select Type
·         Provide referential integrities for the Extension tables by referring the Extension container manually.


·         If you are implementing the R12 Extension Container, please create an additional  task group TASK_GROUP_Extract_MfgResource in the merged container with the following tasks as child tasks and dependency order as 1 and 2 respectively.  Set Truncate Always’ option for this Task group.
1.   SDE_ORA_MfgResource
2.   SDE_ORA_MfgResourceDimension_CRResource_Process
·         Modify the seeded Task group TASK_GROUP_Extract_CodeDimension’ in the Production container and add the following tasks as child tasks.
1.   SDE_ORA_CodeDimension_KanbanCardStatus
2.   SDE_ORA_CodeDimension_KanbanCardType
3.   SDE_ORA_CodeDimension_KanbanDocumentType
4.   SDE_ORA_CodeDimension_KanbanErrorCode
5.   SDE_ORA_CodeDimension_KanbanSourceType
6.   SDE_ORA_CodeDimension_KanbanSupplyStatus
·         Reference all the Subject areas and Assemble them individually



Disabling Tasks and Subject Areas
Subject Area
Requires Oracle BI Applications License
Manufacturing-Costing
Manufacturing-Discrete Manufacturing-Discrete Quality Manufacturing-Inventory Manufacturing-Kanban Manufacturing-Planning
Manufacturing Analytics
Asset Maintenance
Enterprise Asset Management Analytics

Please disable/inactive the un-licensed subject areas and tasks by referring to the matrix below

























Table Name





DAC Task Name
Requires Oracle BI Applications License
W_PURCH_ORDER_F
SIL_PurchaseOrderFact, SIL_PurchaseOrder- Fact_SoftDelete, SDE_ORA_PurchaseOrder- Fact, SIL_PurchaseOrderFact_IdentifyDelete, SDE_ORA_PurchaseOrderFact_Primary
Procurement and Spend Analytics



W_PURCH_SCHEDULE_LINE_
F
SIL_PurchaseScheduleLinesFact, SIL_Pur-
chaseScheduleLinesFact_SoftDelete, SDE_ORA_PurchaseScheduleLinesFact, SIL_PurchaseScheduleLinesFact_IdentifyDe- lete, SDE_ORA_PurchaseScheduleLinesFact_Pri mary
Procurement
and Spend
Analytics
W_SALES_ORDER_LINE_F
PLP_SalesOrderLinesAggregate_Load,
PLP_SalesOrderLinesAggregate_Derive, PLP_SalesOrderLinesFact_Customers_First_ Order_Update, PLP_SalesOrderLinesFact_InvoicedQty_Up- date, PLP_SalesOrderLinesFact_RollupAmt_Up- date, PLP_SalesOrderLinesFact_ShippedQty_Up- date,
SIL_SalesOrderLinesFact, SIL_SalesOrderLinesFact_SoftDelete, SDE_ORA_SalesOrderLinesFact, SIL_SalesOrderLinesFact_IdentifyDelete, SDE_ORA_SalesOrderLinesFact_Primary, PLP_SalesOrderLinesAggregate_Derive_Pos tLoadImage, SIL_SalesOrderLinesAggregate_Derive_Pre- LoadImage, SIL_SalesOrderLinesAggregate_Derive_PreS oftDeleteImage
Supply Chain
and Order Management Analytics

Building the Execution Plan
Build a new Execution Plan with the Subject Areas from existing execution plan and the extension subject areas. After generating parameters, set appropriate values for parameters during the build.





Verifying the Source System Parameters
Oracle BI Applications 7.9.6.3 Extension Pack requires common dimensions like Organization, Product and Time to be loaded. For more details please refer to the corresponding version of the Oracle BI Applications Configuration Guide for Informatica PowerCenter Users that can be obtained on OTN (link).






Please ensure that the following Task level parameters are set for following tasks

Task                                                                              Parameter SDE_ORA_ProductDimension                                Master_org SIL_DayDimension                                                    START_DATE, END_DATE


g)   Configuring the RPD and Webcatalog Objects



a)   RPD Merge
An RPD merge is only required for adding Oracle BI Applications 7.9.6.3 Extension Pack release to a customized BI applications implementation.  If this is the case please follow the instructions below.  Otherwise it is advised that you use the RPD that has been shipped in the Oracle BI Ap- plications 7.9.6.3 Extension Pack as your Production RPD.


A three-way merge should be performed to integrate the contents of the Production RPD and the Extension RPD. The instructions to do a three-way merge are given below.


For  7961 and 7962 (10g  10.1.3.x.x)


·         In the BI Administration tool, open the OracleBIAnalyticsApps_Extn.rpd.
·         Select the menu File > Merge
·         Select the Original Repository (BI Apps seeded RPD). This is the RPD that was extracted from the Oracle Installer for 796x.
·         Once the original repository is selected, the Merge Repositories window appears. Note that the OracleBIAnalyticsApps_796_Original repository is reflected in the Original repository field. Also, note that the changes made in the current repository are listed.
·         Click the Select button beside the Modified repository field to select the modified RPD file [ Production RPD]







·         Now click the Select button beside the “Save merged repository as” field, to give the desired name for the merged repository which will be created as a result of this merge process.
·         You can make the decision to select the changes in the current repository or modified repository appropriately. Scroll to the right to see the Decision column and select Modified or Current from the drop down list.





For  7963 (11g 11.1.1.6.2)

1) In the BI Administration tool, open the OracleBIAnalyticsApps_Extn.rpd.(7963_Extn)
2) Select the menu File > Merge
A screen will appear asking Original Modified and Merged Repository Details as shown below



3) Select Merge Type as Full Repository Merge, Equalize During the Merge (Optional)
4) Select the Original Repository (BI Apps seeded RPD). This is the RPD that was extracted from the
Oracle Installer for 7963.
5) Select Modified Repository field to select the modified RPD file [Production RPD]
6) Provide desired name for the merged repository which will be created as a result of this merge process. Click Next



7) You can make the decision to select the changes in the current repository or modified repository appropriately.
Scroll to the right to see the Decision column and select Modified or Current from the drop down list.

Click on Finish to Complete the Process


a)    Catalog Merge


A webcatalog merge is required only for a customized BI applications implementation. Otherwise it is advised that you use the Webcatalog that has been shipped in the Oracle BI Applications 7.9.6.3 Extension Pack. Here are the steps for Catalog Merge.
1)  Choose File->Open Catalog to open the Production catalog in offline mode.


2)  Open  the  Extension  Web  Catalog  from  the  Staging Area  in  offline  mode  using  the
Catalog Manager.
3)  Copy the folders from the Extension Web Catalog into the Production Web Catalog.