AP Invoices with PO, Intercompany and SLA Details – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

AP Invoices with PO, Intercompany and SLA Details

Report 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

Oracle EBS Tables Used

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

Report Categories

Enginatics, R12 only

GL Account Distribution Analysis, CAC Receiving Value (Period-End), CAC Purchase Price Variance, GL Account Analysis (Distributions), AP Invoices with PO, Intercompany and SLA Details(GST), CAC Receiving Expense Value (Period-End)

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource Link
Excel Example Output None
Blitz Report™ XML Import AP_Invoices_with_PO_Intercompany_and_SLA_Details.xml
Full SQL on Enginatics www.enginatics.com/reports/ap-invoices-with-po-intercompany-and-sla-details/

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:

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

2. Technical Analysis

Core Tables and Views

The report navigates the complex P2P schema, primarily anchoring on Payables and linking outwards:

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.

Integration Points

3. Functional Capabilities

Parameters & Filtering

Performance & Optimization

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.

© 2026 Enginatics