Search Results po_distributions_ap2_v




Overview
Explore in AI Chat

Overview

PO_DISTRIBUTIONS_AP2_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Purchasing (PO) product family. It is a denormalized projection of purchase order distribution accounting data, purpose-built for Payables-facing and funds-check reporting where distribution, encumbrance, and accounting flexfield context must be presented together in a single queryable structure. The view carries the full complement of PO_DISTRIBUTIONS accounting columns, including AMOUNT_BILLED, ENCUMBERED_AMOUNT, ENCUMBERED_FLAG, ACCRUED_FLAG, ACCRUE_ON_RECEIPT_FLAG, GL_ENCUMBERED_DATE, GL_ENCUMBERED_PERIOD_NAME, and the DFF segment set (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15). Its distinguishing feature is a DECODE expression that resolves the effective accounting flexfield per row into a single CODE_COMBINATION_ID, rather than requiring the caller to interpret DESTINATION_TYPE_CODE and accrual flags themselves. This makes the view a convenient source for encumbrance and accrual reconciliation reports, particularly where users search on unencumbered_amount. Note that this column is not projected by the view text; the underlying PO_DISTRIBUTIONS table stores ENCUMBERED_AMOUNT, from which unencumbered amounts are typically derived by subtracting encumbered from the ordered or billed amount.

Underlying Base Objects

The view is defined over PO_DISTRIBUTIONS (referenced as a synonym), which supplies every projected column including the ROWID alias ROW_ID. The ETRM metadata additionally documents the following referenced objects: HR_ORG_UNITS_NO_JOIN, PER_PEOPLE_F, PA_PROJECTS_ALL, and PA_TASKS (synonyms or views), plus the packages HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY, and the HR_ALL_ORGANIZATION_UNITS_TL synonym. The join to HR_ORG_UNITS_NO_JOIN (aliased HOUT) supplies EXPENDITURE_ORGANIZATION from HOUT.NAME. The remaining HR and PA references support organization security, person name resolution, and project/task validation used by the view's parent logic. The result is a single row per purchase order distribution, preserving the transactional grain of PO_DISTRIBUTIONS while enriching it with organizational description.

Key Columns

  • CODE_COMBINATION_ID — derived via DECODE: for EXPENSE destinations with ACCRUE_ON_RECEIPT_FLAG = 'Y', the ACCRUAL_ACCOUNT_ID; for other EXPENSE rows, the base CODE_COMBINATION_ID; otherwise ACCRUAL_ACCOUNT_ID. This is the definitive accounting flexfield for reporting.
  • ENCUMBERED_AMOUNT / ENCUMBERED_FLAG — the amount and indicator of funds reservation against the distribution, central to funds-check and unencumbered balance reporting.
  • AMOUNT_BILLED — the cumulative invoiced value matched to the distribution, used alongside encumbered amounts to compute remaining obligations.
  • DESTINATION_TYPE_CODE, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY — describe where the goods or services are delivered (expense, inventory, shop floor).
  • GL_ENCUMBERED_DATE / GL_ENCUMBERED_PERIOD_NAME — the GL date and accounting period in which encumbrance was recorded.
  • EXPENDITURE_ORGANIZATION — organization name resolved from HR_ORG_UNITS_NO_JOIN for reporting by owning organization.
  • ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — descriptive flexfield context and segments carried forward from the distribution.

Common Use Cases and Queries

A frequent requirement is reconciling encumbered versus billed amounts to identify unencumbered balances per distribution. Because unencumbered_amount is not a stored column, analysts derive it from ENCUMBERED_AMOUNT in PO_DISTRIBUTIONS, filtered through this view for accounting context.

Sample query — encumbrance reconciliation by organization:

  • SELECT v.EXPENDITURE_ORGANIZATION, v.DISTRIBUTION_NUM, v.CODE_COMBINATION_ID, v.ENCUMBERED_AMOUNT, v.AMOUNT_BILLED, v.GL_ENCUMBERED_PERIOD_NAME FROM APPS.PO_DISTRIBUTIONS_AP2_V v WHERE v.ENCUMBERED_FLAG = 'Y' AND v.DESTINATION_TYPE_CODE = 'EXPENSE' AND v.GL_ENCUMBERED_PERIOD_NAME = :period ORDER BY v.EXPENDITURE_ORGANIZATION, v.DISTRIBUTION_NUM;

Sample query — accrued expense distributions by effective account:

  • SELECT v.CODE_COMBINATION_ID, v.ACCRUE_ON_RECEIPT_FLAG, SUM(v.ENCUMBERED_AMOUNT) ENC, SUM(v.AMOUNT_BILLED) BILLED FROM APPS.PO_DISTRIBUTIONS_AP2_V v WHERE v.DESTINATION_TYPE_CODE = 'EXPENSE' GROUP BY v.CODE_COMBINATION_ID, v.ACCRUE_ON_RECEIPT_FLAG HAVING SUM(v.ENCUMBERED_AMOUNT) > SUM(v.AMOUNT_BILLED);

The view is read-only and intended for inquiry; because it derives CODE_COMBINATION_ID through DECODE, always filter on DESTINATION_TYPE_CODE and the accrual flags when the business meaning of the account must be guaranteed.