Search Results po_req_distributions_all




Overview
Explore in AI Chat

Overview

The PO_REQ_DISTRIBUTIONS_ALL table is a core transactional entity within Oracle E-Business Suite Purchasing (PO) module. It stores the detailed accounting and project-based distribution records for requisition lines. Each requisition line can be split into one or more distributions, enabling the allocation of its total quantity and cost across multiple general ledger accounts, projects, tasks, and awards. This table is fundamental for financial control, budgetary tracking, and project accounting integration. Its multi-org design, indicated by the "_ALL" suffix, means it stores data for all operating units, with access typically controlled by a MOAC (Multi-Org Access Control) security profile.

Key Information Stored

The table's primary key is DISTRIBUTION_ID, which uniquely identifies each distribution record. Critical foreign key columns link the distribution to its parent requisition line (REQUISITION_LINE_ID) and define its financial and project context. These include SET_OF_BOOKS_ID for the ledger, CODE_COMBINATION_ID for the primary charge account, and dedicated account columns for BUDGET_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, and VARIANCE_ACCOUNT_ID. For project-related requisitions, key columns are PROJECT_ID, TASK_ID, and EXPENDITURE_TYPE. The table also holds the distributed QUANTITY and REQUESTED_AMOUNT. The presence of specific account IDs and project fields is contingent on the setup of the requisitioning business unit and the item being requested.

Common Use Cases and Queries

This table is central to requisition reporting, account analysis, and audit trails. Common operational and reporting queries involve joining to PO_REQUISITION_LINES_ALL and PO_REQUISITION_HEADERS_ALL to analyze requisition spending by account, department, or project. A typical pattern is to trace the financial impact of a requisition from its distributions through to the resulting purchase order distributions (via REQ_DISTRIBUTION_ID) and eventual invoice and receiving transactions. Sample SQL often aggregates requested amounts by general ledger segment from the associated GL_CODE_COMBINATIONS table. For project-centric reporting, queries join to PA_PROJECTS_ALL and PA_TASKS. The table is also critical for interfaces, as evidenced by its relationship with PO_REQUISITIONS_INTERFACE_ALL and RCV_TRANSACTIONS_INTERFACE.

Related Objects

Based on the documented foreign key relationships, PO_REQ_DISTRIBUTIONS_ALL has extensive integration across EBS modules:

  • PO_REQUISITION_LINES_ALL: Primary parent table, joined via REQUISITION_LINE_ID.
  • GL_CODE_COMBINATIONS: Joined for the charge (CODE_COMBINATION_ID), budget (BUDGET_ACCOUNT_ID), accrual (ACCRUAL_ACCOUNT_ID), and variance (VARIANCE_ACCOUNT_ID) accounts.
  • GL_SETS_OF_BOOKS: Joined via SET_OF_BOOKS_ID.
  • Project Accounting (PA): Joined to PA_PROJECTS_ALL (PROJECT_ID), PA_TASKS (TASK_ID), and PA_EXPENDITURE_TYPES (EXPENDITURE_TYPE).
  • Purchasing Downstream: Source for PO_DISTRIBUTIONS_ALL (REQ_DISTRIBUTION_ID) when a requisition is converted to a purchase order, and for archival in PO_DISTRIBUTIONS_ARCHIVE_ALL.
  • Receiving (RCV): Referenced by RCV_SHIPMENT_LINES, RCV_TRANSACTIONS, and RCV_TRANSACTIONS_INTERFACE via REQ_DISTRIBUTION_ID for matching receipts to requisitions.
  • Grants Accounting (GMS): Linked to GMS_AWARD_DISTRIBUTIONS (DISTRIBUTION_ID).
  • Project Billing: Referenced by PA_BC_COMMITMENTS_ALL (PRL_DISTRIBUTION_ID).