Oracle Fusion Cloud

Add the Oracle Fusion Cloud system using the pod origin and authentication supported by your deployment. The integration form offers Basic, OAuth 2.0 and None.

Two settings are available only through the API, on POST /integrations or PUT /integrations/{id}:

• JWT bearer. Set auth.jwt.token to the bearer token. DataMaker encrypts it at rest, sends it as Authorization: Bearer <token>, and shows it as ******* in every response. Send ******* back on an update to keep the stored token.
• Pod API release. Set apiVersion (for example 11.13.18.05) to pin the release. Data jobs created against the integration record the pinned release.

Discover resources

The service catalogue reads REST describe resources into DataMaker's schema graph. Inspect entity fields, required values, relationships and flexfield segments before generating a template or mapping.

Use a known test resource to verify the connected pod and account permissions. Metadata discovery is not proof that the account can submit a load.

Deliver data

Use a configured REST endpoint for an appropriate request shape, or the supported file-based delivery workflow for FBDI/HDL. File delivery uses a versioned file template, renders and packages data, submits it and tracks the resulting ESS request and result artifact.

Select a template that matches the resource and pod release. Do not assume every Oracle object is covered by a shipped template. Validate a small file and inspect accepted and rejected rows before increasing volume.

Verify on your pod

The integration has fixture-based coverage, but behavior must also be verified against the actual client pod, release and credentials. Review vendor rejection messages, quarantine outputs and key-map entries; submission alone is not success.

After a quarterly update, run a release report against the endpoint before reusing anything built on it: it compares the cached schema with the pod's live metadata without overwriting the cache, and names the templates and scenarios the drift can affect. See Plans, Reconciliation and File-based delivery.