Search Results po_bc_distributions




Overview
Explore in AI Chat

Overview

PO_BC_DISTRIBUTIONS is a core accounting distribution table in the Oracle Purchasing (PO) module, owned by the PO schema. It stores the accounting distribution lines that the Purchasing application generates for encumbrance, accrual, and budgetary control processing. According to Oracle's Enterprise Transaction Repository Model (ETRM) documentation, the table contains values for most of the sources used as Transaction Objects in Subledger Accounting (XLA) for PO, and it serves as one of the principal tables from which those Transaction Objects derive values for core PO sources.

In Oracle EBS 12.1.1 and 12.2.2, the table is closely tied to the Subledger Accounting architecture introduced in R12, where purchasing events such as requisition, purchase order, receipt, and invoice distributions are captured and later accounted. PO_BC_DISTRIBUTIONS supports this flow by holding distribution-level accounting attributes—amounts, currency, code combination, and event context—that feed downstream journal creation.

Based on the FK structure mined from the metadata, which shows references to PO_RELEASES_ALL and GL_ENCUMBRANCE_TYPES but no incoming dependencies, the table is heuristically classified as a standalone object in a Data Vault sense rather than a strict hub, link, or satellite. This classification should be treated as a modeling suggestion only, as its role is transactional rather than a clean dimensional or hub construct.

Key Information Stored

The table comprises 70 documented columns in ETRM 12.2.2. The most functionally significant include:

The documented FK model identifies PO_RELEASE_ID and ENCUMBRANCE_TYPE_ID as foreign key columns. No unique index is documented in the excerpt, so DISTRIBUTION_ID is best treated as the surrogate primary key candidate.

Common Use Cases and Queries

Typical uses of PO_BC_DISTRIBUTIONS include reconciling purchasing accounting entries, tracing XLA events back to distributions, validating encumbrance balances, and reporting on project-related purchasing expenditure.

  • Joining to PO_RELEASES_ALL on PO_RELEASE_ID to report release-level distributions.
  • Joining to GL_ENCUMBRANCE_TYPES on ENCUMBRANCE_TYPE_ID to analyze encumbrance activity.
  • Filtering by AE_EVENT_ID or PACKET_ID to reconstruct the accounting event flow.
  • Aggregating ACCOUNTED_AMT by LEDGER_ID and GL_DATE for period-close reporting.
  • Linking to PA_PROJECT_ID for project cost and award reporting.

A representative query filters on GL_DATE, LEDGER_ID, and CURRENCY_CODE to extract distributions for a given accounting period.

Related Objects