Coverage gaps and Normal vs Extract PVO

MohanPothuri

In extract type of PVOs, we observe that some columns are missing when scheduling using BICC. To get exact functionality of normal PVO, we need to use Multiple Extract PVOs.

Also document available for Extract PVO but not for normal PVO.

Is it safe to use Normal pvo in solution ?

Are there any coverage gaps with Extract PVOs ?

Eg: Normal PVO - FscmTopModelAM.FinGlLedgerDefnAM.LedgerPVO (no document)

ExtractPVO: FscmTopModelAM.FinExtractAM.GlBiccExtractAM.LedgerExtractPVO - https://docs.oracle.com/en/cloud/saas/financials/23b/oadsr/LedgerExtractPVO.html#LedgerExtractPVO

Nathan CCC

Hi,

I dont think columns are "missing" but the extract PVO do tend to be simpler with less joins to other tables.

You do not need a document if a public view object (PVO) if it is also used in metadata repository database (RPD) in oracle transactional business intelligence (OTBI) as well as BICC.

For example, data lineage extract presentation to logical to physical for subject areas in Financials https://community.oracle.com/customerconnect/discussion/40268/r13-financials-otbi-subject-area-to-database-lineage-mapping-spreadsheet/p1

To understand a PVO in BICC that is also in the RPD

you can just issue sql to query it then view the session log in OTBI.

As a user with a role with privilege "Issue SQl Directly" and "Manage Sessions"

In your browser go to

/analytics/saw.dll?issuerawsql

select_physical all t."LedgerId" as pk, t.* 
from "FscmTopModelAM.FinGlLedgerDefnAM.LedgerPVO" t 
fetch next 7 rows only

then select "View Log" which go to /analytics/saw.dll?managesessions

Sudhakar D

This is great Nathan !!! I experimented on

select_physical * from "FscmTopModelAM.FinFaDeprDepreciationAM.DepreciationDetailPVO" fetch first 7 rows only

It resulted only 16 columns in view log. How to enable more columns? From the data lineage document I can see more columns present in that PVO.

thanks in advance

Sudhakar