SYS-06: Integration & Web Service Monitor (Oracle Fusion)

Oracle Fusion Cloud integration failures occur at three distinct layers — the Oracle Integration Cloud (OIC) layer where orchestration flows run, the Fusion inbound FBDI/REST layer where data enters Fusion, and the Fusion outbound REST/BICC layer where data leaves Fusion to downstream systems. Each layer has different diagnostic tools and different failure patterns. SYS-06 provides a structured diagnostic across all three layers using the OIC Monitoring console, Fusion ESS import job history, REST API response analysis, and OTBI integration subject areas.

Oracle Integration Cloud (OIC) orchestration failures are diagnosed through the OIC Monitoring console. Every OIC integration instance — a single execution of an integration flow — is recorded with its status (Succeeded, Failed, Aborted) and the full message payload at each step. When an integration fails, the OIC console shows exactly which step failed, the error message from that step, and the payload that was being processed at the point of failure. The most common OIC failures are authentication errors (OAuth token expired), payload validation errors (required field missing or wrong data type), and target connection timeouts.

Fusion inbound integration failures — data coming into Fusion via FBDI or REST API — are diagnosed through the ESS import job history and the REST API response codes. A 400-series REST response indicates a payload error (the data being sent is malformed or fails validation). A 500-series response indicates a Fusion server error (infrastructure issue requiring Oracle Support). FBDI import failures are diagnosed through the ESS Load Interface File and the module-specific import job output log, which provides row-level rejection detail.

SYS-06 provides a structured integration health diagnostic using OIC Monitoring for orchestration flow status, REST API response code analysis for inbound and outbound integration health, ESS import job history for FBDI integration status, BICC (Business Intelligence Cloud Connector) extract status for outbound data feeds, and OTBI integration subject areas for population-level failure analysis.

OIC Instance Health

OIC Monitoring console — instance count, success/failure breakdown, and failure pattern by integration and time window. Identifies whether failures are isolated or systemic across multiple integrations.

Connection & Auth Status

OIC connection health for all active integrations — OAuth token status, last test date, and expiry. REST API endpoint connectivity test. Identifies authentication failures before they cause instance failures.

FBDI Import Health

ESS import job history for all FBDI-based integrations in the diagnostic window. Output log error categorization. Resubmission readiness check — confirms the FBDI file has been corrected before resubmission.

BICC Outbound Status

BICC extract console — extract job completion status, last successful run, and data volume per extract. Identifies gaps in outbound data feeds to downstream analytics and reporting systems.

════════════════════════════════════════════════════════════
  ORACLE FUSION — INTEGRATION MONITOR DIAGNOSTIC
════════════════════════════════════════════════════════════
  Integration Name   : ERP-to-Salesforce Opportunity Sync
  OIC Instance       : OIC-PROD-2026-02
  Failure Window     : 24-FEB-2026 18:00 to 25-FEB-2026 08:00
  Case Number        : FC-SYS-2026-0618
  Report Date        : 25-FEB-2026 09:10:22
════════════════════════════════════════════════════════════

[ STEP 1 — OIC MONITORING CONSOLE ]        STATUS: ✗ FAILURES
────────────────────────────────────────────────────────────
  Instance Count     : 48 instances in window
  Succeeded          : 41 ✓
  Failed             : 7 ✗
  First Failure      : 24-FEB-2026 18:42:11
  Step Failed        : Invoke Salesforce REST — AUTHENTICATION_FAILURE
  ✗ FAIL: OAuth token expired — Salesforce connection credential needs refresh

[ STEP 2 — CONNECTION HEALTH ]             STATUS: ✗ AUTH ERROR
────────────────────────────────────────────────────────────
  Salesforce REST Conn: OIC Connection: salesforce-prod-conn — expired ✗
  Fusion REST Conn   : fusion-erp-conn — active ✓

[ STEP 3 — FBDI INTEGRATION ]              STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  All FBDI import jobs completed successfully in window ✓

[ STEP 4 — BICC EXTRACT ]                  STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  BICC extract jobs completed — outbound data feeds healthy ✓

════════════════════════════════════════════════════════════
  FUSION DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  7 OIC failures — Salesforce OAuth token expired
  FIX: Refresh Salesforce connection credentials in OIC console
════════════════════════════════════════════════════════════

Diagnostic Steps

Integration health diagnostic using OIC Monitoring console for orchestration flow instance status and error detail, REST API response code analysis for inbound and outbound health, ESS import job history for FBDI integration status, BICC extract console for outbound data feed health, and OTBI integration subject areas for population-level failure analysis.

Backup Created

All diagnostic data is read-only. Failed OIC instance payloads and connection state are exported before any credential refresh or resubmission. Provides the before-state record for the KB article and audit trail.

Guided Data Fix

OIC credential refresh via the OIC console Connections screen. Failed instance resubmission via OIC Monitoring > Resubmit. FBDI correction and reimport via ESS. All actions through supported OIC and Fusion interfaces — no direct database or file system access.

KB Article Generated

Complete KB article from OIC console output — integration name, failure window, failed instance count, error type, connection corrected, instances resubmitted.

Pre-Action Documentation — SYS-06

OIC Monitoring — failed instance list and payloads exported

OIC Connection detail — credential status before refresh

ESS Import job history — FBDI status for the window

Exported before any UI action, ESS resubmission, or FBDI reimport. Provides a point-in-time record of the error state for the KB article and SR documentation if needed.

Pre-Action Verification

OIC Monitoring console accessibleConfirmed ✓

Failed instance list exportedSaved ✓

OIC connection status reviewedDocumented ✓

Fusion REST API connectivity confirmedTested ✓

No active OIC integration runs during credential refreshConfirmed ✓

Audit Trail Record

CASE_NUMBER<consultant case#>

DIAGNOSTIC_TOOL<OTBI / REST API / BIP / ESS>

ERROR_SNAPSHOT<exported before action>

ACTION_TAKEN<UI path / ESS program / FBDI>

RESULT_VERIFIEDYES ✓

No Direct DB Access — By Design

Oracle Fusion Cloud is a SaaS environment. There is no consultant-accessible Oracle schema, no SQL*Plus connection, and no CONS_BACKUP tablespace. All diagnostic and corrective activity goes through OTBI, REST APIs, BIP reports, ESS programs, and the Fusion UI — the same supported tools Oracle Support uses.

REST API Reference — Endpoints Used in This Diagnostic

All API calls use OAuth 2.0 authentication. The base URL is your Fusion Cloud instance URL. Replace {instanceName} with your tenant name. Obtain the OAuth token via the /oauth/token endpoint using client credentials.

GETOIC Integration Instances (Monitoring)

https://{oic-instance}.integration.ocp.oraclecloud.com/ic/api/integration/v1/monitoring/instances

Key Query Parameters

integrationInstance integration code — e.g. ERP_TO_SF_SYNC|01.00.0000 to filter to a specific integration

status FAILED — to retrieve only failed instances

dateRange start={ISO_datetime}&end={ISO_datetime} — time window for the query

limit integer — default 100

Response Fields Read

id — OIC instance ID for resubmission

status — COMPLETED, FAILED, ABORTED

activityStreamEnabled — whether detailed step trace is available

createdTime, completedTime — instance timing

integrationVersion — confirms which integration version processed the instance

NOTE: OIC REST API uses Basic Auth or OAuth. Base URL is your OIC instance URL — different from the Fusion Cloud URL. Confirm with your integration administrator.

GETOIC Integration Instance Activity (Error Detail)

https://{oic-instance}.integration.ocp.oraclecloud.com/ic/api/integration/v1/monitoring/instances/{instanceId}/activityStream

Path Parameters

instanceId string — OIC instance ID from the instances collection GET

Response Fields Read

activityStreamData — array of steps with status per step

stepName — the integration step that failed, e.g. InvokeSalesforce

error.errorCode — machine-readable error code, e.g. AUTHENTICATION_FAILURE

error.errorMessage — human-readable description of the failure

requestPayload — the payload sent to the step (useful for debugging 400 errors)

KB-FC-SYS-0618-001 · Script: SYS-06

OIC ERP-to-Salesforce Sync — 7 Failures: OAuth Token Expired on Salesforce Connection

Module: System
Platform: Oracle Fusion Cloud
Status: RESOLVED

Symptom

7 of 48 OIC instances for ERP-to-Salesforce Opportunity Sync failed between 24-FEB 18:00 and 25-FEB 08:00. OIC console shows AUTHENTICATION_FAILURE at Invoke Salesforce REST step. salesforce-prod-conn credential expired.

Root Cause

Salesforce OAuth token for the OIC connection salesforce-prod-conn expired on 24-FEB-2026 18:42. Token rotation is required every 90 days per Salesforce security policy. The 90-day renewal reminder was not configured in the OIC connection management process.

Tables Affected

OIC Monitoring: 7 failed instances — all failed at InvokeSalesforce step, error: AUTHENTICATION_FAILURE, token_expired
OIC Connections: salesforce-prod-conn — lastTokenRefresh: 26-NOV-2025, status: Expired

Fix Applied

Salesforce OAuth token refreshed via OIC console > Connections > salesforce-prod-conn > Test. Connection status confirmed Active. 7 failed instances resubmitted via OIC Monitoring > Resubmit — all 7 succeeded. Opportunity records in Salesforce confirmed updated.

Prevention

OIC connection token expiry calendar alert added — 7-day advance reminder for all OAuth connections. Connection health check added to the weekly SYS-06 monitoring run. Salesforce token refresh step added to integration management runbook.

OAuth Token Expired — OIC Connection

The most common OIC integration failure. OAuth tokens for third-party connections (Salesforce, ServiceNow, Workday) expire on a schedule set by the target system. SYS-06 identifies the expired connection and the refresh path.

Payload

REST API 400 — Payload Validation Failure

Required field missing, wrong data type, or value fails Fusion validation. OIC error detail or Fusion REST error response body identifies the specific field. SYS-06 maps the error to the source system field for correction.

FBDI

FBDI Import Job Completed with Errors

Bulk data import rejected some records. ESS output log provides row-level rejection detail. SYS-06 categorizes errors and identifies whether the correction is in the source file or in Fusion setup.

BICC

BICC Extract Gap — Outbound Feed Incomplete

BICC extract did not complete for the scheduled window — downstream analytics system has a data gap. SYS-06 identifies the extract definition and the failure reason from the BICC console.

Data Source	Type	Purpose
OIC Monitoring Console	OIC UI	Instance status, error detail, payload at failure point
OIC Connections	OIC UI	Connection health — OAuth status, last test, expiry
ESS: Import Job History	ESS	FBDI import status and output log
BICC Extract Console	BICC UI	Outbound extract job status and data volume
OTBI: Integration Subject Area	OTBI	Population-level integration failure analysis

Decision Framework

How Every Resolution Decision Is Made

Every condition identified by the diagnostic maps to exactly one resolution path. In Fusion Cloud, all paths go through supported Oracle interfaces — UI, REST API, FBDI, or ESS. Direct database access does not exist in this environment.

First Option — Always

Can the Fusion UI resolve this?

Oracle's own Fusion screens, Scheduled Processes (ESS), and workflow tools are always the first resolution path. Manage Invoices, Manage Suppliers, Manage Accounting Periods, BPM Worklist, Scheduled Processes — the diagnostic identifies the exact navigation path and screen sequence for every condition that can be resolved this way. No third-party tools, no API calls, no risk beyond what Oracle's own UI carries.

✓ Functional First

When the UI Path Is Insufficient

Can a REST API PATCH or FBDI reimport resolve this?

For bulk corrections or conditions not surfaced in the standard UI, Oracle Fusion's public REST APIs and FBDI import templates are the supported programmatic path. A REST API PATCH call to correct an invoice distribution account, an FBDI resubmission with corrected records after an import failure, or a Mass Update via the REST API — these are supported, documented, and reversible through normal Oracle mechanisms. The current state is exported before any API call is made.

→The API endpoint is an Oracle-published, versioned REST resource

→The FBDI template matches the current Fusion release version

→The pre-action state is exported (OTBI report / GET response) before the PATCH or import runs

→The result is verified via a follow-up GET or OTBI query before the case is closed

⚡ API / FBDI

Hard Stops — No Exceptions

Does this require Oracle Support?

Certain conditions in Fusion Cloud cannot be resolved through any customer-accessible interface. The diagnostic flags these and generates the Service Request documentation:

✗ESS job infrastructure failures — job status Error (not Completed with Warnings) indicating an engine-level issue not caused by data

✗Subledger accounting engine errors — Create Accounting failures where the error is in the Oracle accounting engine, not in the source transaction data

✗Recurring failures after correct setup — a condition that returns after a confirmed correct resolution indicates a code defect, submitted as an SR with a reproducible test case

✗Fusion data corruption — records in an inconsistent internal state not reachable through any published API or UI action

⚠ Oracle Support

For All Actions Taken

Export → Act → Verify → Document

Before any UI action, ESS resubmission, REST API call, or FBDI reimport — the current error state is exported via OTBI report, BIP report output, or REST API GET response. After the action, a verification step confirms the expected outcome. The complete sequence — tool used, pre-action state, action taken, result verified — is written into the KB article as the primary record of what was done and why.

📋 Documented

Condition Identified	Resolution Path	Notes
OIC authentication failure — OAuth token expired	Functional First	Refresh the connection credential via OIC console > Connections > Test/Re-authorize. SYS-06 identifies the connection, the expiry date, and the resubmission path for failed instances.
Failed OIC instances need resubmission	Functional First	Resubmit failed instances via OIC Monitoring > Select instances > Resubmit. SYS-06 identifies instances that are safe to resubmit (authentication-only failure, idempotent payload) vs those requiring payload correction first.
REST API 400 error — payload validation failure	Functional First	Correct the payload in the source system or the OIC mapping. SYS-06 identifies the specific field and validation rule from the OIC error detail or the Fusion REST API error response body.
REST API 500 error — Fusion server error	Oracle Support SR	A 500-series response from the Fusion REST API indicates a server-side error. SYS-06 documents the endpoint, payload, request ID, and timestamp for the Oracle Support SR.
FBDI import failure — bulk data rejected	Functional First	Review the ESS import job output log. Correct the FBDI file and reimport via Load Interface File for Import. SYS-06 identifies the failing rows and column-level errors from the ESS log.
BICC extract not completing — outbound data feed gap	Functional First	Review the BICC extract console for the failing extract definition. SYS-06 identifies whether the failure is a data volume issue, a changed Fusion object, or a target connection problem.
OIC integration deactivated — flow not running	Functional First	Reactivate the integration via OIC console > Integrations > Activate. SYS-06 confirms the integration status and the last successful activation timestamp.
OIC infrastructure failure — multiple integrations failing simultaneously	Oracle Support SR	Multiple OIC integrations failing across unrelated connections at the same time indicates an OIC instance-level issue. SYS-06 documents the affected integrations and timestamps for the Oracle Support SR.

Safeguards

Nothing Acts Without a Documented State

Fusion Cloud's SaaS architecture eliminates direct database access — which means every action is a supported Oracle API call, UI operation, or ESS submission. Before any action runs, the current error state is captured. After any action, the result is verified.

Pre-Action Documentation — All Completed First

✓

OIC Monitoring — failed instance list and payloads exported

Exported before any corrective action is taken

✓

OIC Connection detail — credential status before refresh

Exported before any corrective action is taken

✓

ESS Import job history — FBDI status for the window

Exported before any corrective action is taken

✓

Post-action verification

Follow-up OTBI query or REST GET confirms the expected state before the case is closed

Fusion Audit Trail — What Replaces CONS_BACKUP

In EBS R12, a CONS_BACKUP table provides the rollback point. In Fusion Cloud, the equivalent audit trail is built from three sources that together give a complete before-and-after record:

BEFORE STATE

OTBI report export or REST API GET response saved as the pre-action snapshot

ACTION RECORD

Fusion audit trail (Setup and Maintenance > Audit Reports) captures every UI and API change with user, timestamp, old value, and new value

AFTER STATE

Post-action OTBI query or REST GET confirms the fix — this output becomes the KB article verification artifact

SYS-06 — Fusion Diagnostic Framework

════════════════════════════════════════════════════════════
  ORACLE FUSION — INTEGRATION MONITOR DIAGNOSTIC STEPS
════════════════════════════════════════════════════════════
  Platform           : Oracle Integration Cloud + Oracle Fusion Cloud
  Tools              : OIC Monitoring, ESS History, REST API, BICC Console
  Pre-Action Export  : Failed instance list and connection state saved
────────────────────────────────────────────────────────────
  Step 1 — OIC Console  : 7 failed instances — all at Salesforce invoke step ✓
  Step 2 — Error Detail : AUTHENTICATION_FAILURE — OAuth token expired ✓
  Step 3 — Connections  : salesforce-prod-conn — credential expiry confirmed ✓
  Step 4 — FBDI / BICC  : All other integration channels healthy ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — Credential refresh and instance resubmission path identified
════════════════════════════════════════════════════════════
  Documentation      : KB article from OIC console and connection detail
  Audit Trail        : OIC connection change logged in OIC audit history
  SR Reference       : N/A — authentication error resolved via OIC console
════════════════════════════════════════════════════════════

Knowledge Base

Every Execution Produces a Record

The knowledge base article is generated automatically from the script's execution output. No manual documentation required. It becomes the institutional record — for the team, for auditors, and for every future engagement in the same environment.

Zero Manual Effort

Every field — environment, tables, before/after values, backup reference, root cause, prevention — is generated from actual execution output. Nothing is written by hand.

Patterns Surface Over Time

The first engagement produces findings. The third produces patterns. Recurring conditions that are invisible as individual incidents become obvious as knowledge base trends.

Survives Staff Turnover

The knowledge base is an institutional record of the Oracle environment. A new manager, a new DBA, or an external auditor can read exactly what happened, what was done, and what prevents recurrence.

KB-FC-SYS-0618-001

OIC ERP-to-Salesforce Sync — 7 Failures: OAuth Token Expired on Salesforce Connection

Oracle Fusion Cloud · System

● RESOLVED

Symptom

Root Cause

Tables

OIC Monitoring: 7 failed instances — all failed at InvokeSalesforce step, error: AUTHENTICATION_FAILURE, token_expired
OIC Connections: salesforce-prod-conn — lastTokenRefresh: 26-NOV-2025, status: Expired

Fix Applied

Prevention

Documentation Page	Title	Scenario
Embedded Banking Services	Embedded Banking Services	Oracle Cloud ERP integration connectivity and acknowledgment processing
Using Payables Invoice To Pay	Using Payables Invoice to Pay — Fusion	Inbound invoice integration via FBDI and REST API reference
Apinvoicesinterface 28280	AP_INVOICES_INTERFACE	Interface table payload structure for inbound integration errors

Integration & Web Service Monitor (Oracle Fusion)

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in SYS-06

Documentation Before Every Action — SYS-06

Pre-Action Documentation — SYS-06

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

What This Script Finds

OAuth Token Expired — OIC Connection

REST API 400 — Payload Validation Failure

FBDI Import Job Completed with Errors

BICC Extract Gap — Outbound Feed Incomplete

Data Sources

How Every Resolution Decision Is Made

Nothing Acts Without a Documented State

Every Execution Produces a Record

Oracle Documentation References

Ready to Resolve This in Your Environment?

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in SYS-06

Documentation Before Every Action — SYS-06

Pre-Action Documentation — SYS-06

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

What This Script Finds

OAuth Token Expired — OIC Connection

REST API 400 — Payload Validation Failure

FBDI Import Job Completed with Errors

BICC Extract Gap — Outbound Feed Incomplete

Data Sources

How Every Resolution Decision Is Made

Nothing Acts Without a Documented State

Every Execution Produces a Record

Oracle Documentation References

Related Diagnostic Scripts

ESS Job Health (Fusion)

Security & Role (EBS)

AP Invoice Validation (Fusion)

Ready to Resolve This in Your Environment?