BICC Extract
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.datacenter.oraclecloud.com/biacm/
When logging into BICC with above
example URL, the following screen is shown as starting page:
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
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):
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 extractand selecting the offering from the drop-down menu:
The removed PVO will no longer be
part of a extract run:
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:
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. 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”:
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.
