Exporting & Importing BICC from one environment to another

Within BICC the PVO is associated with the Oracle BI Applications (OBIA) offering:

E.g. the below example shows that CrmAnalyticsAM.ActivitiesAM.ActivityObjectives is associated with: Human Resource, Sales and Service. Thus, the PVO will be included in these OBIA modules and a text file containing the data will be placed on UCM:

image

The configuration/customizations done in BICC can also be exported using the top right menu:

image

which will provide a zip file e.g. exportCust_2019-02-06_09_57_58.zip

The zip file contains multiple .csv file which export the configuration of BICC:

image

However, none of these backup files will contain the assocation between a PVO and a out-of-the-box (seeded) OBIA offering like Human Resource, Sales or Service. These backup files would only contain a PVO which is associated with a newly (custom) created offering:

image

In practical terms this means, that in order to export/import the association of PVOs with offerings from one environment to another, a new offerings needs to be created and that all the PVOs that should be included must be manually added to this new offering.

Thus, there is not a possibility to deploy all customization conducted in BICC from one environment to another.

Other customization like deselecting attributes from PVOs (to not include them in the BICC extract) are part of the export/import functionality and thus can be deployed from one environment to another.

extracting data from Oracle Fusion cloud for Oracle BI Applications with BICC

the data extract from Oracle Fusion cloud is managed by the Fusion BI Cloud Connector (BICC). This console can be access by the following typical URL: https://customername.fa.datacenterregion.oraclecloud.com/biacm/

For the login a dedicated user is recommended e.g. BICC_ADMIN, since this user will be used to create the extract. According to the documentation, this user must be assigned with the following application roles in order  to inherit the required permissions for running the extract:

  • ORA_ASM_APPLICATION_IMPLEMENTATION_ADMIN_ABSTRACT
  • OBIA_EXTRACTTRANSFORMLOAD_RWD

This user is typically created by the Fusion team and given to the BI team. The BI team can validate the assigned roles by logging in to the following url:
https://customername.fa.datacenterregion.oraclecloud.com/cs/

and clicking on the user name in the top right corner. This will list all the assigned application roles to the user:

image

After validating the user, the Oracle BI Application modules need to be selected within BICC for extraction. This can be done by clicking on the calender icon of the top right menu and clicking on Global Data Store List.

image

This opens the page to enable the Oracle BI Application product offerings / modules within BICC for Fusion cloud extract. The offering must be selected from the drop down list and then be enabled for extract.

image

After all required modules have been selected, the modules can be extracted to UCM (this is the bundled file storage of any Fusion Cloud instance and may be used by multiple Fusion modules e.g. the data import to Fusion Cloud itself). The extract can be configured by clicking on Manage Extract Schedules on the top right menu.

image

This opens the schedule of extracts pane. A extract job can be created from this pane:

image

A new extract can be created by clicking the plus icon on the top pane. This will open a guided workflow, which allows to select the modules which should be extracted. E.g. in an initial project phase you may only choose to extract (run) a single module extract, while you have actived multiple modules. For example the project consists of Financials, Supply Chain, Procurement, but only the Procurement module is scheduled for extract.)

imageThen selecting immediate as recurrence setting the job will be run after saving it.

In case of errors with the extract, the log can be downloaded by clicking the help icon in the top right area of the screen:

image

and by clicking download latest log:

image

The log file may then provide further insight into any issues with the extract:

image

For further reference, please check: