Oracle E-Business Suite and UKG integration

What moves between them

The main flow is UKG into Oracle E-Business Suite. After each payroll run, ml-connector reads UKG's GL payroll journal export via the thirdpartypay endpoint, which includes GL account segments, cost center allocations, debit and credit amounts, and pay period dates. It maps these records to Oracle E-Business Suite GL accounts and cost center dimensions, then posts the payroll journals into EBS GL_JE_LINES via the Integrated SOA Gateway REST API. Employee and cost center reference data flows both directions to keep headcount and cost allocations aligned.

How ml-connector handles it

ml-connector stores both credential sets encrypted and uses HTTP Basic Auth with API key headers to call UKG. On the Oracle E-Business Suite side, it authenticates via the ISG login endpoint to obtain a session token, then uses that token on subsequent API calls along with the required application context headers for responsibility, GL responsibility application, security group, and organization ID. Because UKG GL export is asynchronous and EBS has no webhooks, ml-connector polls both systems on a schedule aligned to your payroll calendar. It reads the UKG thirdpartypay endpoint for GL segments and debit/credit amounts, maps cost centers to matching EBS GL account combinations using a configured mapping table, and posts the journal entry via REST to the ISG. When the ISG returns a confirmation or async job ID, it tracks the import status in the audit log so a failed concurrent program execution can be retried. UKG API keys are refreshed on 401; Oracle session tokens are validated before each request and re-fetched if expired.

A real-world example

A mid-sized manufacturing company runs Oracle E-Business Suite for all finance and procurement, and uses UKG for payroll and HR across three plants and a shared services center. Before the integration, the finance team exported the payroll register from UKG every two weeks, manually allocated labor costs to the correct departments and cost centers in a spreadsheet, and re-entered the totals into the EBS general ledger by hand. Month-end close took an extra 3 to 5 days because labor accounts had to be researched and reconciled against UKG. With Oracle E-Business Suite and UKG connected, each payroll run's GL journal flows automatically into EBS within an hour of final payroll processing, allocated to the correct responsibility and cost center, and the finance team starts the close process with all labor accounts already posted and balanced.

What you can do

• •Post UKG payroll GL journals into Oracle E-Business Suite's general ledger after each pay period, mapped to the correct GL accounts and cost centers.
• •Keep Oracle E-Business Suite headcount and cost center dimensions aligned with UKG employees and organizational structure.
• •Authenticate Oracle E-Business Suite via the Integrated SOA Gateway session token endpoint with required application context headers, and UKG via API key or OAuth credentials.
• •Poll UKG and Oracle E-Business Suite on a schedule tied to your payroll calendar, with retries and a full audit trail on every record.
• •Track payroll GL postings through the Oracle E-Business Suite concurrent program import cycle so failed entries can be corrected and replayed.

Questions

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

The main flow is UKG into Oracle E-Business Suite. Payroll GL journals from UKG post into EBS after each pay period. Employee and cost center reference data flows in both directions to keep the two systems aligned. Oracle E-Business Suite AP payments and invoices are read-only from the integration perspective.

How does ml-connector handle Oracle E-Business Suite's session tokens and application context requirements?

ml-connector authenticates to the ISG login endpoint with HTTP Basic Auth to obtain a session token, then includes that token on all subsequent requests. It also populates the required application context headers (responsibility, responsibility application, security group, organization ID) from the customer configuration so the API calls execute with the correct GL responsibility and org context. Tokens are validated before each request and refreshed on 401.

Does polling work for a payroll cycle that spans multiple time zones or organizations?

Yes. ml-connector accepts a configurable polling schedule tied to your payroll calendar so it can run after your final payroll process completes, regardless of time zone. Because UKG GL export includes cost center and responsibility mappings per record, and Oracle E-Business Suite's application context headers set the GL responsibility per request, the same payroll GL can be split across multiple responsibilities or organizations in a single import cycle.