# General setup

The Oracle Fusion Cloud connector is metadata-based. It retrieves input and output schemas for objects you select at design time.

# Object setup

When you choose an action or trigger, the first step is object selection. After selecting an object (such as Invoice or Receivable Credit Memo), the connector fetches all relevant input fields for that object.

Object selection populates the fields in the action Object selection populates the fields in the action

If you don't have access to the selected object resource in Oracle Fusion Cloud (for example, an HCM module object not enabled in your plan), a 403 Forbidden error appears.

Error populating the fields of the specific object Error populating the fields of the specific object

The populated fields include both main object properties and child object properties. For example, Invoices includes main attributes like Invoice number, Business unit, and Invoice amount, plus child objects like Invoice Lines, Invoice installments, and Attachments.

Main attributes under Invoice Main attributes under Invoice

Child objects under Invoice Child objects under Invoice

Each child object accepts a list input, which is useful when passing data from upstream systems. For example, you can pass product line items from Salesforce to the Invoice Lines child object.

Passing list datapill to child object Passing list datapill from Salesforce to the child object Invoice lines

To input child objects manually instead of using a list, change the list to a fixed list and add items individually.

Fixed list setup under child object Fixed list setup under child object

Child objects can contain additional nested objects, accessible using the same method. This allows you to add inputs at any depth for a record.


Last updated: 9/25/2025, 2:46:35 PM