Search Results po_distributions_ap_v




Overview
Explore in AI Chat

Overview

PO_DISTRIBUTIONS_AP_V is an Oracle E-Business Suite database view owned by the APPS schema and classified under the Purchasing (PO) product module. It presents purchase order distribution data in a form tailored for Payables-side consumption and reporting. The view carries a VALID status in the EBS data dictionary and is documented in ETRM for releases 12.1.1 and 12.2.2. Its description is simply "Purchase order distributions," reflecting its role as a filtered, derived projection of the base distribution records rather than a new physical entity.

In Oracle EBS reporting and integration, the view serves as a stable, read-only interface that exposes the accrual and charge account logic required by subledger and GL-facing processes. Because the AP-side accounting for a distribution depends on whether the destination is an expense and whether accrual on receipt is enabled, the view centralizes that decision logic so that downstream reports, interfaces, and inquiry forms do not need to replicate it. This makes the object valuable in both functional inquiry (purchase order distribution review) and technical integration (feeds into payables, encumbrance, and reconciliation extracts).

Underlying Base Objects

The documented view metadata lists PO_DISTRIBUTIONS (SYNONYM) as the referenced base object. In practice, PO_DISTRIBUTIONS_AP_V is defined with a straightforward SELECT over the PO_DISTRIBUTIONS table, aliased as POD in the view text, projecting a defined column list with a small number of DECODE-based derivations. The view does not introduce joins to other tables in the documented definition; all columns are drawn from the single base table, and the alias POD is preserved in the view text. As a synonym-backed view, the view is referenced as APPS.PO_DISTRIBUTIONS_AP_V, with the synonym resolving to the PO_DISTRIBUTIONS base structure. The view therefore inherits the grain of PO_DISTRIBUTIONS: one row per purchase order distribution, keyed by PO_DISTRIBUTION_ID.

Key Columns

The view exposes the full distribution identifier and audit columns (PO_DISTRIBUTION_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), the owning purchase document hierarchy (PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, PO_RELEASE_ID), and the accounting context (SET_OF_BOOKS_ID, CODE_COMBINATION_ID, BUDGET_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, VARIANCE_ACCOUNT_ID). Quantity and amount measures include QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_BILLED, QUANTITY_CANCELLED, AMOUNT_BILLED, ENCUMBERED_AMOUNT, UNENCUMBERED_QUANTITY, UNENCUMBERED_AMOUNT, and the encumbrance/cancellation status flags (ENCUMBERED_FLAG, ACCRUED_FLAG, GL_ENCUMBERED_DATE, GL_ENCUMBERED_PERIOD_NAME, GL_CANCELLED_DATE).

Two derived expressions distinguish this view. First, the account column is computed as DECODE(DESTINATION_TYPE_CODE, 'EXPENSE', DECODE(ACCRUE_ON_RECEIPT_FLAG, 'Y', ACCRUAL_ACCOUNT_ID, CODE_COMBINATION_ID), ACCRUAL_ACCOUNT_ID) — selecting the accrual account when accrual on receipt is active for expense destinations, the code combination otherwise, and the accrual account for non-expense destinations. Second, an accrual/encumbrance indicator is computed as DECODE(PREVENT_ENCUMBRANCE_FLAG, 'Y', 'N', DECODE(ACCRUE_ON_RECEIPT_FLAG, 'Y', 'N', 'Y')) — suppressing accrual where encumbrance prevention applies and where accrual on receipt is active. Request/reference columns (REQ_HEADER_REFERENCE_NUM, REQ_LINE_REFERENCE_NUM, REQ_DISTRIBUTION_ID, SOURCE_DISTRIBUTION_ID, DISTRIBUTION_NUM) support reconciliation, while DESTINATION_TYPE_CODE, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY and the WIP/BOM columns support destination analysis. Descriptive flexfield columns ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY, GOVERNMENT_CONTEXT, USSGL_TR and the concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) are also projected.

Common Use Cases and Queries

Typical scenarios include reconciling purchase order accruals to Payables invoices, reporting encumbered versus unencumbered balances by distribution, and auditing the account derivation for expense versus inventory destinations. A representative query follows:

  • SELECT pod.po_distribution_id, pod.po_header_id, pod.po_line_id, pod.destination_type_code, pod.quantity_ordered, pod.quantity_billed, pod.amount_billed FROM apps.po_distributions_ap_v pod WHERE pod.po_header_id = :p_header_id;
  • SELECT pod.code_combination_id, pod.accrual_account_id, pod.encumbered_flag, pod.encumbered_amount, pod.unencumbered_amount FROM apps.po_distributions_ap_v pod WHERE pod.set_of_books_id = :p_sob AND pod.encumbered_flag = 'Y';
  • SELECT pod.distribution_num, pod.req_header_reference_num, pod.req_line_reference_num, pod.quantity_billed FROM apps.po_distributions_ap_v pod WHERE pod.req_header_reference_num IS NOT NULL;

Because the view retains the base distribution grain and preserves PO_DISTRIBUTION_ID, its results can be joined back to PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL on the corresponding identifier columns. All queries should predicate on SET_OF_BOOKS_ID or PO_HEADER_ID to avoid full-table scans on the underlying PO_DISTRIBUTIONS synonym.