Search Results po_distributions_trx_v




Overview
Explore in AI Chat

Overview

PO_DISTRIBUTIONS_TRX_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema within the Purchasing (PO) module. It is catalogued in ETRM with a status of VALID and is documented as a "Requisition Distribution View." Its primary purpose is to expose purchasing distribution transaction data in a form suitable for reporting, inquiry, and integration. Because the object is a view rather than a base table, it provides a read-only, denormalized projection of distribution-level purchasing activity, allowing reporting tools, concurrent programs, and external integrations to retrieve distribution, encumbrance, accounting, and receiving-related attributes without directly querying the underlying transactional tables. The view is relevant across both EBS 12.1.1 and 12.2.2 releases, where the Purchasing distributions model remains largely consistent.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, PO_DISTRIBUTIONS_TRX_V references the following base objects: PO_CLM_INTG_GRP (a PACKAGE), PO_DISTRIBUTIONS (a SYNONYM), and PO_LINES_TRX_V (a VIEW). The central source of the columns is the PO_DISTRIBUTIONS synonym, which resolves to the core PO_DISTRIBUTIONS_ALL transactional table holding one row per purchase order distribution. The view text selects the full set of distribution attributes (prefixed POD.) directly from this object, anchoring the view to the distribution grain. PO_LINES_TRX_V is referenced as an additional view, typically to supply or join line-level context, while PO_CLM_INTG_GRP is a Purchasing package involved in the integration or lookup logic layered into the view. The relationship is therefore one of projection and enrichment: the view presents distribution rows from PO_DISTRIBUTIONS and augments them through references to the line view and package logic.

Key Columns

The view exposes the complete column set of PO_DISTRIBUTIONS. Key identifiers include PO_DISTRIBUTION_ID (primary key of the distribution), PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, and PO_RELEASE_ID, which collectively locate the distribution within the purchasing document hierarchy. Quantity and amount tracking is provided by QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_BILLED, QUANTITY_CANCELLED, AMOUNT_BILLED, and UNENCUMBERED_QUANTITY/AMOUNT. Accounting and budgeting columns include CODE_COMBINATION_ID (the charge account), SET_OF_BOOKS_ID, BUDGET_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, and VARIANCE_ACCOUNT_ID. Encumbrance-related fields such as ENCUMBERED_FLAG, ENCUMBERED_AMOUNT, GL_ENCUMBERED_DATE, and GL_ENCUMBERED_PERIOD_NAME support funds control reporting. Destination and project data are captured through DESTINATION_TYPE_CODE, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY, PROJECT_ID, TASK_ID, and EXPENDITURE_TYPE. Requisition linkage is available via REQ_HEADER_REFERENCE_NUM, REQ_LINE_REFERENCE_NUM, and REQ_DISTRIBUTION_ID. Finally, the fifteen ATTRIBUTE columns and standard WHO/audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) provide extensibility and traceability.

Common Use Cases and Queries

PO_DISTRIBUTIONS_TRX_V is commonly used for distribution-level spend analysis, encumbrance reconciliation, requisition-to-PO traceability, and project/cost reporting. A typical query joins the view to PO_HEADERS_ALL and PO_LINES_ALL through the exposed foreign keys:

  • Distribution detail for a purchase order line: SELECT po_distribution_id, quantity_ordered, quantity_billed, code_combination_id FROM po_distributions_trx_v WHERE po_line_id = :line_id;
  • Encumbrance reporting by period: SELECT gl_encumbered_period_name, SUM(encumbered_amount) FROM po_distributions_trx_v WHERE encumbered_flag = 'Y' GROUP BY gl_encumbered_period_name;
  • Requisition traceability: SELECT req_header_reference_num, req_line_reference_num, po_header_id FROM po_distributions_trx_v WHERE req_distribution_id IS NOT NULL;
  • Project and task expenditure analysis: SELECT project_id, task_id, expenditure_type, SUM(amount_billed) FROM po_distributions_trx_v WHERE project_id IS NOT NULL GROUP BY project_id, task_id, expenditure_type;

These patterns support reporting views and extracts that require granular purchasing distribution data across the documented columns.