Results for “po_req_distributions_all”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_REQ_DISTRIBUTIONS_ALL is the Purchasing (PO) application table that stores requisition distributions in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Each row represents the accounting, project, and funding distribution of a requisition line, defining how the requisitioned amount or quantity is charged across general ledger accounts, projects, tasks, expenditure types, and awards. The table is the requisition-side counterpart to the purchasing distributions maintained for purchase orders, and it plays a central role in encumbrance accounting, budgetary control, and project commitment tracking.

From a Data Vault modeling perspective, the mined foreign key structure classifies this object as satellite-leaning. It behaves primarily as a descriptive satellite attached to requisition line and requisition header hubs and links, though it also carries several foreign key references that make it a natural dependent of the PO_REQUISITION_LINES_ALL hub via REQUISITION_LINE_ID.

Key Information Stored

The table is defined in the PO schema with 86 documented columns. The surrogate primary key is DISTRIBUTION_ID, enforced by the PO_REQ_DISTRIBUTIONS_PK constraint; a unique index, PO_REQ_DISTRIBUTIONS_U1, provides a business-key candidate on the same column. The most significant columns include:

Common Use Cases and Queries

Requisitions distributions are commonly queried for encumbrance reconciliation, project commitment reporting, and budgetary control analysis. A typical join retrieves distributions with their charge accounts and requisition lines:

  • Joining PO_REQ_DISTRIBUTIONS_ALL to PO_REQUISITION_LINES_ALL on REQUISITION_LINE_ID to report requisition detail by distribution.
  • Joining to GL_CODE_COMBINATIONS on CODE_COMBINATION_ID to obtain the concatenated accounting flexfield for reconciliation and encumbrance reports.
  • Filtering on ENCUMBERED_FLAG or GL_ENCUMBERED_PERIOD_NAME to identify distributions not yet encumbered or those posted in a specific period.
  • Using PROJECT_ID, TASK_ID, and EXPENDITURE_TYPE to report project commitments and to reconcile against PA_BC_COMMITMENTS_ALL, which references this table through PRL_DISTRIBUTION_ID.
  • Querying by ORG_ID to isolate distributions for a specific operating unit.

Sample SQL pattern:

SELECT d.distribution_id, d.requisition_line_id, d.req_line_amount, g.concatenated_segments FROM po.po_req_distributions_all d, gl.gl_code_combinations_kfv g WHERE d.code_combination_id = g.code_combination_id AND d.encumbered_flag = 'Y' AND d.org_id = :org_id;

Related Objects

The table is tightly integrated with requisition, purchasing, and receiving objects. The most significant related tables include:

  • PO_REQUISITION_LINES_ALL — Parent table joined on REQUISITION_LINE_ID.
  • GL_CODE_COMBINATIONS — Accounting flexfield referenced by CODE_COMBINATION_ID, BUDGET_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, and VARIANCE_ACCOUNT_ID.
  • GL_SETS_OF_BOOKS — Ledger reference via SET_OF_BOOKS_ID.
  • PA_PROJECTS_ALL, PA_TASKS, PA_EXPENDITURE_TYPES — Project charging references.
  • PO_DISTRIBUTIONS_ALL — Purchase order distributions referencing REQ_DISTRIBUTION_ID.
  • RCV_SHIPMENT_LINES and RCV_TRANSACTIONS — Receiving records referencing REQ_DISTRIBUTION_ID.
  • PA_BC_COMMITMENTS_ALL — Project commitments referencing PRL_DISTRIBUTION_ID.
  • GMS_AWARD_DISTRIBUTIONS — Award distributions referencing DISTRIBUTION_ID.