R13.x Deprecated and New BI View Objects
Summary
This posting includes R13 deprecated Business Intelligence View Objects (BIVOs) that are unavailable for extraction using BI Cloud Connector (BICC) in Oracle Applications Cloud. It also includes new BIVOs and columns, including which are selected for extraction in BICC.
Content
This posting is applicable to customers using BICC to extract data from Oracle Applications Cloud. The spreadsheets in this posting are published by Oracle BI Cloud Adapter Development. They document deprecated, inactive, and new BIVOs. Deprecated BIVOs and BIVO columns that are inactive are unavailable for extraction using BICC in Oracle Applications Cloud. Customers can use these spreadsheets to research deprecated and inactive VOs to exclude them from BICC extracts, and to understand the new BIVOs and columns available for extraction.
Additionally, use the following guides that describe the view objects and attributes:
Comments
-
Hi Rohan
Thank you for this article and the list of changes.
If Fusion is SAAS why don't Oracle Corp exclude these VOs as part of the patching on Fusion?
Many Thanks
Stuart
0 -
Hi Rohan, how about release 13_21? Thanks
0 -
Hi,
I am looking for latest 21X BIVO list for ERP (Financials, Procurement, Projects and HCM). Any link where I can download the latest listing. Appreciate your help
Thanks
Rizwan
0 -
Hello Rohan
Do you ahve idea about 22A BIVO list
Regards
Rahul
0 -
Any updates on 22B List?
0 -
Hi All,
How do we go about asking to add fields to certain view objects? Is there a feature request that can be put in, if so how is this done?
For example I would like the FundingAllocationId added to the FscmTopModelAM.PrjExtractAM.PjcBiccExtractAM.ExpenditureItemExtractPVO view object.
Any insight would be greatly appreciated.
Thank you.
0 -
Hi All,
I understand VOs are added/deprecated. Does Oracle ever add/remove columns from an existing VO? If so, are there ever cases where a column is added and then enabled by default so would automatically be included in a custom offering that was created with that VO?
Thanks
0 -
Columns get added all the time, the depreciation document lists additions to the VO's as well, and some of them are selected on the VO by default, but to my knowledge, it will never alter a job already setup. So if you already have a configured VO, it will stay that way until you alter it.
0 -
If the VO is marked as customized then changes made by Oracle to seed data/starter selections will not get included in extracts. Best practice would be to edit/close (touch, don't need to actually make a change) to get the VO marked as customized. That way any changes coming from Oracle will not affect your extracts/jobs.
0 -
Does anyone have any experience around using the extract vs. nonextract PVOs for data extraction? For certain areas like planning where there are no ExtractPVOs would it be OK to use the non-extract PVOs? How often do these non-extract PVOs change or get deprecated and if they do change often, then is using BIP a better approach to extract data in bulk for data warehousing use cases?
0 -
The primary reason we are moving to extract from the OTBI PVO's is fewer issues with things like determining primary keys, duplicate data, etc. The Extracts have fewer issues in our experience.
As for changes to the extracts, they add columns, but removal of columns isn't a big issue (at least for us right now). The bigger one is determining how to wire up one or more tables to get back to what we had in the original OTBI version of the download.
0 -
Thanks Dave for those insights. We are in the process of developing a data warehouse using Oracle Fusion SCM Cloud as a source and are trying to determine what the best data extraction mechanism (BICC Extract vs. BICC non-extract vs. BIP) for each of the key procurement cloud table is.
I noticed that in certain cases, even the Extract PVOs do not get all the columns from the Oracle cloud base table (ex: SupplierExtractPVO does not get all the columns from POZ_SUPPLIERS). Even Flex Fields are not straightforward to extract using BICC.
Given some of the limitations around using BICC, would using a tool like SplashOC https://splashbi.com/splashoc/ that replicates the data in the core Oracle cloud tables be a better approach for data extraction? It is probably built on BIP but is able to extract (replicate) data in bulk.
0 -
BIP has limits as well, but I don't know the tool you referenced. One major limit of BIP reports is a hard 2 million row max limit that Oracle seems to not want to lift.
0 -
Another comment on extract vs. nonextract PVOs. The nonextract PVOs are used throughout Fusion Applications just not OTBI/BICC. They contain a lot of columns that are required outside of "reporting". The extract PVOs are scaled down to only include columns deemed required for reporting purposes.
0 -
Hi,
where can i find 23B BIVO list?
Regards
Nicole
0 -
Please review the below KM Document.
How to Review Database Lineage Mappings, Check For Columns and View Objects for BICC PVOs? (Doc ID 2626555.1)
Thanks,
Praveen
1 -
Hi,
Can someone please guide me to the documentation which shows deprecated, inactive, and new BIVOs as part of 23B.
Thanks,
Sridhar
0 -
Hi,
Can someone help me to get documentation on the deprecated, inactive, and new BIVOs for 23C.
Thanks.
0 -
Thank you Dave Kekish for the link. Thats what I wanted.
Hi - The link shared by Dave Kekish is the one where you can refer to. But as of now, 23C xlsx file is not yet available.
Thanks,
Sridhar
0