This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Docs Learn Support
Help
Docs Learn Support
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Oracle Cloud ERP RODS Connector: Overview and Setup

singhalok286
Employee
Employee

on ‎10-27-2026 01:59 PM

 

Introduction

Oracle is moving large extract workloads off the Fusion transactional database and away from BICC to RODS, its new Read-Only Data Store. Incorta's RODS connector (Oracle Cloud Applications – Data Extraction) loads Fusion data from RODS with full and incremental loads.

This article explains what RODS is, how the connector works, and how to set it up end to end, from the Oracle Cloud Console to your first load in Incorta.

singhalok286_0-1793014498787.png

 

What you should know before reading this article

We recommend that you be familiar with these topics:

  • Oracle Fusion Cloud Applications and the Oracle Cloud Console
  • Oracle identity domains and OAuth confidential applications
  • Fusion Security Console roles
  • Incorta data sources, schemas and loads

What is RODS?

  • Oracle is moving its largest, most read-intensive workloads off the Fusion transactional database to RODS (Read-Only Data Store)
  • Extracts run against RODS, a read-optimized Autonomous Data Warehouse installed as part of the Spectra technology upgrade
  • Data is replicated from the Fusion Applications database to RODS in near real time using GoldenGate
  • RODS significantly reduces load on the transactional database and middle tier
  • RODS uses business objects as its data model. BOSS (Business Object Spectra Service) is the service layer around them, hiding the complexity of the Fusion physical schema
  • These configurable extracts are intended to eventually replace the Business Intelligence Cloud Connector (BICC)
  • Coverage is still limited: not all modules and objects are available yet, and Oracle is expanding support each release

The solution supports:

  • Selecting one or more business view or extraction views
  • Full and incremental extracts
  • On-demand runs or scheduled extractions
  • Monitoring and viewing extract statuses

This approach is designed as the long-term replacement for Business Intelligence Cloud Connector (BICC), offering a more modern, efficient, Redwood-based experience.

Feature Comparison

Feature BICC RODS
Performance Medium Very High
Schema type Complicated view Clean business object views
Incremental Support Limited Full + optimized
Load on apps database High Near-zero
UI Legacy Redwood

Overall, the tool provide a high-performance, read-optimized extraction experience.

How the connector works

singhalok286_2-1793014648822.png

At a high level, the Incorta RODS connector follow these three steps:

  1. Trigger extraction: Incorta's RODS connector starts an extract job in Fusion
  2. Write data: RODS writes the extract output to Oracle Object Storage
  3. Extract data: Incorta downloads the files, transforms them and loads them into Incorta

What the connector gives you:

  • Table discovery from the RODS APIs
  • End-to-end pipeline orchestration: run extract jobs, pull output from object storage, transform and load in Incorta
  • Full and incremental loads
  • Easy handling of business object changes
  • Support for Oracle Object Storage

Applies to

  • Incorta with the Oracle Cloud Applications – Data Extraction (RODS) connector from the connector marketplace
  • Oracle Fusion Cloud Applications, release 26A and later, with the Data Extraction Tool enabled

Let's Go

Here is everything that you need to set up the Oracle Cloud (Fusion) and Incorta to use the RODS connector. 

Before you start

Who should follow this guide: your Oracle Cloud administrator, ideally with your Oracle Fusion security administrator

What Incorta can do with this access: list the views available for extraction, define and run extract jobs, and download their output files. It does not change your business data.

Check these four things first or the connection test cannot pass:

  • The Data Extraction Tool is turned on in Oracle Fusion. It's opt-in, available from release 26A, and your Fusion administrator turns it on in Setup and Maintenance
  • Oracle has enabled the services the tool needs. Oracle Support confirms this for your environment
  • You can sign in to the Oracle Cloud Console as an administrator of the identity domain linked to your Fusion environment
  • You can sign in to Oracle Fusion with access to the Security Console and Setup and Maintenance

Step 1: Find Your Oracle Fusion Details

  1. Sign in to the Oracle Cloud Console. Go to My Applications > Fusion Applications > Environments and select your environment
  2. Oracle Cloud Applications URL: copy the Application URL, e.g. https://fa-abcd-test-saasfaprod1.fa.ocs.oraclecloud.com
  3. Oracle Cloud Instance Name: take the part between fa- and -saasfaprod1. In the example it is abcd-test
  4. Oracle Cloud Identity Service URL: open the associated identity domain. On the Domain information tab, copy the Domain URL, e.g. https://idcs-1a2b3c4d5e.identity.oraclecloud.com

To double-check the instance name, go to Oracle Cloud Services > Oracle BOSS Cloud (Spectra) in the identity domain. Its Primary audience reads urn:opc:resource:fusion:<instance name>:boss.

Step 2: Create the Integration Application

The integration application is the account Incorta signs in with. It signs in on its own, with no person involved, so it never needs a password reset.

  1. Go to Identity & Security > Domains and open the identity domain from Step 1
  2. Go to Integrated applications > Add application
  3. Choose Confidential Application and select Launch workflow
  4. Enter a name, e.g. Incorta Fusion Data Extraction, and select Submit
  5. Open OAuth configuration > Edit OAuth configuration
  6. Select Configure this application as a client now
  7. Under Authorization, tick Client credentials only
  8. Keep this page open for Step 3

After Step 3, activate the application with Actions > Activate. Then copy the Client ID and Client Secret from the OAuth configuration tab and keep the secret safe.

Step 3: Add Three Fusion Service Scopes

Each service needs its own scope. Missing any one makes the connection test fail at that service. Replace <instance name> with yours.

Service

Scope to Add

Found Under

Used For
Data Extraction definitions urn:opc:resource:fusion:<instance name>:boss/ Oracle BOSS Cloud (Spectra) Create and update extract definitions
Data Extraction catalog urn:opc:resource:fusion:<instance name>:scm-core/ Search spectra-scm-core List pillars, functional groups and views
Batch Jobs and Files urn:opc:resource:fusion:<instance name>:saas-batch/ Oracle SaaS Batch Cloud Service Run extract jobs, track progress, download files
  1. Under Token issuance policy, set Authorized resources to Specific
  2. Turn on Add resources and select Add scope
  3. Search for the resource, tick it, and select Add
  4. For the catalog scope, pick the one ending in :scm-core/, not a longer one ending in a path
  5. Repeat for the other two scopes, then select Submit
  6. Check that all three scopes appear, each ending with /

Step 4: Grant permission in Oracle Fusion

Scopes let the application reach the services. Fusion roles decide what it may do there. Your Fusion security administrator does this step.

  1. Turn on the authorization service. Go to Setup and Maintenance > Manage Administrator Profile Values and set ORA_ASE_SAS_INTEGRATION_ENABLED to Yes at Site level.
  2. Create a job role for data extraction. Go to Security Console > Roles > Create Role and tick Enable Permission Group. Under Role Hierarchy, add these two roles and save:
    • ORA_RCS_SUPPLY_CHAIN_INTEGRATION_SPECIALIST_JOB (manage extract definitions and schedules)
    • ESS Administrator Role (run extract jobs)
  3. Assign the role to the integration application. Set up the Client ID as a user in the Security Console and assign it the role. You can also add the role under Security Console > Application Extensions > Custom OAuth Client Applications > (your application) > Roles.

Without this role, the connection test signs in but stops, saying the application is not allowed to use a service.

Step 5: Install, configure and test in Incorta

  1. Install the Oracle Cloud Applications – Data Extraction connector from the Incorta connector marketplace
  2. Create a data source of that type and fill in these fields:

Field in Incorta

What to Enter

Example
Oracle Cloud Applications URL Fusion sign-in address (Step 1) https://fa-abcd-test-saasfaprod1.fa.ocs.oraclecloud.com
Oracle Cloud Instance Name Fusion instance name (Step 1) abcd-test
Oracle Cloud Identity Service URL Identity domain address (Step 1) https://idcs-1a2b3c4d5e.identity.oraclecloud.com
Client ID From the application (Step 2) 3f9c…e21
Client Secret From the same application (Step 2) (hidden)
Primary Key Extract Leave off. Turn it on only for a second data source that detects records deleted in Fusion. Off

Then select Test Connection. Incorta checks each of the three Fusion services in turn. A pass means setup is complete.

singhalok286_3-1793014715888.png

Step 6: Create a schema and load data

  1. Create a schema in Incorta.
  2. Use the schema wizard to add a table from the RODS data source.
  3. Run a Full load, then an Incremental load to confirm both work.

Troubleshooting

The test checks Data Extraction definitions, then the catalog, then Batch Jobs and Files, and stops at the first problem. Fix it and test again.

The message starts with

What it means

How to fix it
Oracle Cloud did not accept the Client ID or Client Secret Wrong values, or the application is not active Copy both values again and check the application shows Active (Step 2)
The integration application is not allowed to sign in on its own Client credentials is not ticked Tick it under Authorization (Step 2)
Oracle Cloud did not give access to the … service Scope missing, or wrong instance name Add the scope named in the message (Step 3) and check the instance name (Step 1)
Could not use the … service. Oracle Fusion did not accept the sign-in Fusion does not recognize the sign-in Check the instance name matches the Fusion URL and the application is in this environment's identity domain (Step 1)
Could not use the … service. The integration application signed in but is not allowed No Fusion role for that service Complete Step 4 and check the Data Extraction Tool is turned on
Could not reach Oracle Cloud while checking the … service Incorta could not reach the Fusion or identity address Check both URLs and that your network allows Incorta to reach them
Could not use the … service, followed by a reason and an HTTP code Any other Fusion error Send the full message to Incorta Support

Related Material

Best Practices Index
Best Practices

Just here to browse knowledge? This might help!

Contributors
Version history
Last update:
‎10-27-2026 01:59 PM
Updated by:
Employee
Copyright © 2026 Khoros, LLC