Oracle Fusion Applications

Oracle Fusion Cloud Applications have everything you need to optimize your business, make faster and better decisions, and outpace change. Best-of-breed apps for your entire business—in any industry, next-generation cloud infrastructure designed for SaaS applications, all on a standards-based applications platform to easily extend, personalize and integrate applications. DLH.io just happens to be your best chance for getting data from Oracle Fusion Cloud Applications the way you need it into your target destination.

The DLH.io Oracle Fusion BICC connectors were built by an Oracle ACE, so the reliability you are looking for is here now.

Applications Supported

DLH.io currently supports several Oracle Fusion Cloud applications, and the ability to integrate with other applications as well based on request. These include:

• Financials and Supply Chain Management - Oracle Fusion Financials
• Human Capital Management - Oracle Fusion HCM
• Customer Relationship Management - Oracle Fusion CRM

DLH.io supports REST API and Business Intelligence Cloud Connector (BICC) capabilities which makes the DLH platform the optimal data integration platform for synchronizing your data inside or outside of Oracle.

Ask our customer success team about pushing data into your Oracle Fusion application systems in addition to exporting and synchronizing data.

BICC exposes thousands of datastores per connector (3,887 for HCM, 1,717 for CRM, 837 for Financials). Not all are equally useful for analytics and reporting. The default resources below represent the most commonly required tables for standard BI, finance, sales, and HR use cases. Customers can add more datastores after the initial setup. These defaults ensure the most critical data is available from day one without overwhelming the customer with thousands of tables to configure.

How it Works & Syncs

Depending on your decision to use the BICC approach or the REST API approach. DLH provides both. Each process has adds to consumption of the platform and your Oracle Fusion system where applicable. Both BICC and the REST API having their own merited use cases and the instructions differ. Most automated data warehouse and data lake solutions will seek to use the BICC approach.

REST API integration is the easiest to set up but depending on your data needs it can more engaged development to get core answers from joining the data to answer questions for your use case. The benefit is that you get all the data you could possibly need from your Fusion application.

Using the BICC integration approach provides curated Oracle extract data sets that are closer to having modeled relationships, where data engineering work is still required for building analytical reporting but conversely it is an easier lift than using data from the REST API integration.

For BICC Sync Configuration

At a high-level, you need to sign into your Oracle Fusion and BICC configuration UI and select the offerings (ex: HCM) required for the data you need to have extracted. Configure the storage as Oracle Cloud Storage (i.e.: OCI Object Storage). Here's a high-level check list that you'll run through for the initial BICC setup for DLH.io:

• Configure an Oracle Cloud Storage (i.e.: OCI Object Storage) bucket location.
  • This is an optional but supported feature. Otherwise you will use the default UCM concept in fusion
• Extract data based on the required offerings or specific objects.
• Run an initial BICC extract and confirm data is landing in your Oracle Storage bucket
• Connect DLH.io to your Oracle Fusion BICC using the DLH.io Fusion BICC Connector
• Run incremental extracts if you need only the data that changed since your last extract.
• Monitor extracts and review logs on your Fusion account.
• Manage refresh metadata and specify dates for incremental refresh comparison.

Schedule BICC extracts to run at specified intervals.

Using BICC DLH connects to your Oracle Fusion Cloud instance and creates the necessary jobs for extracting data and observing and extracting primary keys that corresponds to changing data within your fusion apps. This is typically only two new jobs created during your Oracle Fusion App BICC setup of the DLH connector:

• Job A - Creates a data extract job, DLH_DATA_EXTRACT_<APP_NAME>
• Job B - Creates a Current PKs job, DLH_CURRENT_PKS_<APP_NAME>

All data lifecycles for incremental loading, etc. are handled by DLH.io.
When the DLH.io Sync Bridge runs, the Sync Brige provides any updates to the jobs as required to filter for the incremental data (the deltas) to increase the speed of synchronization. DLH.io handles the seamless automation from the external object storage through to your target destination.

We understand that many Oracle customers have unique busienss cases with their data and we are here to help. Even though the platform is self service, don't be scared if this is your case, just reach out to our customer success team. One of the easiest ways to do so is to schedule a meeting on our calendar right now, on this link.