How to delete Extract Schedules in Oracle RODS using REST APIs

This article explains how to delete the extract schedules in Oracle RODS using REST APIs.

Deleting simple or immediate extract schedules manually—one by one—in the Oracle RODS UI can be tedious and time-consuming. Instead, you can automate this process by retrieving the extract schedule IDs and deleting them via REST APIs.

1. Retrieve the Extract Schedule ID

Fetch the list of extract schedules to find the specific schedule ID you want to delete.

(Refer to article on how to fetch extract schedules using REST APIs for full details.)

2. Locate the $id Field

From the JSON response payload of the extract schedule, locate and copy the $id attribute value (for example: 300005596387893).

3. Send the REST DELETE Request

Perform a DELETE HTTP request, passing the schedule's $id at the end of the API endpoint URL and use OAUTH2.0 with BOSS scope.

• HTTP Method: DELETE
• Endpoint URL: https://<your-instance>.oraclecloud.com/api/boss/data/objects/ora/scmCore/dataExtract/v1/extractSchedules/300005596387893

Verification

A successful request will return an HTTP 204 No Content status code, confirming that the extract schedule has been permanently removed.

Before delete:

After delete:

Read More »

Dynamically update REST Adapater Invoke connections in OIC

This article explains how to dynamically select and switch REST Adapter connections at runtime in Oracle Integration Cloud (OIC).

1. Create REST Connections

Create two separate REST connections in your OIC instance, each configured with a different Fusion instance URL.

Use this article to create connections.

2. Configure the Trigger Interface

Create a new integration and add an input query parameter to the trigger endpoint so the caller can specify which target environment to use.

3. Define a Connection Identifier Variable

Create an integration variable to store the target connection identifier dynamically.

4. Assign Connection Identifier via Switch Case

Use a Switch activity to evaluate the input query parameter and assign the appropriate connection identifier to your variable (e.g., HP_REST_TEST_1 or HP_REST_TEST_2).

5. Configure the REST Adapter Endpoint

Add the REST Adapter Invoke connection and configure it to fetch sales orders using the following relative resource path:

/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub

 6. Enable Dynamic Connection

In the REST endpoint configuration, check the Enable Dynamic Connection option and map your connection identifier variable to it.

7. Define Query Parameters

Configure endpoint query parameters such as limit and onlyData.

8. Map Parameters

In the mapper, map limit to 10 and onlyData to true.

Testing the Integration

Test the integration by passing different instance values as the input query parameter:

Test Case 1: Pass the parameter for TEST1. Observe that OIC dynamically routes the call using the HP_REST_TEST_1 REST connection.

Test Case 2: Pass the parameter for TEST2. Observe that OIC dynamically routes the call using the HP_REST_TEST_2 REST connection.

Read More »

How to create REST Adapter connection in OIC

This article explains how to create a REST connection in Oracle Integration Cloud (OIC) step-by-step.

1. Navigate to Connections:

Go to Design --> Connections from the left navigation menu.

2. Select the REST Adapter

Search for and select the REST adapter from the list.

3. Configure Connection Details

• Name & Identifier: Enter a clear name and a unique identifier for your connection.
• Role: Set the role to Trigger and Invoke.

4. Set Up Connection Properties & Credentials

• Select REST API Base URL as the connection type.
• Enter your Oracle Fusion SaaS URL.
• Provide your basic authentication credentials (username and password).

5. Test the Connection

Click the Test button to verify that the connection works properly.

Read More »

How to enable Offering in Oracle Fusion Apps

This article details the steps involved in enabling the offering: Data Extraction tool with in Oracle Fusion Apps.

1. Navigate to Setup and Maintenance

Open the Profile Menu (Settings and Actions) in the top right corner and select Setup and Maintenance.

2. Select the Setup category

From the Setup dropdown menu, choose the relevant offering category (for example, Manufacturing and

Supply Chain Materials Management).

3. Open “Opt In” options

Click the Change Feature Opt In link located near the top of the Functional Areas pane

4. Access Area Features 

On the Opt-In page, locate the appropriate Functional Area row and click the Edit Features icon (pencil icon) under the Features column.

5. Enable RODS – Read Only Data Store feature 

Find the feature named "Redwood: Extract Application Data from a Read-Optimized Data Store using a Redwood Page" and check the Enable box. Click Done.

6. Verify Tool Availability

Open the main navigation menu and expand Tools. The Data Extraction tool will now be visible and accessible.

Read More »

How to Fetch Data Extract Schedules in Oracle RODS Using REST APIs

While you can easily view extract schedules using the RODS Data Extraction UI, you may sometimes need to fetch them programmatically via REST APIs. This is useful for automating tasks, such as cleaning up completed or old schedules.

Data Extraction Schedules UI:

RODS REST API Endpoint:

GET https://fa-test.fa.ocs.oraclecloud.com/api/boss/data/objects/ora/scmCore/dataExtract/v1/extractSchedules?$filter=frequency%20=%20%27Immediate%27&$limit=25&$offset=0&$sortBy=scheduleId%3AAsc&$fields=extractType,name,scheduleId,status,frequency,extractDefinition.name,extractDefinition.overrideProperties

Query parameters:

$filter : Filters results based on criteria like schedule name or frequency (e.g., frequency = 'Immediate')

$limit : Sets the maximum number of records returned in a single response (e.g., 25)

$offset : Defines the starting index for pagination.

$sortBy : Sorts the output by a specific field (e.g., scheduleId:Asc).

$fields : Specifies which attributes to include in the response payload.

Response:

{

    "items": [

        {

            "extractType": "Incremental",

            "name": "TEST_HP_JOB_11052026_01",

            "scheduleId": "9976262",

            "status": null,

            "frequency": "Immediate",

            "$id": "300005596387893",

            "$context": {

                "links": {

                    "$self": {

                        "href": "https://fatest-test.fa.ocs.oraclecloud.com/api/boss/data/objects/ora/scmCore/dataExtract/v1/extractSchedules/300005596387893"

                    }

                }

            },

            "extractDefinition": {

                "name": "TEST_EXTRACT_SAMPLE_SO_HDRS",

                "overrideProperties": "{\"outputDataFormat\":\"CSV\",\"historyStartDate\":\"2026-04-01T00:00:00+00:00\",\"type\":\"BV\",\"csvDelimiter\":\",\"}",

                "$id": "300005596387887",

                "$context": {

                    "links": {

                        "$self": {

                            "href": "https://fatest-test.fa.ocs.oraclecloud.com/api/boss/data/objects/ora/commonBoss/dataExport/v1/exportGroupDefinitions/300005596387887"

                        }

                    }

                }

            }

        }

    ],

    "hasMore": true

}

The API response includes a boolean field called hasMore: 

• If hasMore is true, there are additional records to fetch. 
• You can write a loop that increments the $offset parameter by the $limit value (e.g., offset 0, then 25, then 50) to fetch all available schedule records sequentially.

Read More »

Extension Flex Fields - RODS data extract failure

This article explains how to fix data extraction errors for Fulfill Lines Extension Flex Fields (EFF) in Oracle.

Typically, EFF extraction errors happen because the relevant business view or flex field hasn't been deployed yet.

Step 1: Identifying the Issue

You observe that the RODS data extract job has failed.

Check the corresponding ESS job request and confirm it failed as well.

Open the child request output file to inspect the failure. You will see a status of "failed" along with an error message similar to this:

Error processing extract: "DOO_FULFILL_LINES_EFF_B_BackorderExtract_1783432279245. advancedQueryExtraction: An error occurred while processing request.. Details: Request refers to a BOSS artifact that doesn't exist. Name: oraScmCoreOrderMgmtOrders.ora_..., Type: Business Object.oracle.boss.batch.BatchException: advancedQueryExtraction: An error occurred while processing request.",

Step 2: Checking the Extract Definition

Go to the extract definition and edit it.

Try to select attributes with in any of the object contexts.

You may see a "failed to load attributes" error in the object attributes selection.

Step 3: Resolving the Issue

This issue usually occurs because the flex fields are not deployed for RODS data extraction.

To resolve it, enable and deploy the Extension Flex Fields business views for RODS data extraction. Follow the detailed steps in this guide:

After deploying the flex fields, you should be able to view and select the EFF business views in your data extracts.

Read More »

Deploy Pre-built OCI Function & Configure Event Rule

This article details the process for deploying a pre-built OCI Function and configuring an OCI Event Rule to trigger it automatically.

1. Log In to Oracle Cloud 

Go to cloud.oracle.com, enter your Cloud Account Name, and click Next. Then, enter your username and password to log in.

2. Navigate to Pre-Built Functions

Open the main navigation menu, go to Developer Services, locate Functions, and click Pre-Built Functions.

3. Select the Function Template

Find and select the Object Storage File Extractor pre-built function card, then click Create function.

4. Configure Function Details

Enter a unique Name for your function, select the appropriate Application compartment and Application, and then click Create.

5. Review Dynamic Group and IAM Policies 

If automatic IAM policy creation is enabled, OCI will automatically create the required dynamic group and assign the policies (provided you have sufficient permissions). If you lack administrative rights, work with your administrator to set up the dynamic group and assign policies manually.

6. Verify Function Creation

Navigate to your selected Application to verify that the function appears in the list and shows an Active status.

7. Navigate to OCI Events Service

Open the main menu, navigate to Observability & Management, and select Rules under the Events Service section.

8. Define Rule Conditions

Click Create rule. Enter a Display name and Description. Under Rule conditions, set the following parameters: 

• Condition: Event type | Service name: Object Storage | Event type: Object - Create

• Condition: Attribute | Attribute name: resourceName | Attribute value: *.zip

• Condition: Attribute | Attribute name: bucketName | Attribute value:  STAGE_RODS

9. Set Action and Create Rule

In the Actions section, select Functions as the Action type. Choose the target Function compartment, Function application, and Function. Click Create rule. Once configured, the function will execute automatically whenever a new ZIP file is uploaded to the specified bucket.

Read More »