Skip to main content
Use the @bijection/connectors/oracle-fusion entrypoint to declare Oracle Fusion Cloud Applications resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
REST resource

​
observed: RowMatch walk by (LastUpdateDate, key); CX Sales deletions from deletedRecords

The following example matches configuration financials.

​
Configuration: financials

Case: oracle-fusion/resource/observed/financials. Connection and resource configuration are declared by this exact case. Credential kind: oracle_fusion. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: hcm

Case: oracle-fusion/resource/observed/hcm. Connection and resource configuration are declared by this exact case. Credential kind: oracle_fusion. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: sales

Case: oracle-fusion/resource/observed/sales. Connection and resource configuration are declared by this exact case. Credential kind: oracle_fusion. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
BI Cloud Connector extract files

​
objectStorage: Each manifest’s files streamed from OCI Object Storage and checked against its MD5

The following example matches configuration standard.

​
Configuration: standard

Case: oracle-fusion/biccExtract/objectStorage/standard. Connection and resource configuration are declared by this exact case. Credential kind: oracle_bicc_object_storage. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: files
File contracts: extractFile.
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

oracleFusion.resource.observed({ api, resource, version?, key, columns, deletedObjectCode?, lag? }) reads one REST resource of Financials, SCM and Procurement (fscmRestApi), HCM (hcmRestApi) or CX Sales (crmRestApi) under the binding’s baseUrl, the pod such as https://acme.fa.us2.oraclecloud.com/. Requests send REST-Framework-Version: 2, whose RowMatch q takes or and parentheses, and walk strictly after the last (LastUpdateDate, key) read: (LastUpdateDate > 'T') or ((LastUpdateDate = 'T') and (InvoiceId > K)), ordered LastUpdateDate:asc,<key>:asc, 499 rows per request, continuing while the answer states hasMore. A finished pass carries the last pair and the next re-reads from lag seconds (default 300) before it. LastUpdateDate is the version. Limits: amounts are JSON numbers, so columns are number, not exact. No command is declared: Oracle documents the ETag and If-Match for singular resources, and a collection answer’s per-row tag is not relied on.

​
CX Sales

CX Sales resources (crmRestApi) are keyed by their numeric ids: PartyId for accounts, contacts, households and resources, OptyId for opportunities, LeadId for leads, ActivityId for activities, and OrderHeaderId for salesOrders (quotes). Their URL item keys (PartyNumber, OptyNumber, the leads hash) are not used. Set deletedObjectCode to turn on deletions: each pass first walks the deletedRecords entries whose ObjectCode is that code, by LastUpdateDate (offset inside one instant, since Oracle lists only ObjectCode and the audit columns as queryable), and publishes each as the deletion of the record whose key KeyAttributeValues names. An entry whose KeyAttributeNames is not the resource’s key attribute is refused. Oracle does not list the object codes: read the code from the tenant’s own deletedRecords before declaring it. Oracle keeps deleted records for seven days, so a source unread for longer misses deletions without any signal; poll well within a week. Other Fusion applications list no deletions, so none is observed there. Bind an oracle_fusion credential: basic, or oauth_client_credentials against the identity domain’s /oauth2/v1/token. No Fusion pod has been reached.

​
BI Cloud Connector extract files

oracleFusion.biccExtract.objectStorage({ maxFileBytes?, startAfter?, every? }) reads the files BI Cloud Connector (BICC) writes to an OCI Object Storage bucket, one record per file. The binding’s bucketUrl is the bucket under the S3-compatible endpoint, path style: https://<namespace>.compat.objectstorage.<region>.oraclecloud.com/<bucket>. Each pass reads one extract: it lists the next MANIFEST-<timestamp>.MF after the carried one (startAfter on the first pass; none listed ends the pass), reads that manifest (first line the source version, then file;md5 lines), and streams every file it names whole into protected storage, at most maxFileBytes (default and ceiling 1 GiB). A file is published only where its bytes hash to the manifest’s MD5. The record holds name, dataStore (the file name’s lowercase spelling of the data store), and the host-written file, size, sha256, md5 and ETag content_version. Files stay compressed CSV; external compute reads their rows. A pass that read every file carries the manifest’s name. Limits: extracts run on BICC’s own schedules (ESS submitRequest is not sent, and BICC’s last extract date is never reset); manifests are never renamed or deleted; job-specific manifests (MANIFEST_DATA_…) and UCM storage are not read; a manifest naming more than 256 files, or a file over the bound, fails its pass; no deletion is inferred from primary-key (.pecsv) files. Bind an oracle_bicc_object_storage credential: a sigv4 envelope holding an OCI Customer Secret Key, region the OCI region identifier (us-ashburn-1), service s3, for a user allowed to list and read the bucket. No bucket has been reached.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.