Oracle Fusion Cloud Applicationslink
Updated October 4, 2023
Oracle Fusion Cloud Applications is a suite of SaaS applications for business functions.
Fivetran supports the following Oracle Fusion Cloud applications:
- Customer Experience - Oracle Fusion Cloud Applications - CRM connector
- Enterprise Resource Planning - Oracle Fusion Cloud Applications - FSCM (ERP & SCM) connector
- Supply Chain Management - Oracle Fusion Cloud Applications - FSCM (ERP & SCM) connector
- Human Capital Management - Oracle Fusion Cloud Applications - HCM connector
Fivetran uses Business Intelligence Cloud Connector (BICC) to sync data from Oracle Fusion Cloud applications to your destination.
Once we connect to your Oracle instance, we create the following BICC extract jobs for each object:
- Data job to extract data.
- Active PK job to extract active primary keys.
We use the query filters of these jobs to fetch incremental data from your Oracle Fusion Cloud applications. The connectors manage the life cycle of these jobs.
During syncs, the connectors create submit schedules for the BICC jobs. We extract the data files from Oracle UCM and sync the data to your destination.
We use the BICC Extract Active Primary Key job to fetch the list of active records. We mark the non-active records as deleted.
If an object doesn't have incremental filter then Oracle treats that object as a re-import object. Fivetran in that case extracts all the rows even in incremental syncs, which increases MAR. Refer our Oracle Fusion Cloud setup guides to enable incremental extract for custom objects.
The length of the query filters in BICC jobs is limited to 4000 characters. If the length exceeds 4000 characters, we treat the incremental objects as re-import objects.
Syncing custom objectslink
We support syncing custom objects. You must add the custom object to an offering and select the primary keys in the custom objects. For more information, see our Oracle Fusion Cloud setup guides.
The connectors sync the View Objects as they are available in the Oracle Fusion databases.
View Objects are referred to as datastores in the source.
We split the datastores when naming tables and schemas. We name tables after the last component. We name the schema after the product (if present) and the pillar (removing the
AM suffix if it is present.)
NOTE: We remove the
AMsuffix if is present in the product or pillar name. We don't remove any suffix from the product or pillar name if it ends with any suffix other than
Some datastores have three parts - Application.Pillar.Table while some have four parts - Application.Product.Pillar.Table
For three parts datastore the schema name would be the Pillar name (removing the
AM suffix if present) and the last component (i.e. table) would be the Table name.
Schema Name in Source: FinArTopPublicModel
Table name: TransactionLinePVO
For four parts datastore the schema name would be the Product_Pillar (removing the AM suffix if present) and the last component (i.e. table) would be the Table name.
Schema Name in Source: FinExtract_XlaBiccExtract
Table name: SubledgerJournalDistributionExtractPVO
In destination, the schema name would be
destinationSchemaPrefix_schemaNameInSource. destinationSchemaPrefix is nothing but the schema name set by the User in the setup form.
NOTE: Oracle Fusion Cloud Apps Connectors use Standard Renaming Rules for schema and table names in the destination.
Fivetran only supports Universal Content Management (UCM) for storing the BICC extract job files.
Fivetran creates and manages the BICC extract jobs. Do not manually edit the Fivetran jobs or create schedules.
Fivetran only syncs the default columns for all the data stores. In the data store, the default columns have the Select List checkbox checked. To sync a non-default column, check the Select List checkbox. You can customize the data store in the Oracle BICC Console.
NOTE: In the BICC Console, you must customize the data store itself and not the jobs associated with the data store.
Fivetran marks source tables as Excluded By System in the connector dashboard:
- If the data store is inactive.
- If the data store is not part of an offering.
- If the data store does not contain a primary key.
- If the data store contains more than 1000 default columns (Oracle doesn't support retrieving more than 1000 columns for a data store).
- If the submitted job schedule fails for a datastore in Oracle.
The connectors perform an automatic re-import:
- If the Active PK job or its schedule is deleted, we perform a re-import to fix data integrity issues.
- We need access to the active primary keys file to capture deletes. By default, the files are removed from UCM in 90 days. If the previous files are removed, we perform a re-import to capture the deletes.
- If the Active PK job schedule fails in Oracle.
View object to database lineage mappinglink
|Data Source||Oracle Lineage Mapping Spreadsheet|
|Customer Experience (CX)||Mapping Spreadsheet|
|Enterprise Resource Planning (ERP)||Mapping Spreadsheet|
|Supply Chain Management (SCM)||Mapping Spreadsheet|
|Human Capital Management (HCM)||Mapping Spreadsheet|
NOTE: Oracle ERP and SCM share the same lineage mapping spreadsheet because Oracle treats both the applications as the Financials and Supply Chain Management (FSCM) application.
TIP: You can download the consolidated database lineage mapping spreadsheet for the Financials and Supply Chain Management (FSCM) and Customer Experience applications.
Syncing empty tables and columnslink
Fivetran can sync empty tables for your Oracle Fusion Cloud Applications. Fivetran can sync empty columns only if the column data types are known. For Oracle Fusion Cloud Applications connector, Fivetran infers the column data types other than VARCHAR, DATE, TIMESTAMP, and NUMERIC, as unknown.
Unsupported data typeslink
The connectors don't support the BLOB and CLOB data types.