Oracle E-Business Suite

Spend connects to Oracle EBS R12.2 through Integrated SOA Gateway (ISG) REST services. It never writes to Payables base tables: invoices go through the open interface and Payables Open Interface Import, the route Oracle supports for third-party invoices.

Direction	What	EBS objects
In	Suppliers and primary pay site	AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL
In	Approved standard POs, lines, match level, charge account, Projects coding	PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PA_PROJECTS_ALL, PA_TASKS
In	Receipts, net of corrections and returns, with inspection	RCV_SHIPMENT_HEADERS, RCV_TRANSACTIONS
Out	Approved invoices, PO-matched or coded, with Projects coding	AP_INVOICES_INTERFACE, AP_INVOICE_LINES_INTERFACE, then APXIIMPT
In	Import outcome: AP invoice id or rejection reasons	AP_INVOICES_INTERFACE.STATUS, AP_INTERFACE_REJECTIONS
In	Budget, encumbrance and actual balances, for funds checks	GL_BALANCES, GL_BUDGET_VERSIONS, GL_CODE_COMBINATIONS_KFV
Out	Approved expense reports as EXPENSE REPORT invoices	AP_INVOICES_INTERFACE, AP_INVOICE_LINES_INTERFACE, then APXIIMPT

Matching follows each PO shipment: no receipt required means 2-way, receipt required means 3-way, inspection required means 4-way.

Setup (about a day for the customer or their EBS partner)

1. Add SPEND as a value of the Payables lookup type SOURCE.
2. Compile the Spend integration PL/SQL package in the APPS schema (database 12.2 or later).
3. In the Integration Repository, generate and deploy its REST service with the alias XXSPEND_API, and grant its methods to the integration user’s responsibility.
4. Create an integration user with a Payables responsibility for the operating unit, such as PAYABLES_MANAGER under SQLAP.
5. Set the connector’s variables on the Spend server (each with the tenant id as a suffix, such as EBS_ISG_URL_TEN_ACME):

Variable	Meaning
EBS_ISG_URL	ISG base URL, HTTPS only
EBS_USERNAME, EBS_PASSWORD	The integration user
EBS_ORG_ID	Operating unit
EBS_RESPONSIBILITY, EBS_RESP_APPLICATION	Such as PAYABLES_MANAGER and SQLAP
EBS_SEGMENTS	Where fund and cost center sit in the accounting flexfield, as JSON
EBS_BUDGET_NAME	GL budget read hourly for funds checks

Schedule

Job	When
Suppliers, POs and receipts	Every 15 minutes
Approved invoices to the open interface, then import	After each approval batch (checked every 5 minutes, at most an hour after the first approval waits)
Import results	10 minutes after each import, then hourly while any are pending
Payments read back from Payables	Hourly
Funds balances	Hourly
Expense reports out, reimbursements back	Daily
Invoices and audit packets to the CMIS repository	Hourly, once EBS has imported the invoice

When EBS rejects an invoice, Spend opens an AP case with the rejection codes and stops sending it until the cause is fixed. EBS Payables stays the system that pays; Spend reads the check or EFT number and date back and marks the invoice paid.

Before go-live

Check on the customer’s own instance: descriptive flexfields, suppliers with more than one pay site, how the requester is found on the PO distribution, POs with several shipments or distributions per line, whether import calculates tax, the import program’s arguments at the patch level in use, and the budget name and encumbrance types for funds checks.