General OBIEE

Get Involved. Join the Conversation.


    Rohan Lobo
    R13.19C Introducing OTBI Metadata Independent Mode Using BI...
    Topic posted June 20, 2019 by Rohan LoboBlue Ribbon: 750+ Points, last edited July 5, 2019, tagged Analyses, Discussion Forums, Fusion, OTBI, Reports, Upgrades 
    167 Views, 3 Comments
    R13.19C Introducing OTBI Metadata Independent Mode Using BI Cloud Connector (BICC)
    Opt in to use the OTBI Metadata Independent Extract Mode in BICC introduced in R13.19C.

    What is the Change?

    Starting in Release 13.19C, BICC will no longer be dependent on the OTBI metadata repository, and the extract mode by default will use the OTBI metadata independent mode. Data Stores (or BIVOs) can be extracted independent of OTBI Metadata (RPD). The new BIVOs introduced in future releases of Oracle Applications Cloud will use OTBI metadata independent mode. The new mode eliminates the dependency on the existence of a BIVO in the OTBI metadata.

    How to Opt In to use the OTBI Metadata Independent Mode for Extraction?

    Refer to the attached document for detailed steps to opt in.

    Future Product Direction

    The OTBI metadata (RPD) dependent mode is going to be deprecated in Release 20C. Oracle Development strongly recommends that you switch your BICC extracts to use OTBI metadata independent mode by 20C. Refer to the attached document for more detailed information.  If you have further questions, contact Oracle Support.



    • Mark daynes


      The title (and content) of the embedded PDF document does't seem to refer to independent it is "View Business Intelligence View Objects that support OTBI dependent mode Release 13 (Update 19C)".  Is there a list of the independent BIVO's?  


    • Senthilrajan Vaithianathan

      Hi Rohan,

      Will this allow us to create a custom PVO's/Data store from SaaS Tables and use it for our BICC data extractions?


    • Senthilrajan Vaithianathan

      Also there is a new feature "UNION ALL for incremental extract".

      Details of this feature is not covered in the documentation, can someone share details of this functionality?