Search Results cst_reconciliation_summary




The PO_DISTRIBUTIONS_ALL table is a critical entity in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, serving as the foundation for procurement and financial distribution tracking within the Purchasing module. This table stores detailed distribution-level information for purchase orders (POs), requisitions, and blanket agreements, linking procurement transactions to accounting entries in the General Ledger (GL). Below is a detailed analysis of its structure, purpose, key columns, and integration points.

Purpose and Functional Overview

The PO_DISTRIBUTIONS_ALL table captures financial and operational data for each distribution line associated with a PO document. It enables:
  1. Cost Allocation: Distributes PO line amounts across multiple accounts, projects, or tasks.
  2. Budgetary Control: Tracks encumbrances and expenditures for funds checking.
  3. GL Integration: Generates accounting entries via the Create Accounting process.
  4. Multi-Org Support: Stores data for all operating units (indicated by ORG_ID).

Key Columns and Relationships

Column Description Related Tables
PO_DISTRIBUTION_ID Primary key, unique identifier -
PO_HEADER_ID Links to PO_HEADERS_ALL PO_HEADERS_ALL
PO_LINE_ID Links to PO_LINES_ALL PO_LINES_ALL
QUANTITY_ORDERED Ordered quantity at distribution level -
AMOUNT_ORDERED Distribution amount in transaction currency -
DESTINATION_TYPE_CODE Indicates expense/inventory/asset etc. -
CODE_COMBINATION_ID GL account (links to GL_CODE_COMBINATIONS) GL_CODE_COMBINATIONS
ENCUMBERED_FLAG Indicates if funds are reserved -

Integration Points

1. Financial Modules: Distributes amounts to GL via Subledger Accounting (XLA tables).
2. Projects: Links to PA_EXPENDITURE_ITEMS_ALL for project costing.
3. Inventory: Tracks distributions for inventory receipts via RCV_TRANSACTIONS.
4. Assets: Asset distributions flow to FA tables during capitalization.

Technical Considerations

  • Multi-Org Access Control (MOAC): Queries must filter by ORG_ID.
  • Indexes: Key indexes exist on PO_HEADER_ID, PO_LINE_ID, and CODE_COMBINATION_ID.
  • Audit Columns: Includes CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Common Use Cases

1. Custom Reporting: Extracting detailed PO spend by account/department.
2. Data Fixes: Correcting misaligned distributions before GL posting.
3. Interface Development: Feeding PO data to external systems.
4. Audit Trails: Tracing historical changes to distributions. This table's centrality in procurement-to-pay processes makes it indispensable for customization, reporting, and troubleshooting in Oracle EBS implementations.