Oracle

This page records how composerID publishes into Oracle: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. Oracle Fusion Cloud ERP/Procurement is a financial-commitment system of record for the outsourced work-order channel. composerID raises a Purchase Requisition (or Purchase Order, where policy allows) through the Fusion REST APIs, carries the Intent ID in a Descriptive Flexfield, and reconciles PO lifecycle changes back onto the intent timeline.

Category: ERP. Coverage status: Specification mapped. Vendor documentation: public developer portal.

Integration path

How composerID connects to this destination, at a glance.

Step	Detail
Authentication	OAuth 2.0 via OCI IAM identity domains - create a confidential application (client credentials for server-to-server, or JWT/certificate assertion); the Client ID must also exist as a Fusion user with the right roles.
composerID publishes	Purchase Requisition: POST /fscmRestApi/resources/{v}/purchaseRequisitions (+ submit-for-approval action)
Intent ID lands on	`purchase_requisition` `DFF.intentId`, written into the destination record
Back-sync	Webhooks and polling: some lifecycle events are pushed, the rest are read on a schedule.

Vendor documentation

REST API for Oracle Fusion Cloud Procurement

Purchase Orders REST endpoints

Purchase Requisitions REST endpoints

API posture

Aspect	Detail
Authentication	OAuth 2.0 via OCI IAM identity domains - create a confidential application (client credentials for server-to-server, or JWT/certificate assertion); the Client ID must also exist as a Fusion user with the right roles. Basic auth works but fails once MFA is enforced - treat OAuth as the production path.
Style	REST, JSON (ADF-based resources; newer BOSS v1 endpoints use /api/boss/… paths); offset/limit pagination with hasMore
Base URL	https://{instance}.fa.{datacenter}.oraclecloud.com/fscmRestApi/resources/{version} (e.g. 11.13.18.05)
Webhooks	ERP business events consumed via Oracle Integration (OIC) or polling; no plain public webhook registry on the REST resources themselves.
Events posture	Webhooks and polling
Rate limits	Throttled per identity domain (unofficially ~5,000 calls/hour/user); 429 on breach - keep publishing transactional, use FBDI/bulk paths for volume.
Objects	purchaseRequisitions (header/lines + submit action), purchaseOrders (+ communicateOnePurchaseOrder and other actions), draft POs, suppliers, receipts; Descriptive Flexfields (DFFs) on both PR and PO

Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.

Purchase Requisition

Raise the demand

Mapping	Detail
Canonical to destination	description, service_category, cost_center, budget, dates
Target	POST /fscmRestApi/resources/{v}/purchaseRequisitions (+ submit-for-approval action)
Requirement	Required
Notes	Preparer coupling: the API user must be the requisition preparer (error POR-2010915 otherwise)

Purchase Order

Commit the spend

Mapping	Detail
Canonical to destination	supplier, amount, currency, dates
Target	purchaseOrders REST resource
Requirement	Tenant
Notes	Direct PO create/communicate where program policy allows

Intent ID + back-sync

Correlate and reconcile

Mapping	Detail
Canonical to destination	intent_id (DFF attribute); PO/receipt changes
Target	Descriptive Flexfield + ERP business events via OIC / delta polling
Requirement	Required
Notes	DFFs carry the correlation on both PR and PO

Auth is per identity domain: register the confidential app in OCI IAM and mirror its Client ID as a Fusion user with matching roles - a token alone is not enough. Version strings matter (resources exist in multiple versions; newer BOSS v1 endpoints use a different path shape). DFF segments are tenant-configured, so agree the Intent ID segment name per tenant. The API user must be a valid preparer for requisition creation.

Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.

⌘I

Get started

Concepts

Guides

Destinations

Upstream connectors

API reference

Endpoints

Manuscript API (Triage)

Manuscript endpoints

Resources

Integration path

Vendor documentation

REST API for Oracle Fusion Cloud Procurement

Purchase Orders REST endpoints

Purchase Requisitions REST endpoints

API posture

Publish target and field mapping

Next steps

How composerID connects

Publishing

All destinations

​Integration path

​Vendor documentation

REST API for Oracle Fusion Cloud Procurement

Purchase Orders REST endpoints

Purchase Requisitions REST endpoints

​API posture

​Publish target and field mapping

​Next steps

How composerID connects

Publishing

All destinations

Integration path

Vendor documentation

API posture

Publish target and field mapping

Next steps