You are on page 1of 8

Introducing

OTBI
Metadata
Independent
Mode
Oracle Business Intelligence Cloud Connector
Release 13.19C

JUNE 20, 2019


PURPOSE
This document provides an overview of BI Cloud Connector’s OTBI Metadata Independent Extract
Mode feature included in Oracle Applications Cloud Release 13.19C. It is intended solely to help you
assess the benefits of using this extract mode when upgrading to 13.19C and to plan your I.T.
integration projects.

DISCLAIMER
This document in any form, software or printed matter, contains proprietary information that is the
exclusive property of Oracle. Your access to and use of this confidential material is subject to the
terms and conditions of your Oracle software license and service agreement, which has been
executed and with which you agree to comply. This document and information contained herein may
not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written
consent of Oracle. This document is not part of your license agreement nor can it be incorporated
into any contractual agreement with Oracle or its subsidiaries or affiliates.

This document is for informational purposes only and is intended solely to assist you in planning for
the implementation and upgrade of the product features described. It is not a commitment to deliver
any material, code, or functionality, and should not be relied upon in making purchasing decisions.
The development, release, and timing of any features or functionality described in this document
remains at the sole discretion of Oracle.

Due to the nature of the product architecture, it may not be possible to safely include all features
described in this document without risking significant destabilization of the code.

2 W HITE PAPER / Introducing OTBI Metadata Independent Mode


EXECUTIVE SUMMARY
The Oracle Business Intelligence Cloud Connector (BICC) is used to bulk extract data from Business Intelligence View Objects (BIVOs),
referred to as Data Stores in the BICC, in Oracle Applications Cloud (Customer Experience, Enterprise Resource Planning, Human Capital
Management, and Supply Chain Management). The data can be extracted to either Universal Content Management (UCM) or Oracle
Storage Cloud. BICC, which is a metadata-driven platform, depends on the existence of BI View Objects (BIVOs) in the OTBI metadata
repository (RPD).

3 W HITE PAPER / Introducing OTBI Metadata Independent Mode


WHAT IS CHANGING?
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.

OPT IN TO USE THE OTBI METADATA INDEPENDENT MODE

New Implementations of BICC in 19C


Uptake the new Manage Job and Job Schedules feature

By default, all Data Stores (BIVOs) are in OTBI Independent Mode (OTBI Metadata dependent option is unchecked).

Note: The mode for all BIVOs in a job can be managed either at the Job or the BIVO level using the Manage Jobs Console in BICC. All
BIVOs default to OTBI Independent Mode when using the Manage Jobs feature. It is recommended to use the Manage Jobs
functionality instead of using the Manage Offering and Data Stores option to manage the extract mode of the BIVOs.

Existing BICC Implementations Updating to 19C


BIVOs delivered prior to 19C retain their configuration as OTBI metadata dependent mode. Before Release 20C, you must switch these
BIVOs to use the OTBI metadata independent mode and test and validate your integration using the new mode.

How do I test BICC extracts in OTBI metadata independent mode in 19C?

Create a job definition using Manage Job and Job Schedules.

Switch BIVOs to use OTBI metadata independent mode. Refer to this list of BIVOs that can be opted in to use the OTBI
metadata independent mode.

Create the Job Schedule

Review the extract files that are created using the new mode. The Manifest, Primary Key, and Extract Status file names will include the
Job ID as well as the ESS Request ID as shown below. This is to ensure the extract files created in the new mode do not overwrite files
created using OTBI dependent mode.

Data extract

MANIFEST_DATA_<JOB_ID>-<ESS_REQUEST_ID>-<TIMESTAMP>.MF

EXTRACT_STATUS_DATA_<JOB_ID>-<ESS_REQUEST_ID>-<TIMESTAMP>.JSON

Primary Key extract

MANIFEST_KEYS_<JOB_ID>-<ESS_REQUEST_ID>-<TIMESTAMP>.MF

EXTRACT_STATUS_KEYS_<JOB_ID>-<ESS_REQUEST_ID>-<TIMESTAMP>

Compare extract results between the two modes.

4 W HITE PAPER / Introducing OTBI Metadata Independent Mode


What changes should I expect in the new mode?

When performing BICC extracts in the new mode, you may notice the following changes in the extracted data:

• Date fields include or exclude the time component.


o Action: Review the time component returned in the date fields to ensure it doesn’t conflict with your downstream
application where date fields are used.
• Certain numeric fields that are defined as Not Null will return zero instead of nulls.
o Action: Update your downstream application to accept zeros instead of nulls for these numeric fields.

How to uptake the OTBI metadata independent mode in 13.19C using Global Extracts?

1. Start the BICC Console

2. Select a Data Store

3. Edit the Data Store

4. Uncheck - Use OTBI metadata dependent extract and click Save.

What are my next steps?

You should switch to the new extract mode if the test results don’t show prohibitive discrepancies. If you encounter any issues using the
new extract mode, please raise a support ticket using My Oracle Support.

5 W HITE PAPER / Introducing OTBI Metadata Independent Mode


CONCLUSION

Future Product Strategy


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.

If you have further questions, please contact Oracle Support.

6 W HITE PAPER / Introducing OTBI Metadata Independent Mode


APPENDIX A: DATA STORES THAT SUPPORT OTBI INDEPENDENT MODE
The following file contains a list of data stores (BI View Objects) that support OTBI independent mode.

Rel13_19C_BICC_BI
VO_OTBI_independe

APPENDIX B: NUMERIC FIELDS DEFINED AS NOT NULL, WHICH WILL RETURN


ZERO INSTEAD OF NULL
The following file contains a list of numeric fields defined as Not Null, which will return zero instead of null in OTBI independent mode.

Rel13_19C_BICC_Nu
meric_Zero_Null.pdf

7 W HITE PAPER / Introducing OTBI Metadata Independent Mode


ORACLE CORPORATION

Worldwide Headquarters
500 Oracle Parkway, Redwood Shores, CA 94065 USA

Worldwide Inquiries
TELE + 1.650.506.7000 + 1.800.ORACLE1
FAX + 1.650.506.7200
oracle.com

CONNECT W ITH US
Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at oracle.com/contact.

blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are
subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed
orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be
reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks
of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0619
White Paper Introducing OTBI Metadata Independent Mode
June 2019

You might also like