AP Invoices with PO, Intercompany and SLA Details
Description:
AP Invoices with PO, Intercompany and SLA Details
Parameters
Ledger, Operating Unit, Invoice Date From, Invoice Date To, Accounting Date From, Accounting Date To, Supplier, Supplier Site, Invoice Source, Invoice Number, Exlude Invoice Line Types, Exlude Invoice Dist Types, Include Discarded Invoice Lines, Display Item Category Set, Show AP SLA Accounting, Show INV SLA Accounting, Show Intercompany Details
Used tables
po_req_distributions_all, po_requisition_lines_all, po_requisition_headers_all, po_distributions_all, po_line_locations_all, po_lines_all, po_headers_all, po_releases_all, po_line_types_v, mtl_units_of_measure, mtl_parameters, hr_all_organization_units_vl, financials_system_params_all, mtl_system_items_vl, rcv_transactions, rcv_shipment_headers, mtl_item_categories_v, ap_inv, po
Categories
Dependencies
If you would like to try one of these Oracle EBS SQLs without having Blitz Report installed, note that some of the reports require functions from utility package xxen_util.
Example Report
Report SQL
www.enginatics.com/reports/ap-invoices-with-po-intercompany-and-sla-details/
Blitz Report™ import options
AP_Invoices_with_PO_Intercompany_and_SLA_Details.xml
Case Study & Technical Analysis: AP Invoices with PO, Intercompany and SLA Details
1. Executive Summary
Business Problem
In the Oracle E-Business Suite “Procure-to-Pay” (P2P) cycle, data is often siloed across multiple modules: Purchasing, Receiving, Payables, and Subledger Accounting (SLA). Standard reports typically focus on one area (e.g., “Invoice Register” or “Purchase Order Detail”), making it difficult for Finance and Procurement teams to:
- Trace Lineage: Easily link an invoice back to the original Requisition and Receipt to validate 3-way matching.
- Reconcile Accounting: Verify that the AP Invoice distribution accounts match the final SLA journal entries posted to the General Ledger.
- Analyze Intercompany: Isolate and reconcile intercompany transactions which often have complex accounting flows.
Solution Overview
The AP Invoices with PO, Intercompany and SLA Details report serves as a comprehensive P2P analysis tool. It bridges the gap between modules by joining AP Invoice data directly with upstream Purchasing/Receiving records and downstream SLA accounting entries. This “horizontal” view allows users to audit the entire lifecycle of a transaction in a single row, ensuring data integrity and simplifying month-end reconciliation.
Key Benefits
- Full P2P Visibility: See the Requisition Number, PO Number, Receipt Number, and Invoice Number side-by-side.
- SLA Reconciliation: Optional inclusion of Subledger Accounting data allows for detailed reconciliation between AP Distributions and GL Journals.
- Intercompany Focus: Dedicated logic to identify and report on Intercompany transactions, aiding in elimination and reconciliation processes.
- Flexible Granularity: Parameters allow users to toggle detail levels (e.g., “Show AP SLA Accounting”), optimizing performance and relevance.
2. Technical Analysis
Core Tables and Views
The report navigates the complex P2P schema, primarily anchoring on Payables and linking outwards:
AP_INVOICES_ALL/AP_INVOICE_LINES_ALL/AP_INVOICE_DISTRIBUTIONS_ALL: The core Payables tables containing invoice header, line, and accounting distribution data.PO_HEADERS_ALL/PO_LINES_ALL/PO_DISTRIBUTIONS_ALL: Purchasing tables linked viaPO_DISTRIBUTION_IDto show the source order.PO_REQUISITION_HEADERS_ALL/PO_REQ_DISTRIBUTIONS_ALL: Requisition tables linked to the PO to show the initial request.RCV_TRANSACTIONS/RCV_SHIPMENT_HEADERS: Receiving tables linked to show proof of delivery (Receipts).XLA_AE_HEADERS/XLA_AE_LINES: Subledger Accounting tables (conditionally joined) to show the final debits and credits sent to GL.GL_CODE_COMBINATIONS: For resolving account segment values.
SQL Logic and Data Flow
The query likely starts with AP_INVOICE_DISTRIBUTIONS_ALL (or Lines) as the grain, as this is the lowest level of detail that links to both PO Distributions and SLA.
- Left Outer Joins: Used extensively for PO and Receipt tables, ensuring that “Non-PO” invoices (like expense reports or direct entry) are still reported, just with blank PO columns.
- Conditional Logic (SLA): The “Show AP SLA Accounting” parameter likely controls a dynamic join or a
UNIONbranch that brings inXLAtables. This is a critical performance feature, as joining to SLA tables significantly increases row count and query cost. - Intercompany Logic: Specific filters or columns are derived to flag transactions where the balancing segment of the liability account differs from the expense account, or based on specific Intercompany transaction types.
Integration Points
- Purchasing: Validates price variances by comparing Invoice Unit Price vs. PO Unit Price.
- Inventory/Receiving: Validates quantity variances by comparing Billed Quantity vs. Received Quantity.
- General Ledger: Provides the “Accounting Date” and final GL accounts.
3. Functional Capabilities
Parameters & Filtering
- Date Ranges: Filter by
Invoice Date(operational) orAccounting Date(financial/period close). - Supplier/Site: Target specific vendors for audit.
- Show Flags:
Show AP SLA Accounting: Enables the join to XLA tables for deep accounting analysis.Show Intercompany Details: Adds columns relevant to intercompany reconciliation.Include Discarded Invoice Lines: Allows filtering out cancelled/discarded lines for a cleaner view of “Net” liability.
Performance & Optimization
- On-Demand Joins: By making the SLA and Intercompany sections optional via parameters, the report avoids scanning massive tables (
XLA_AE_LINES) when users only need operational AP/PO data. - Indexed Columns: Filtering on
Accounting DateandOrg_IDleverages standard Oracle indexes for fast retrieval.
4. FAQ
Q: Why are the PO and Receipt columns blank for some rows? A: These are likely “Non-PO” invoices, such as manual expense entries or direct invoices that were not matched to a Purchase Order.
Q: Why do I see multiple rows for the same Invoice Line? A: If “Show AP SLA Accounting” is enabled, a single invoice distribution may result in multiple SLA journal lines (e.g., liability, expense, tax, variance), causing the row to split.
Q: How does this report help with Accrual Reconciliation?
A: By showing the PO_DISTRIBUTION_ID and the ACCRUAL_ACCOUNT, you can match the AP entry against the PO Receipt accrual to identify discrepancies in the “AP/PO Accrual Reconciliation” process.
Oracle E-Business Suite Reporting Library
We provide an open source Oracle EBS SQLs as a part of operational and project implementation support toolkits for rapid Excel reports generation.
Blitz Report™ is based on Oracle EBS forms technology, and hence requires minimal training. There are no data or performance limitations since the output files are created directly from the database without going through intermediate file formats such as XML.
Blitz Report can be used as BI Publisher and Oracle Discoverer replacement tool. Standard Oracle BI Publisher and Discoverer reports can also be imported into Blitz Report for immediate output to Excel. Typically, reports can be created and version tracked within hours instead of days. The concurrent request output automatically opens upon completion without the need for re-formatting.
The Filters, Columns, Rows and Values fields are used to create and deliver the data in pivot table format with full drill down to details.

The Excel template upload functionality in Blitz Report allows users to create their own layouts by uploading an Excel template with additional sheets and charts, automatically refreshed when the report runs again. This allows to create custom dashboards and more advanced visualizations of report data.

You can download and use Blitz Report free of charge for your first 30 reports.
The installation and implementation process usually takes less than 1 hour; you can refer to our installation and user guides for specific details.
If you would like to optimize your Oracle EBS implementation and or operational reporting you can visit www.enginatics.com to review great ideas and example usage in blog. Or why not try for yourself in our demo environment.
Useful Links
Blitz Report™ – World’s fastest data upload and reporting for Oracle EBS
Oracle Discoverer replacement – importing worksheets into Blitz Report™
Blitz Report™ Questions & Answers
Supply Chain Hub by Blitz Report™
© 2025 Enginatics