10/14/21, 4:44 PM pvo | Oracle BI Applications

TA G A RCHI V ES : PV O

Exporting & Importing BICC from one

environment to another
Posted on 8. March 2019

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:

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

https://biapplications.wordpress.com/tag/pvo/ 1/8
10/14/21, 4:44 PM pvo | Oracle BI Applications

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:

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:

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.

https://biapplications.wordpress.com/tag/pvo/ 2/8
10/14/21, 4:44 PM pvo | Oracle BI Applications

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.

Posted in OBIA on PaaS | Tagged BICC, biccc, pvo, ucm | 1 Reply

working with BICC to resolve

extract issues
Posted on 15. February 2019

in order to extract data from Oracle Fusion Applications Cloud, BICC needs to be used. This is
part of every Fusion Applications Cloud and is typically reachable by extending the URL with
/biacm e.g.

https://pod-environment.fa.datacenter.oraclecloud.com/biacm/

When logging into BICC with above example URL, the following screen is shown as starting page:

This is indeed the Review Cloud Extract Configuration page of the top right navigation menu and
allows to click on a PVO (Data Store) to further check the configuration of the PVO in terms of
associated offerings (OBIA modules) and to be selected attributes (columns) of the PVO (Public
View Object).

When starting with a OBIA implementation project, upon the first initial login, the required OBIA
modules need to be enabled with the Global Data Store List from the navigation menu:

https://biapplications.wordpress.com/tag/pvo/ 3/8
10/14/21, 4:44 PM pvo | Oracle BI Applications

The offerings (OBIA module) can be selected from the drop down menu and the respective PVOs
can be enabled for extract:

This will enable the PVO for use within BICC and the extraction process. In the background these
PVOs are created, additionally they will also be associated with the respective OBIA Modules,
hence for an OBIA implementation of Human resources, only the required PVOs for HR are
extracted from Fusion Cloud.

However, the BICC extracts may fail due to errors which require to execute some tasks within
BICC, to fix the Errors as workaround. These tasks include:

remove a PVO from an associated offering (OBIA module)

deselect columns for a PVO

The following section shows a step-by-step approach to fix these errors within BICC:

remove PVO from offering

A typical reason to remove a PVO from an offering may be due to the following error:

ORA-00942: table or view does not exist 

https://biapplications.wordpress.com/tag/pvo/ 4/8
10/14/21, 4:44 PM pvo | Oracle BI Applications

This error can be resolved by navigating to the start page of BICC or the Review Cloud Extract
Configuration link from the navigation menu. The PVO name of the error log can be copied to the
Data store field to search. To configure the PVO and the association with the offering the icon right
to the name or the name itself can be clicked:

On the page of the PVO click edit:

On the following page, the associated offerings is listed in the (right) selected menu box. The
associated offering can be removed from the PVO, to exclude it from the next extract run of the
OBIA module (offering):

https://biapplications.wordpress.com/tag/pvo/ 5/8
10/14/21, 4:44 PM pvo | Oracle BI Applications

After removing the associated offering from the PVO, the customization can be saved and on the
following screen of PVO summary, the PVO can be closed by clicking “Done” to get back to the
Review PVO page.

The above method of customization, will permanently remove the PVO from the offering (OBIA
Module). When scheduling a subsequent extract run, the removed PVO will not be part of the
offering. This can be validated when creating a new extract (from Manage Extract Schedules) and
selecting the offering from the drop-down menu:

The removed PVO will no longer be part of a extract run:

https://biapplications.wordpress.com/tag/pvo/ 6/8
10/14/21, 4:44 PM pvo | Oracle BI Applications

This Data Store List screen can also be used for temporary test of deselecting a PVO from a
offering (OBIA module) extract. Typically, the OBIA module is selected from the offering drop-down
menu and the enabled for Extract checkbox in the header of the table is clicked to enable all
associated PVOs for extract, but an individual PVO can also be deselected for the list, to only
affect this specific run (e.g. for temporary testing purposes). Thus, a PVO can be removed from a
offering for all subsequent runs or just an specific run (using the Data Store List of the Manage
schedule screen).

deselect columns from a PVO

Another common error are missing columns from a PVO e.g. because they are obsolete after an
upgrade or not used anymore. The following error is show within the BICC logs:

FscmTopModelAM.PjtProjectPlanAM.ProjectPlanIntegrationPVO – Missing columns –

[DeliverableTypesBPEOLastUpdateDate1, ProjPlanLinePEOLastUpdateDate2]

or:

ORA-00904: “COLLABORATIONENTRIESHISTPEO”.”COLLAB_ENTRY_VERSION”: invalid

identifier

In the latter case, the physical column first needs to be mapped to a attribute (field) of the PVO in
order to deselect the attribute from the select list. This is most reliably done by create an SR wth
Oracle Support. After the attribute has been identified, the attribute can be deseleted from the
PVO by going back to the Review Cloud Extract Configuration screen and searching for the
respective PVO. Once the PVO name has been clicked (like in above section) the PVO summary
page is shown. From this page the PVO can be edited by clicking “Edit”:

https://biapplications.wordpress.com/tag/pvo/ 7/8
10/14/21, 4:44 PM pvo | Oracle BI Applications

After clicking next to the select column page, the configuration of columns is shown for the PVO:

First, it is recommended to make the highlighted columns visibile to check if an attribute is used for
the select list, as primary key or within the incremental filter. The attribute name can then be used
to search for the attribute which needs to be deselected:

After deselecting the checkbox e.g. of Select List, the PVO needs to be saved. These changes will
then be saved for the next extract run with BICC where the  deselected attribute will not be part of
the select statement and thus not be retrieved. Since, this column hasn’t been available and
caused the extract issue, the issue has been fixed by also deselecting the attribute from the PVO
definition.

Posted in OBIA on PaaS | Tagged BICC, biccc, Fusion Applications, fusion cloud, OBIA,
Oracle, pvo | Leave a reply

https://biapplications.wordpress.com/tag/pvo/ 8/8