Oracle EBS P2P + private AI
AI for Oracle E-Business Suite Procure to Pay, From Requisition to Payment
Short answer
AI for Oracle EBS procure to pay lets buyers, receiving staff and AP analysts ask plain-English questions across requisitions, purchase orders, receipts and Payables invoices, answered from live EBS data with the SQL shown. It reads through read-only database access or Integrated SOA Gateway services under EBS security, and can run fully on-prem.
- ERP
- Oracle E-Business Suite 12.2, Oracle E-Business Suite 12.1
- Industries
- Manufacturing, Aerospace, Defense, Electronics
- Written for
- Procurement Director
Procure to pay in Oracle E-Business Suite crosses at least three modules: iProcurement or Purchasing for requisitions and orders, Receiving for deliveries, and Payables for invoices, all closing into General Ledger through Subledger Accounting. Large EBS estates run it across many operating units, with approval hierarchies, blanket agreements and supplier sites accumulated over fifteen years.
The reporting problem is not lack of data. PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, RCV_TRANSACTIONS and AP_INVOICES_ALL hold everything. The problem is that a straight question such as which received lines are uninvoiced beyond thirty days in operating unit 204 needs a specialist to write and validate the SQL, and the specialist is queued behind upgrade work.
Oracle's AI direction centers on Fusion Cloud applications. Many EBS customers have deliberately stayed on 12.2 with online patching, often for customizations and for control of where data resides. Sending supplier terms, pricing and bank details to a public model is a difficult conversation with security and with defense or aerospace customers.
This page explains how a private AI layer attaches to EBS procure to pay, which tables and interfaces it touches, and where it adds real value to buyers and AP, compared with seeded reports and Discoverer-era or OBIEE replacements already in place.
What usually gets in the way
The problems we hear most from procurement director teams running Oracle E-Business Suite 12.2.
Cross-module questions need a SQL specialist
Joining requisitions to POs to receipts to invoices across PO, RCV and AP tables is routine for a developer and impossible for a buyer, so questions queue behind other work.
Multi-org security hides the full picture
Operating unit access through MO: Security Profile means each user sees a slice. Group-level spend questions require someone with wide access to run and combine reports.
Invoice holds pile up without a clear cause
Payables holds such as quantity received, price or matching holds accumulate, and AP analysts open each invoice to find out why. Pattern analysis by supplier or buyer is rarely done.
Approvals stall in hierarchies
Requisitions and POs waiting in Approvals Management Engine or position hierarchies sit unnoticed when an approver is away.
Customizations make the seeded reports unreliable
Personalizations, custom DFF segments and CEMLI extensions mean the seeded reports do not always show what the business actually tracks.
Where AI earns its place in Oracle E-Business Suite 12.2
Each use case names the ERP objects it reads or writes, so your ERP team can judge the integration effort before anyone commits budget.
Uninvoiced receipts accrual review
Lists received-not-invoiced lines by supplier, operating unit and age, with the matching rule shown.
Touches: RCV_TRANSACTIONS, PO_LINE_LOCATIONS_ALL, AP_INVOICE_LINES_ALL, PO_DISTRIBUTIONS_ALL
Outcome: Shortens month-end accrual review by giving AP a ranked list instead of an exported report.
Invoice hold root cause
Groups Payables holds by hold code, supplier and buyer and explains the likely cause per group.
Touches: AP_HOLDS_ALL, AP_INVOICES_ALL, PO_HEADERS_ALL
Outcome: Moves AP from opening invoices one by one to fixing the few causes that repeat.
Requisition and PO approval backlog
Shows documents stuck in approval, the current approver and days waiting.
Touches: PO_REQUISITION_HEADERS_ALL, PO_HEADERS_ALL, PO_ACTION_HISTORY
Outcome: Reduces silent stalls from absent approvers.
Supplier on-time delivery analysis
Compares promised date against receipt date per supplier and item category.
Touches: PO_LINE_LOCATIONS_ALL (PROMISED_DATE, NEED_BY_DATE), RCV_TRANSACTIONS
Outcome: Gives sourcing managers evidence for supplier reviews.
Price variance and PPV drill-down
Explains purchase price variance by showing PO price, invoice price and standard cost movements.
Touches: PO_LINES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, MTL_MATERIAL_TRANSACTIONS
Outcome: Replaces ad hoc spreadsheet reconciliation.
Draft requisitions from shortages
Proposes requisitions for shortages identified by planning, left in an incomplete state for the requester to review and submit.
Touches: MRP_RECOMMENDATIONS, PO_REQUISITIONS_INTERFACE_ALL
Outcome: Speeds routine replenishment while keeping approval control.
Blanket agreement consumption
Reports release consumption against blanket agreement limits and warns before the limit is reached.
Touches: PO_HEADERS_ALL (blanket), PO_LINES_ALL, PO_LINE_LOCATIONS_ALL
Outcome: Avoids surprise exhaustion of negotiated agreements.
Reference architecture
The AI layer reads EBS data through read-only access with an APPS-independent schema account or through Integrated SOA Gateway REST services. It maps EBS security so answers reflect an operating unit and responsibility the user is entitled to.
- 1
EBS connector
A read-only database user on selected PO, RCV, AP and XLA objects or custom views, with Integrated SOA Gateway REST services for actions. APPS credentials are not used by the AI layer.
- 2
Semantic layer
Maps operating units, suppliers and sites, match approval levels and your descriptive flexfield segments to business terms; reflects customizations documented by your EBS team.
- 3
Model serving
An open-weight model on vLLM or Ollama on customer GPUs or a private cloud; sized for read-heavy question answering.
- 4
Retrieval and agents
Grounded SQL with visible queries; requisition suggestions go through the PO requisitions open interface into an incomplete state.
- 5
Governance and audit
Operating-unit scoping, per-user logging and approval before any interface write.
Integration notes for your ERP team
- Use a read replica or Active Data Guard standby where available to protect OLTP performance.
- Respect operating unit security by setting the multi-org context (MO_GLOBAL.SET_POLICY_CONTEXT) so queries return only permitted rows.
- Integrated SOA Gateway exposes PL/SQL APIs as REST services; use only those your team has deployed and secured.
- Prefer the open interfaces (PO_REQUISITIONS_INTERFACE_ALL, PO_HEADERS_INTERFACE) for any write, never direct inserts into base tables.
- In 12.2, avoid reading from the patch edition during online patching cycles; point the connector at the run edition.
- Descriptive flexfield segments in ATTRIBUTE columns are mapped from the flexfield definitions, not guessed.
Deployment options
Air-gapped on-prem
Defense and aerospace estates running EBS inside restricted networks.
Model, retrieval and connector run on local GPUs with no outbound route; a read replica or Active Data Guard standby can serve queries.
Private or sovereign cloud
EBS hosted on OCI or a managed provider.
A dedicated tenant in the same region and tenancy boundary as EBS.
Hybrid
Regional EBS instances with local data residency requirements.
One governance layer, instance-level connectors, local data stays local.
Compliance and data control
How the architecture supports your obligations. Certification and accountability stay with your organisation; the design keeps the evidence straightforward.
SOX
Read-only by default and interface-based drafting preserve segregation of duties; approvals stay in EBS.
ITAR and EAR where applicable
On-prem processing keeps controlled technical and pricing data in your boundary; your compliance owner defines scope.
GDPR
Supplier contact and employee approver data stays inside infrastructure you control.
DFARS and CMMC flow-down
An enclave deployment lets you document where CUI-adjacent procurement data is processed; certification remains the customer's.
How an engagement runs
Phase 1 . 2-3 weeks
Discovery
- -Module and customization inventory
- -Operating unit and responsibility map
- -Question backlog from buyers and AP
- -Architecture decision
Phase 2 . 6-8 weeks
Pilot
- -Read-only connector on a non-production clone
- -Uninvoiced receipts and hold analysis live
- -Accuracy review vs seeded reports
- -Security review
Phase 3 . 4-6 weeks
Production
- -Cutover to read replica
- -Operating unit scoping
- -Runbook
- -DBA handoff
Phase 4 . Ongoing
Scale
- -More operating units
- -Draft requisition agent
- -Supplier analytics
- -Quarterly accuracy review
Questions to ask any vendor, including us
A short list that separates real Oracle E-Business Suite 12.2 AI work from a chatbot demo.
- Does the connector use APPS or a dedicated read-only account?
- How does it enforce operating unit access?
- Will queries run against a replica, and what is the load on production?
- How does it handle our descriptive flexfields and CEMLI objects?
- What happens after a 12.2 patch or an ADOP cycle?
- Can every generated query be reviewed?
- Do writes use open interfaces?
- What would you say is better served by existing OBIEE or BI Publisher content?
Frequently asked questions
Can AI run on Oracle EBS without moving to Fusion?
Yes. A private model can read EBS tables or REST services directly, so no migration is needed. EBS stays the system of record, and the AI layer is an external read-focused service that respects EBS security rather than replacing any module.
How do you protect EBS performance?
By reading from a replica or standby where possible, bounding queries by date and operating unit, and caching reference data. The pilot measures load against a clone before production is touched.
Can it match invoices to POs and receipts?
It can show and explain three-way matching results and holds. Matching itself is performed by Payables as configured. Suggested actions are surfaced for AP to act on; nothing is released or approved automatically.
Does it work with iProcurement?
It reads the same requisition and PO tables iProcurement writes to. It does not change the iProcurement catalog or shopping experience, though it can help explain why a requisition is stuck in approval.
Is supplier pricing safe?
In on-prem and private-cloud deployments, yes: processing stays in your infrastructure with no public AI API call. You should verify network paths and logging during discovery.
What about our customizations?
Customizations are the main discovery topic. Custom tables, flexfields and extensions are documented with your EBS team and mapped in the semantic layer. Unknown customizations are the most common reason for wrong answers.
Is this a replacement for OBIEE or BI Publisher?
No. Fixed operational reports are usually better kept where they are. AI adds value for ad hoc questions and explanations that nobody built a report for.
Related guides
AI for Oracle E-Business Suite, Without Leaving On-Prem
Add AI to Oracle E-Business Suite 12.2 without moving off-prem. Query concurrent programs, interface tables, and AP/PO data with a private LLM. See how.
Oracle EBS order management AIAI for Oracle EBS Order Management, From Booking to Invoice
Private AI for Oracle EBS Order Management: order holds, ATP, pick release, shipping and AutoInvoice questions answered from live data, no cloud AI needed.
PO follow-up that does not wait on a personAI Purchase Order Automation: Supplier Follow-Up and Expedite Without a Buyer Chasing Email
AI drafts routine PO confirmation and expedite messages from open ERP order data, with a buyer approving every message and change before it goes out.
AP automation + on-prem AIAI for accounts payable invoice matching in your ERP
On-prem AI reads vendor invoices, runs 3-way match against your ERP PO and receipt, and routes only real exceptions to your AP team. No invoice data leaves your network.
Oracle EBS industrial AIAI for Oracle EBS in Industrial Manufacturing: WIP, MRP, and BOM Questions Answered Directly
AI for Oracle E-Business Suite in industrial manufacturing: WIP jobs, BOMs, MRP, inventory and purchasing answered in plain English, private and read-only.
RAG + SQL + permissionsA Private LLM Grounded on Your ERP Data
How a private LLM answers questions on your ERP data: RAG plus text-to-SQL, role-based permissions inherited from the ERP, and where each fits.
Plan it with numbers
Procure-to-Pay Efficiency Calculator
Quantify the labor cost buried in your purchase order and invoice processing, including exception handling, and benchmark your cost per invoice against automation leaders.
Free ToolAP Invoice Automation ROI Calculator
Estimate the annual savings, payback period, and three-year ROI of automating accounts payable invoice capture, matching, and posting.
Free ToolSupplier Risk Scorecard
Score your supply base across financial, sourcing, quality, cyber, and continuity risk in eleven questions, and get a banded action plan for the gaps you find.
GuideAI Agents for ERP: The Complete Guide
Everything you need to know about AI agents for ERP systems. How they work, ROI expectations, implementation approaches, and real-world results.
GuideERP Integration Patterns with AI Middleware
Modern ERP integration patterns using AI middleware. Event-driven architecture, API orchestration, and intelligent data synchronization for Infor and Salesforce.
GuideLegacy ERP Modernization with AI Agents
Modernize legacy ERP systems with AI. Gradual transformation from BPCS, MAPICS, BAAN, and other legacy systems to modern Infor cloud ERP.
Talk it through with an engineer who knows Oracle E-Business Suite 12.2
Bring one real question your team cannot answer from the ERP today. We will map the data path, the model, and where it runs, and tell you honestly if AI is the wrong tool for it.