Oracle E-Business Suite and Anaplan integration

What moves between them

The main flow runs from Oracle E-Business Suite into Anaplan. ml-connector reads posted GL journal lines and AP invoices from the EBS open interface views, along with the GL code combinations and cost-center segments behind them, and loads them into Anaplan as actuals in a budget module and as members of the chart-of-accounts and cost-center lists. The reverse flow carries approved Anaplan plan values back into Oracle E-Business Suite: ml-connector runs the Anaplan export action, downloads the file, and posts the figures into GL_INTERFACE so the Journal Import concurrent program creates budget or allocation journals. Reference lists such as accounts and cost centers are aligned first so every planning row resolves to a real ledger combination. Cadence follows your close and planning calendar, typically after each period close and on a regular intraday or daily refresh.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the EBS side it obtains a session token, sends it as the cookie on every request, attaches the operating-unit context such as ctx_orgid, and re-authenticates when EBS returns 401 as the 30 to 60 minute session expires. It accepts the full tenant URL and the deployed service aliases per customer, since EBS publishes no shared base URL and each instance names its services differently. On the Anaplan side it logs in for a 35-minute auth token, refreshes it before expiry, and discovers the workspace ID, model ID, and the import and export action IDs at runtime, respecting the lowercase workspace and uppercase model casing. Because both systems are pull-only, it polls EBS views by LAST_UPDATE_DATE with limit and offset, and polls Anaplan task status until complete rather than waiting for a push. Accounts and cost centers are mapped first so every loaded actual and every returned journal references a combination that already exists. Two real gotchas shape the design. Anaplan locks a model while an import, export, or process runs, so ml-connector serializes actions against the same model and respects the 600 request per minute tenant limit with backoff on HTTP 429. EBS writes are asynchronous: posting to GL_INTERFACE inserts rows, and the Journal Import concurrent program must run before the journal exists, so ml-connector sets a unique source value, dedupes on source plus reference to avoid double-posting, and confirms by reading the base tables. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized manufacturer with about 900 employees runs Oracle E-Business Suite for the general ledger, payables, and procurement across several operating units, and its finance team builds the annual budget and rolling forecast in Anaplan. Before the integration, an analyst exported trial balances and AP detail from EBS each month, reshaped them in spreadsheets, and loaded them into Anaplan by hand, then keyed the approved budget back into the ledger line by line. The actuals were always a few days stale, cost-center mismatches crept in, and budget-versus-actual variance reports never quite tied to the ledger. With Oracle E-Business Suite and Anaplan connected, posted journals and AP invoices flow into the planning models within the refresh window, mapped to the right accounts and cost centers, and the approved budget posts back through Journal Import. The monthly export-and-reshape step is gone, and variance reporting starts from numbers that match the ledger.

What you can do

• •Load Oracle E-Business Suite GL journals and AP invoices into Anaplan modules as actuals for budget-versus-actual reporting.
• •Sync EBS GL code combinations and cost-center segments into the matching Anaplan chart-of-accounts and cost-center lists.
• •Post approved Anaplan plan values back into Oracle E-Business Suite through GL_INTERFACE and the Journal Import concurrent program.
• •Bridge the EBS session token and operating-unit context to the Anaplan auth token and workspace and model IDs.
• •Poll both pull-only systems on your close calendar, serialize Anaplan model actions, and keep a full audit trail on every record.

Questions

Which direction does data move between Oracle E-Business Suite and Anaplan?

The main flow is Oracle E-Business Suite into Anaplan, carrying posted GL journals, AP invoices, and the accounts and cost centers behind them so plans compare against real actuals. Approved plan values flow back the other way into GL_INTERFACE, where the Journal Import program turns them into budget or allocation journals. Anaplan is a planning tool with no ledger of record, so the authoritative accounting stays in Oracle E-Business Suite.

Neither system has webhooks, so how does the sync stay current?

Both Oracle E-Business Suite and Anaplan are pull-only, with no event push, so ml-connector polls on a schedule tied to your close and planning calendar. It reads EBS open interface views filtered by LAST_UPDATE_DATE and paged with limit and offset, and it runs Anaplan import and export actions and polls their task status until complete. You set the cadence, typically a refresh after each period close plus a regular intraday or daily pull.

How does the integration deal with Anaplan model locking and the asynchronous EBS journal import?

Anaplan locks a model while any import, export, or process runs, so ml-connector serializes actions against the same model and backs off on the 600 request per minute tenant limit when it sees HTTP 429. On the EBS side, posting to GL_INTERFACE only inserts rows, and the Journal Import concurrent program must run before a journal exists. ml-connector sets a unique source value, dedupes on source plus reference to avoid double-posting, and confirms the result by reading the base tables.