Deploy Oracle AI Agent for end users

This aricle details the steps involved in creating a Guided Journey for an AI Agent, assigning it to the properties of a Redwood page using Visual Builder Studio (VBS), and deploying it for end users.

1. Navigate to My Client Groups à Show More à Journeys Setup à Guided Journey

2. Click on Create to start a new Guided Journey

3. Create a Draft by entering the Name and Code for the Journey

4. Add tasks to the Journey

Enter the task name, set the task type to Agent, Agent type to Workflow Agent and select the desired AI Agent to deploy for end users.

5. Activate the Guided Journey

Verify the status of the newly created Guided Journey changes to Active.

 

6. Navigate to Order Management à Order Management (New) (Redwood Page)

7. Navigate to Settings & Actions à Administration à Edit page in Visual Builder Studio

8. Select the appropriate extension project.

9. Assign the newly created Guided Journey code to the “Journey Code” page property.

10. Preview the application in Visual Builder Studio, verify the appearance of the “Ask Oracle” button with the Agent Name and publish the changes.

11. Click “Ask Oracle” to open the AI Agent chatbot panel and inquire about order details by providing an order number.

12. Inquire about the order lines details for the same order number.

Read More »

Create Business Object to create Sales Order via Oracle AI Agent

Navigation: Menu --> Tools --> AI Agent Studio --> Business Object

Click on the Add button to start creating Business Object.

Fill out the following details.

• Family: SCM
• Product: Order Management
• Name: HP Create Sales Order
• Code: Populates automatically
• Resource type: Monolith
• Resource Path: Populates automatically
• Description: Provide an understandable description

Scroll down and click on + plus button to add the business function.

Add the correct resource path "/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub" and set operation type to "POST" in Business Object Function.

Toggle the native authentication header and provide the payload as follows or as required.

{

  "SourceTransactionSystem": "PS",

  "SourceTransactionId": "{p_SourceTransactionId}",

  "SourceTransactionNumber": "{p_SourceTransactionNumber}",

  "TransactionalCurrencyCode": "USD",

  "BusinessUnitId": 300000001921096,

  "BuyingPartyNumber": "{p_BuyingPartyNumber}",

  "TransactionTypeCode": "REGULAR",

  "RequestedShipDate": "{p_RequestedShipDate}",

  "SubmittedFlag": false,

  "FreezePriceFlag": false,

  "FreezeShippingChargeFlag": false, 

  "FreezeTaxFlag": false,

  "RequestingBusinessUnitId": 300000001921096,

  "CustomerPONumber": "{p_CustomerPONumber}",

  "billToCustomer": [

    {

      "CustomerAccountId": {p_CustomerAccountId},

      "SiteUseId": {p_SiteUseId}

    }

  ],

  "shipToCustomer": [

    {

      "PartyId": {p_PartyId},

      "SiteId": {p_SiteId}

    }

  ],

  "lines": {p_Lines}

}

Add a Header with content type set to application/json. The parameters will auto populte based on defined payload inputs.

Add an example payload; This helps AI agent understand and map the fields as required.

All set;  just save your progress, use the business object within the Oracle AI agent and ensure that you map the payload parameters correctly in the prompt.

Read More »

Enable Business Objects for Order EFF tables in Oracle RODS Data Extraction

By default the Extension Flex Field Business Objects are not enabled in the Oracle RODS, New data extraction tool. We need to deploy the flex fields and publish them to enable them.

 Go to Setup and Maintenance

Search for the task Manage Order Extensible Flexfields.

Search for the Flexfield Code DOO_FULFILL_LINES_ADD_INFO and deploy it (Deploy Offline).

Navigate to Tools > Scheduled Processes.

Submit a new process named Publish Extensible Flexfield Attributes.

Ensure that the process completes Successfully.

Review the log and output files to verify there are no errors during the flexfield publishing process.

You should now be able to view the EFF business objects in RODS.

Read More »

How to Connect OIC Integrations to Oracle AI Agent Studio

By leveraging the Model Context Protocol (MCP), you can seamlessly turn your Oracle Integration Cloud (OIC) flows into executable tools inside Oracle AI Agent Studio.

Step 1: Configure the MCP Server & Add Integrations

1. Configure MCP server 

2. Add Integration to Tool in OIC

Step 2: Create the Tool in AI Agent Studio

Open Tools ->  Click Add button

Select the tool type as MCP and provide tool name, family and product.

Step 3: Set Up Connection & Security

Provide the MCP server URL which is obtained from OIC AI Agent tool, select transport type as "Streamable HTTP" and Token URL and client credentials.

{
  "grant_type": "client_credentials",
  "scope": "https://XXXX.integration.ocp.oraclecloud.com",
  "client_id": "DCSDSDSD",
  "client_secret": "SDSDSD"
}

Step 4: Map Integrations & Preview

Select the required integration from the list of added integartions in the OIC tool

You can preview the tool

Pass the tool parameters (OIC integration parameters) and preview.

Read More »

Add OIC Integration to MCP server for Oracle AI Agent Studio

1. Enable MCP server in OIC Projects

View detailed article to enable MCP server here

2. Open OIC Projects, go to AI Agents tab and add tool

3. Add the integration and create tool

4. Add the description and parameteres (OIC Input) and make them as required if any.

Read More »

How to Enable the Model Context Protocol (MCP) Server in OIC and OCI

If you want to expose your Oracle Integration Cloud (OIC) integrations to LLMs and AI agents using the Model Context Protocol (MCP), you need to configure the following things across both OIC and Oracle Cloud Infrastructure (OCI).

 1. Create an Integration in OIC project and activate it

2. Edit the projet settings

3. Enable the MCP server

4. Create OAUTH configuration in OCI for the above MCP server URL

5. With the OAUTH configuration complete, generate the client id and secret. These will be used further to connect MCP server with applications.

Read More »

Extracting Information from Documents Using a Custom Agent in Oracle AI Agent Studio

Oracle AI Agent Studio allows you to create custom AI agents capable of reading unstructured documents and extracting relevant data directly into a structured format.

This article explains how to enable file attachments, configure the necessary tools, and format the extracted data into JSON.

Step 1: Enable the File Upload Option in the Agent Team

Before an agent can process a document, you must provide a way for users to upload files.

1. Navigate to the Chat Experience tab while creating or editing your AI Agent team.
2. Locate the Enable file upload setting.
3. Toggle the option to On. This allows users to attach documents directly within the chat interface.

Step 2: Add the Multi-File Processor Tool

Create a custom agent and follow the steps

1. Go to the agent configuration settings.
2. Add the Oracle standard tool "Multi File Processor" to the agent.
3. This tool processes the uploaded document and makes its textual content accessible to the agent's language model.

Step 3: Define the Agent Persona and Instructions

A well-defined role ensures the agent extracts data accurately and consistently.

1. Configure the agent's Persona and Role to match the business requirements (for example, a "Purchase Order Data Extraction Specialist").
2. Write a clear, concise system prompt detailing what data points need to be collected.
3. Test the agent and refine the instructions if the initial results do not capture all the required information.

Step 4: Configure the JSON Output Schema

To seamlessly integrate the extracted data with downstream applications or databases, the output must be structured.

1. Define a strict JSON schema within the agent configuration.
2. Specify the exact keys, data types (such as strings, numbers, or arrays), and mandatory fields you expect in the final output.
3. This ensures that the agent translates unstructured document text into a clean, predictable JSON object every time.

Sample JSON:

{

  "$schema": "http://json-schema.org/draft-07/schema#",

  "type": "object",

  "properties": {

    "purchase_orders": {

      "type": "array",

      "items": {

        "type": "object",

        "properties": {

          "purchase_order_number": { "type": ["string", "null"] },

          "date": { "type": ["string", "null"], "format": "date" },

          "customer_number": { "type": ["string", "null"] },

          "supplier": {

            "type": ["object", "null"],

            "properties": {

              "name": { "type": ["string", "null"] },

              "address_box": { "type": ["string", "null"] },

              "city": { "type": ["string", "null"] },

              "province": { "type": ["string", "null"] },

              "postal_code": { "type": ["string", "null"] }

            },

            "required": ["name", "address_box", "city", "province", "postal_code"]

          },

          "ship_to": {

            "type": ["object", "null"],

            "properties": {

              "organization_name": { "type": ["string", "null"] },

              "branch_name": { "type": ["string", "null"] },

              "address_line": { "type": ["string", "null"] },

              "city": { "type": ["string", "null"] },

              "postal_code": { "type": ["string", "null"] }

            },

            "required": ["organization_name", "branch_name", "address_line", "city", "postal_code"]

          },

          "line_items": {

            "type": "array",

            "items": {

              "type": "object",

              "properties": {

                "item_code": { "type": ["string", "null"] },

                "quantity": { "type": ["integer", "null"] },

                "price": { "type": ["number", "null"] }

              },

              "required": ["item_code", "quantity", "price"]

            }

          },

          "total_quantity": { "type": ["integer", "null"] },

          "total_price": { "type": ["number", "null"] }

        },

        "required": [

          "purchase_order_number", "date", "customer_number", 

          "supplier", "ship_to", "line_items", "total_quantity", "total_price"

        ]

      }

    }

  }

}

Read More »