Tuesday, November 17, 2026

Oracle Fusion Data Extraction Tool with read-optimized data store (RODS): Storage Destinations - UCM, Oracle Managed Storage and OCI Object Storage

In the previous blog, I explained the details about Oracle Fusion Data Extraction Tool and how it differs from BI Cloud Connector (BICC). We also learned about initial configurations to be performed to enable the Data Extraction tool in your Fusion environment.

Out of the box, Data Extraction tool offers the default storage options such as Universal Content Management (UCM) and Oracle Managed Storage. These two options do not need any explicit configurations and we can use them straight out of the box.

But when it comes to using OCI Object Storage buckets as external storage, it requires a number of configurations to be performed.

In this blog, we are going to understand the step by step process to use the out-of-box storage options like UCM and Oracle Managed Storage, and also to enable customer-managed Storage option, incorporate the Object Storage configurations in OCI and finally connect the Object Storage bucket to the Data Extraction tool.

First, let's take a look at the out-of-box storage options.

Universal Content Management (UCM)


Oracle has mentioned that the support for UCM is provided for compatibility with existing processes, similar to BICC and extract generation using UCM may take longer compared to Oracle Managed Storage. Let's see how to use this storage option.

- Navigate to Tools -> Data Extraction



- Go to Extract Schedules

- Select the desired extract definition to be run

- Under Storage section, select Universal Content Management



- Click Create

- We can monitor the run from Extract Schedules section



- Once completed, navigate to the Extract Jobs tab and note down the Request Id of the job.




- Navigate to the content server of your environment (usually by following your Pod URL followed by /cs)



- Go to Search and search for Title Substring <Job Id copied from above steps>




- Download and open the Manifest (.MF) file


- The Manifest file should list the actual names of the data files generated by our data extract.



- I would normally copy the first number from the file name (usually relates to an internal ESS Job Id). 9835117 in my case.

- Navigate back to the Search and this time search for Title Substring <the copied number> (9835117 in this case).



- With this, you should be able to see the actual data files generated on UCM. You can download, inspect and use them in further processes based on your use-cases.



Oracle Managed Storage


Oracle Managed Storage is the default and recommended option by Oracle. With this, the extract output is written directly to the internal managed storage. Oracle Managed Storage allows you to download the extracted data directly from the application. Let's see how to use this storage option.


- Navigate to Tools -> Data Extraction

- Go to Extract Schedules

- Select the desired extract definition to be run

- Under Storage section, select Oracle Managed Storage




- Click Create

- We can monitor the run from Extract Schedules section



- Once completed, navigate to Extract Jobs section and click on the download icon under Actions




- This will bring up a pop-up showing all the data files generated by our Data Extract



- You can download, inspect and use the data files in further processes based on your use-cases.


OCI Object Storage


In above sections we saw how we can use the out of box storage options like UCM and Oracle Managed Storage. In this section we will focus on how to configure and use the OCI Object Storage as an external storage option in Data Extraction tool.

This is a 3-step process:

- Fusion: Enabling the opt-in feature for customer managed storage

- OCI: Configurations pertaining to the object storage bucket and related policies

- Fusion: Creating a Storage connection to connect to the above bucket

So, let's dive in.

Step 1: Enabling the opt-in feature for customer-managed storage

In order to perform the Storge configurations from within the Data Extraction tool, we first need to activate that feature.

- Navigate to Setup and Maintenance

- Switch to 'Manufacturing and Supply Chain Materials Management'

- Click 'Change Feature Opt In'





- Locate 'Manufacturing and Supply Chain Materials Management' and click the edit icon under Features column.





- Locate the feature 'Redwood: Schedule Data Extracts to Customer Storage Using a Redwood Page
' and enable it.







- Let's verify if we are able to see the "Extract Storage" setting in the Data Extraction tool.

- Navigate to Tools -> Data Extraction

- At this stage, we should be able to see Extract Storage tab. This means we've successfully enabled the this feature. We'll come back to this in Step-3.




Step 2: OCI configurations for the object storage bucket and related policies

Let's switch the gears to OCI. We need do configurations related to the bucket and related policies so that it can be accessed by Fusion Data Extraction tool.

- Login to your OCI console

- Navigate to Storage -> Buckets

- Create the desired bucket you wish to use in Data Extraction tool storage configurations. Data extraction tool will send the data files over to this bucket.

I've created a bucket named data_extraction_bucket


- Make a note of the bucket name.

- Navigate to Compartments and note down the OCID of your compartment in which the bucket resides.




- Navigate to Identity & Security -> Policies



- Create a new policy, give a relevant name and description.

- We need to create two policy statements in below format:

Statement 1:

Allow any-user to {OBJECT_CREATE, OBJECT_DELETE, OBJECT_OVERWRITE} in compartment id
 <compartment_OCID>
where all {
  request.principal.id=/urn_opc_resource_fusion_*/,
  request.principal.id=/*_saas-batch_APPID/,
  target.bucket.name='<bucket_name>',
  target.object.name='/<object_prefix>*/'
}

Statement 2:

Allow any-user to read objectstorage-namespaces in compartment id <compartment_OCID>
where all {
  request.principal.id=/urn_opc_resource_fusion_*/,
  request.principal.id=/*_saas-batch_APPID/
}



Step 3: Creating a Storage connection in Fusion Data Extraction tool

Let's switch back to Fusion.

- Navigate to Tools -> Data Extraction.

- Go to Extract Storage tab

- Click + to create a new storage connection

- Enter Name, Display Name, the actual bucket name and compartment OCID obtained from above steps and lastly a preferred prefix for the data files that will be created on object storage (I'm using test_ as a prefix in my example).



- Click Create. This will validate all the details and complete our object storage connection in the data extraction tool.


Encryption:

Optionally, we can enable the encryption at the source. In order to 

There are two options:

1. Customer Managed Keys:

If we wish to use customer managed keys for encryption, we would be expected to have the Keys stored in OCI Vault. We would use the Vault and Secret details in the Data Extraction tool confiuration.

In addition to this, we need to configure the required IAM policy to allow Object Storage to access the encryption key in OCI:

Allow service objectstorage-<region_name> to use keys in compartment id <compartment_OCID>
where target.key.id = <key_OCID>




2. Oracle Managed Keys:

If we are using Oracle Managed keys, then we need to mention the key in the config.




Now our Object Storage connection is ready for use. 

- Let's navigate to Extract Schedules

- Create a new schedule

- Under Storage options, select OCI Object Storage as Storage, Customer Managed Storage in the second option and select our 'ObjectStorageConnection' for Customer Managed Storage.




- Once we run the Data Extract and it completes, we should be able to see the data file(s) generated in the Object Storage Bucket.


With this, we've covered all the storage configurations available in the Fusion Data Extraction tool. Their usage really depends on requirements of the downstream data integration use-cases.

The Oracle-managed storage or UCM might be sufficient for the customers with a small number of data integrations.

The customer-managed OCI Object Storage might be the right fit for businesses with a larger number of integrations or complex downstream systems.



Share:

Friday, November 6, 2026

Oracle Fusion Data Extraction Tool with read-optimized data store (RODS): Prerequisites and Setup

In my previous blog, I covered the concepts around BI Cloud Connector (BICC) in Oracle Fusion. BICC helps you extract business intelligence and other data in bulk and load it into designated external storage areas such as UCM or OCI Object Storage.

Oracle has recently launched a new tool called Data Extraction tool, which is a targeted to be the long-term replacement for Business Intelligence Cloud Connector (BICC) and offers an efficient, Redwood-based experience.


How does the BICC work?


BICC provides pre-packaged data extracts called offerings. Each offering contains a set of PVOs (Public Virtual Objects) that provide data pertaining to specific business areas.

The offerings are available for business areas such as Financials, Procurement, HCM, Supply Chain, and more.

PVO has attributes which map to a specific database tables and columns optimized for bulk extraction. BICC supports Full as well as Incremental data extracts and supports data export to UCM or OCI Object Storage in CSV format.

BICC extracts the data from the live transactional database of Oracle Fusion Applications.


How does the Data Extraction tool work?


Unlike BICC which extracts the data from live transactional database of Oracle Fusion, the Data Extraction tool extracts data from a read-optimized data store (RODS) to ensure faster and more reliable data extraction.

This approach doesn't put load on the core Fusion applications server as it offloads the data extraction to a read-optimized data store.

This improves the overall performance and efficiency for both transactional activities and data extraction use-cases.


The Data Extraction tool is available under the following business areas and Oracle is working on adding more business areas in the upcoming updates.

- Procurement

- Supply Chain Planning

- Financials

- Manufacturing and Supply Chain Materials Management

- Product Management

- Fusion Accounting Hub

- Order Management

- Workforce Deployment

- Workforce Development


In this blog, I'm going to walk you through all the steps to enable the Data Extraction tool in your Oracle Fusion environment.


1. Enable Security Console External Application Integration


- Navigate to Setup and Maintenance



- Search for 'Manage Administrator Profile Values'


- Search for the profile option code 'ORA_ASE_SAS_INTEGRATION_ENABLED' and set the Site level value to Yes



- Save and Close


2. Create a custom Job Role and Assign to the desired user


- Navigate to Tools -> Security Console

- Let's create a custom role named 'DataExtractionRole'

- Make sure you enable Permission Groups


- Navigate to Role Hierarchy (5) tab



- Add below role memberships:

ESSAdmin: To manage the ESS Jobs pertaining to data extracts

ORA_RCS_SUPPLY_CHAIN_INTEGRATION_SPECIALIST_JOB: To manage the extract definitions and extract schedules

OBIA_EXTRACTTRANSFORMLOAD_RWD: To view and download extract files from Oracle WebCenter Content (UCM)




- Navigate to Users (7) tab

- Assign this custom role to the desired Users

- Save and Close


At this point, we've enabled the External Application Integration and created a custom role with the necessary permissions and assigned to the desired users.


In the final step, to enable the Data Extraction tool, we have to opt-in to the feature that is available under the 'Manufacturing and Supply Chain Materials Management' offering.

Steps to opt-in the Data Extraction tool feature

- Navigate to Setup and Maintenance

- Make sure you have selected 'Manufacturing and Supply Chain Materials Management' offering.



- Click 'Change Feature Opt In'



- Click Edit (pencil icon) under Features



- Find and enable the feature 'Redwood: Extract Application Data from a Read-Optimized Data Store using a Redwood Page'


- Click Done


Accessing the tool


- The Data Extraction tool can be accessed by navigating to Tools -> Data Extraction




- If all the configuration steps are done correctly, the users should see the landing page of the Data Extraction tool where they can create new extract definitions and run the jobs to extract the Fusion data over to various destinations.





And voila! At this point we've completed all the steps to incorporate all the necessary configurations to enable the Data Extraction tool in Oracle Fusion Cloud.


I'll be covering next steps to explain how to use this tool to extract different data sets from various business areas and how do the data extract outputs look like. Stay tuned for my upcoming posts for the same!



Share:

Tuesday, November 3, 2026

Oracle Fusion AI Agent Studio: Monitoring and Evaluation (METRO)

In this blog we will understand process of utilizing the Monitoring and Evaluation (METRO) features of Fusion AI Agent Studio. METRO capabilities help monitor performance of the AI agents. We can also evaluate the accuracy of the agents as well as track the interactions with the agents and identify the errors.

AI Agent Studio - Monitoring


Monitoring helps track the AI Agent's performance and provides insights on how the agents may perform in the production environment. It helps analyze the quality of response time and token counts used by a given AI Agent. Additionally, it also helps understand if there are any errors logged during AI Agent operations.

Monitoring Dashboard Prerequisites

In order to get the monitoring dashboard working for insights on performance, cost and reliability, we first need to run (or schedule) the ESS job 'Aggregate AI Agent Usage and Metrics'.

- Let's go to Tools -> Scheduled Processes



- Search for ESS Job 'Aggregate AI Agent Usage and Metrics' and submit it. This job doesn't have any parameters.


- We can also schedule this process to run on a set schedule (say every 8 hours or so).

- Confirm that the ESS job is successfully completed:


 

Monitoring dashboard

- Navigate back to AI Agent Studio - > Monitoring and Evaluation




- Click on Monitoring tab

 - We should now see all the details on the Monitoring dashboard.

- It shows performance metrics such as Error rate, Error count, Sessions, Latency etc.




 If we open a specific agent from the list, we will be able to see all the sessions as well as agent's error rate, error count, total tokens consumed etc.



- If we navigate to Value tab, it will show us an approximate aggregate value of how many hours (and cost) these AI Agents have saved for us. It will also show the time saved by each individual agent.



- In this case, if we open the "1 Agent Teams" link under Recruiting, we will see our custom agent's name as well as the value metrics for the same.



AI Agent Studio - Evaluation

Evaluation sets are useful in analyzing the performance of our AI Agents. A given evaluation set may have one or more test cases/questions, their expected responses as well as the metrics to be measured. The evaluation sets are specific to each agent. We can create multiple evaluation sets for a given AI Agent.

Let's understand the steps involved in creating the evaluation sets, executing the evaluations and understanding the results.


Creating Evaluation Sets

- Click Manage Evaluations and select Add (+)


- Enter a name/code, description for the evaluation set. Select the agent team we want to evaluate.


- Choose the run mode (Sequential or Random). This may differ based on your use case.


- Sequential: This mode runs the questions in the exact order you define them. It's recommended to use this if one question depends on the context of the previous one.

    - Random: This mode runs the questions in a random order.

- From the Questions tab, add the desired questions that would be most likely asked to the AI the agent. Also, enter the expected answers that the agent should deliver. Make sure that the questions and answers are concise. You can add the questions / answers manually or upload a CSV file with the questions in the column 1 and the expected answers in the column 2.


 

- Navigate to the Metrics tab. Here we can edit each metric to set the pass and fail criteria. For example, to indicate that the test fails if the correctness score is less than 0.5, choose < as the threshold condition and enter 0.5 as the threshold value.



- Click Create to save the evaluation set.


Running Evaluation Sets

Navigate to the Manage Evaluations page, select the Initiate Evaluation Run action for the desired evaluation set.



 - Let's choose the Draft version of the agent team and click Run.


- We should see a confirmation message.



- To monitor the evaluation run, go to View Evaluation Runs action



 - We should see the run in progress.



Analyzing the evaluation run results

- Once the Evaluation Run is completed, we can view the summary results



- To see the detailed results, we can navigate to View Run Results option.


- We can see details on Response performance as well as Correctness of the Agent.

Response performance: This shows the comparison of the expected response versus the actual response from the agent for each question, along with the metrics for each question in the evaluation.

Trace: This provides information about the detailed timeline for each question in the evaluation.



Correctness: This gives us a detailed breakdown of the correctness score. The LLM provides an initial score and feedback.


We can add our own feedback for record keeping in the Correctness Score by Human column.

Comparing Evaluation Runs

We can see the comparison of two different evaluation runs (for the same evaluation set), and understand the regressions or improvements in latency, correctness, and token usage.

- Select any two evaluation runs and click Compare.



- The Summary tab displays a high-level overview of the performance differences between the runs.



- The Details tab provides a granular breakdown of the runs. We can directly compare the actual response from Run 1 against the actual response from Run 2 for each given question.
We can also compare the other metrics such as latency, tokens used, and trace links for each question.
This helps us in understanding changes in the performance as well as accuracy of our AI Agent.




This is how we can utilize the METRO functionality of Oracle Fusion AI Agent Studio to monitor the AI Agent's performance as well as evaluate the agent's response, correctness, and other metrics such as latency, tokens consumed and errors.

This is very useful in making sure that the AI Agent is functioning as expected before we deploy it in the production environment.



Share: