Oracle E-Business Suite and ADP integration

What moves between them

The main flow runs from ADP into Oracle E-Business Suite. After each payroll run, ml-connector reads ADP general ledger documents and posts the labor cost journals into the EBS general ledger, mapped to the matching account combinations and operating unit. Worker records flow the same direction so EBS headcount reflects ADP hires, terminations, and rehires. Reference data such as cost centers, departments, and job codes is aligned so payroll allocations land on valid EBS account segments. GL postings are read-only in ADP, so ml-connector never writes financial entries back to payroll.

How ml-connector handles it

ml-connector stores both credential sets encrypted and presents the ADP client certificate at the TLS layer on every request, refreshing the ADP bearer token when a call returns 401. On the EBS side it logs in for a session token, attaches it as the session cookie, and adds the responsibility and operating unit context to every call, since multi-org context is mandatory. Posting a payroll journal is a two-step write: ml-connector inserts rows into GL_INTERFACE with a unique SOURCE value, then triggers or waits for the Journal Import concurrent program, so a 200 means the row was queued rather than posted, and the base tables are polled to confirm. Because EBS is pull-only, worker data and ADP general ledger documents are read on a schedule tied to your payroll calendar, and ADP event notifications are accepted where they are enabled. Cost centers and account combinations are mapped first so every journal line references an account that already exists in EBS. ADP rate limits return HTTP 429 per gateway node and EBS itself has no rate limiter, so ml-connector keeps EBS concurrency low to protect the shared instance, backs off and retries on ADP, and tracks the ADP certificate expiry so a renewal does not turn into an outage. 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 around 600 employees runs Oracle E-Business Suite R12.2 on its own servers for finance and procurement and uses ADP Workforce Now for payroll across three plants. Before the integration, the finance team exported payroll registers from ADP every pay period and keyed the labor totals into EBS by hand, then spent the first days of month-end close chasing differences between HR headcount and the labor accounts in the ledger. With Oracle E-Business Suite and ADP connected, each payroll run's GL document flows into the EBS general ledger automatically, allocated to the operating unit and cost center for each plant, and worker changes keep the two systems aligned. Month-end close starts with the labor accounts already reconciled, and the manual re-keying step is gone.

What you can do

• •Post ADP payroll GL documents into the Oracle E-Business Suite general ledger after every pay run via the GL_INTERFACE table and Journal Import.
• •Keep Oracle E-Business Suite headcount aligned with ADP hires, terminations, and rehires.
• •Map ADP cost centers, departments, and job codes to EBS account combinations so payroll lands on valid accounts.
• •Authenticate ADP with OAuth2 and the required mutual TLS certificate, and EBS with a session token plus operating unit context.
• •Poll on a schedule tied to your payroll calendar at low EBS concurrency, with retries and a full audit trail on every record.

Questions

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

The main flow is ADP into Oracle E-Business Suite. Payroll GL documents and worker records move from ADP into EBS, while cost centers and account combinations are aligned so journals land on valid accounts. ADP general ledger documents are read-only, so ml-connector does not write financial entries back into payroll.

How are payroll journals written into Oracle E-Business Suite?

EBS writes are a two-step open interface pattern. ml-connector inserts journal rows into the GL_INTERFACE table with a unique SOURCE value, then triggers or waits for the Journal Import concurrent program to validate and post them. A 200 on the insert means the row was queued, so ml-connector polls the base tables to confirm the journal actually posted.

Does the integration use webhooks, and how does it handle ADP mutual TLS?

Oracle E-Business Suite has no self-service webhooks, so EBS data is read by scheduled polling of the open interface views filtered on last update date. ADP requires a client certificate at the TLS layer on every call in addition to OAuth2 credentials, so ml-connector stores the certificate encrypted, presents it on each request, and tracks its expiry so a renewal is handled before it can cause an outage.