12/12/2019 working with BICC to resolve extract issues | Oracle BI Applications

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:

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Close and accept

https://biapplications.wordpress.com/2019/02/15/working-with-bicc-to-resolve-extract-issues/ 1/7
12/12/2019 working with BICC to resolve extract issues | Oracle BI Applications

#ExploreFrance #ExploreFrance
What to do and see What to do and see
on the Côte d'Azur on the Côte d'Azur

REPORT THIS AD REPORT THIS AD

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
Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
The
To find out following
more, section
including how toshows
controlacookies,
step-by-step approach
see here: Cookie to fix these errors within BICC:
Policy

remove PVO from offering Close and accept

https://biapplications.wordpress.com/2019/02/15/working-with-bicc-to-resolve-extract-issues/ 2/7
12/12/2019 working with BICC to resolve extract issues | Oracle BI Applications

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

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:

Privacy &OnCookies: This sitepage,

the following uses cookies. By continuing
the associated to use
offerings is this website,
listed in theyou agree
(right) to their menu
selected use. box. The
To find out more, including how to control cookies, see here: Cookie Policy
associated offering can be removed from the PVO, to exclude it from the next extract run of the
OBIA module (offering):
Close and accept

https://biapplications.wordpress.com/2019/02/15/working-with-bicc-to-resolve-extract-issues/ 3/7
12/12/2019 working with BICC to resolve extract issues | 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:

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Close and accept

https://biapplications.wordpress.com/2019/02/15/working-with-bicc-to-resolve-extract-issues/ 4/7
12/12/2019 working with BICC to resolve extract issues | 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:

#ExploreFrance #ExploreFrance
What to do and see What to do and see
on the Côte d'Azur on the Côte d'Azur

REPORT THIS AD REPORT THIS AD

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”:

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Close and accept

https://biapplications.wordpress.com/2019/02/15/working-with-bicc-to-resolve-extract-issues/ 5/7
12/12/2019 working with BICC to resolve extract issues | 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.

Advertisements

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Close and accept

https://biapplications.wordpress.com/2019/02/15/working-with-bicc-to-resolve-extract-issues/ 6/7
12/12/2019 working with BICC to resolve extract issues | Oracle BI Applications

REPORT THIS AD

Advertisements

REPORT THIS AD

SHAR E T HIS:

 Print  Facebook  Twitter

Like
Be the first to like this.

RELAT E D

extracting data from Oracle Exporting & Importing BICC

Fusion cloud for Oracle BI from one environment to
Applications with BICC another Working with OBIA-CM and
In "OBIA on PaaS" In "OBIA on PaaS" Domain Member mappings
In "OBIA on PaaS"

This entry was posted in OBIA on PaaS and tagged BICC, biccc, Fusion Applications,
fusion cloud, OBIA, Oracle, pvo by Gerhard Herrmann. Bookmark the permalink
[https://biapplications.wordpress.com/2019/02/15/working-with-bicc-to-resolve-extract-
issues/] .

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Close and accept

https://biapplications.wordpress.com/2019/02/15/working-with-bicc-to-resolve-extract-issues/ 7/7