Search Results total_prepays




Overview
Explore in AI Chat

Overview

PO_VENDORS_AP_V is an APPS-owned, VALID view in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment. It belongs to the Oracle Payables (AP) product family and exposes a consolidated supplier/vendor profile, combining core supplier master attributes with withholding tax configuration, pay-site counts, and prepayment balances. The view's central purpose is to present, in a single queryable structure, the information the Payables and Purchasing applications require when evaluating a supplier's payment posture for a given operating unit.

The view is functionally significant because it embeds a Multi-Org security predicate: the WHERE clause references MO_GLOBAL.CHECK_ACCESS(HR.ORGANIZATION_ID) = 'Y', meaning row visibility is automatically restricted to the operating units the session is authorized to access. For reporting and integration purposes this makes PO_VENDORS_AP_V a convenient, security-aware source for supplier-level extracts, BI Publisher data models, and interface programs that need both vendor attributes and live payment aggregates.

Because the view is defined with a UNION, it returns two categories of rows: supplier records drawn from AP_SUPPLIERS (carrying VENDOR_ID, vendor number, and full payment configuration) and party-level records from HZ_PARTIES where no AP supplier exists, for which VENDOR_ID and related supplier-only columns are returned as NULL. Consumers must therefore account for NULL VENDOR_ID when joining downstream.

Underlying Base Objects

The documented base objects referenced by the view are:

  • AP_SUPPLIERS (synonym) — the primary supplier master, aliased ASUP, supplying vendor number, 1099 data, VAT registration, hold flags, withholding tax and interest settings, and active date ranges.
  • HR_OPERATING_UNITS (view) — aliased HR, supplying the ORG_ID and the operating unit driving MO_GLOBAL access checking.
  • IBY_EXTERNAL_PAYEES_ALL (synonym) — aliased PAYEE, supplying payment function, exclusive payment flag, settlement priority, and bank charge bearer.
  • HZ_PARTIES (synonym) — aliased HZ, supplying the trading partner (party) name.
  • MO_GLOBAL (package) — provides CHECK_ACCESS for Multi-Org row filtering.
  • PO_VENDORS_AP_PKG (package) — provides GET_NUM_ACTIVE_PAY_SITES and GET_NUM_INACTIVE_PAY_SITES for pay-site counts.
  • AP_INVOICES_PKG (package) — provides GET_TOTAL_PREPAYS and GET_AVAILABLE_PREPAYS, the prepared prepayment aggregates.

Rather than storing data, PO_VENDORS_AP_V is a pure read construct: supplier facts are joined to party names on PARTY_ID, to external payees on PAYEE_PARTY_ID, and to operating units via the Multi-Org check. The two package-based functions execute per row, so query cost scales with supplier count.

Key Columns

The column sequence for the party-only UNION branch terminates before VENDOR_TYPE_LOOKUP_CODE, so those rows carry NULLs for all AP_SUPPLIER-derived columns.

Common Use Cases and Queries

The most frequent driver for this object is the search term "total_prepays": users want supplier prepayment exposure for reconciliation, cash forecasting, or supplier statement review. A representative query is:

  • SELECT vendor_number, trading_partner, org_id, total_prepays, available_prepays FROM po_vendors_ap_v WHERE total_prepays > 0 AND org_id = :p_org_id;
  • SELECT vendor_name, SUM(total_prepays - available_prepays) applied_amount FROM po_vendors_ap_v GROUP BY vendor_name; to derive applied prepayments.
  • SELECT vendor_id, vendor_number, enabled_flag, num_active_pay_sites FROM po_vendors_ap_v WHERE vendor_type_lookup_code = 'EMPLOYEE'; for employee-supplier analysis.

Because ORG_ID drives MO_GLOBAL.CHECK_ACCESS, queries return only accessible operating units; in multi-org reporting the ORG_ID predicate should be stated explicitly. Note that TOTAL_PREPAYS and AVAILABLE_PREPAYS are computed by function calls at runtime, so performance-sensitive extracts should filter aggressively (for example by ORG_ID or VENDOR_ID) before these columns are evaluated. The view is read-only and should not be used as an interface target.