Skip to the content.

AP Supplier Statement – Oracle EBS SQL Report

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

Overview

Application: Payables Source: Supplier Statement Short Name: APTPSTMT DB package: AP_TP_STMT_PKG

Report Parameters

Reporting Level, Reporting Context, GL Date From, GL Date To, Document Date From, Document Date To, Supplier Name From, Supplier Name To, Currency, Pay Group, Vendor Type, Include Zero Balance Suppliers, Include Unvalidated Transactions, Include Unapproved Transaction, Accounted Transactions, Report Level, Summarization Level

Oracle EBS Tables Used

gl_code_combinations_kfv, ap_invoices, ap_suppliers, ap_supplier_sites_all, hr_operating_units, gl_periods, gl_ledgers, ap_lookup_codes, ap_invoice_payments, ap_checks

Report Categories

Enginatics, R12 only

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 AP Supplier Statement 28-Apr-2021 200101.xlsx
Blitz Report™ XML Import AP_Supplier_Statement.xml
Full SQL on Enginatics www.enginatics.com/reports/ap-supplier-statement/

Case Study & Technical Analysis: AP Supplier Statement

1. Executive Summary

Business Problem

Supplier relationships are often strained by communication gaps regarding payment status. Vendors frequently contact Accounts Payable asking, “Have you received Invoice X?”, “When will you pay Invoice Y?”, or “Why was my payment short?”. Answering these queries manually is time-consuming and inefficient.

Solution Overview

The AP Supplier Statement is a comprehensive, external-facing document designed to be sent directly to vendors. It provides a complete history of the account, including:

Key Benefits

2. Technical Analysis

Core Tables and Views

SQL Logic and Data Flow

The report typically uses a UNION approach to combine different transaction types into a single chronological list:

  1. Invoices: Selects standard invoices, debit memos.
  2. Payments: Selects payments, linking them to the invoices they paid.
  3. Prepayments: Identifies available prepayments.
  4. Balance Calculation: Uses analytic functions (e.g., SUM() OVER (PARTITION BY Vendor ORDER BY Date)) to calculate a running balance.

Integration Points

3. Functional Capabilities

Parameters & Filtering

Performance & Optimization

4. FAQ

Q: Can this report show “In Process” invoices? A: Yes, by checking “Include Unvalidated Transactions,” you can show vendors that you have received their invoice even if it’s on hold or pending approval.

Q: Does it handle “Cross Currency” payments? A: Yes, the report logic typically handles cases where the invoice is in EUR but paid in USD, showing the relevant amounts.

Q: How is the “Running Balance” calculated? A: It takes the opening balance (sum of all transactions prior to the “From Date”) and adds/subtracts subsequent invoices and payments chronologically.


© 2026 Enginatics