OBIA 11g: BICCC extracts to OTBI Metadata Independent mode changes the format of the Manifest Files from <TIMESTAMP>_MANIFEST_DN to MANIFEST_DATA_<JOB_ID>-<ESS_REQUEST_ID>-<TIMESTAMP>.MF
(Doc ID 2691246.1)
Last updated on JULY 24, 2020
Applies to:Business Intelligence Applications Consumer - Version 220.127.116.11.1 to 18.104.22.168.2 [Release 11g]
Information in this document applies to any platform.
Fusion Apps 19c Customers have received this email requiring them to switch BICCC extracts to OTBI Metadata Independent mode prior to upgrading to 20c.
They are getting asked to upgrade to 20c promptly.
IMPORTANT: This information applies to customers using Business Intelligence Cloud Connector (BICC) for bulk data extracts from Oracle Fusion Applications
In Update 19C, Oracle introduced the new OTBI Metadata Independent extract
mode in BICC. With this improved mode, data stores (BI View Objects or
BIVOs) can be extracted independently of metadata, thus making it easier to
extract data from Oracle Fusion Applications. In addition, the new mode
ensures that even if changes are made to BIVOs in the OTBI repository,
current BICC data extracts will not be impacted.
In Update 20C, Oracle will update all BIVOs to the OTBI Metadata Independent
extract mode. Therefore, if you use BICC to extract data from Oracle Fusion
Applications, you MUST transition to the new mode PRIOR to Update 20C.
II. Your Action -- We strongly suggest you begin now to ensure a smooth
Before Update 20C, you MUST configure your BICC extracts to use the new OTBI
Metadata Independent mode. Please perform the following steps:
Create a BICC extract job using the new Independent mode and compare the
data files with files previously created using the Dependent mode
Test your downstream processes using the data files you created in the new
If there are NO issues in the downstream process test with the new data
files, then no further action is required
If there ARE differences, refer to the OTBI Metadata Independent Mode document below for next steps
Review the OTBI Metadata Independent Mode forum post and document on the
Cloud Customer Connect community. Note: you must be a registered community member to access.
Review the Schedule an Extract: Add a Job topic in the BI Cloud Extract book.
The customer is using OBIA 22.214.171.124.1, and they are not able to run Load Plans after the manifest.mf format change.
*** Instead for format: _MANIFEST_DN the format is now MANIFEST_DATA_<JOB_ID>-<ESS_REQUEST_ID>-.MF
How do we handle the code change in ODI to read the new format file?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document