Results for “po_distributions_gt”

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

Overview

PO_DISTRIBUTIONS_GT is a global temporary table (GTT) owned by the PO schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its structure mirrors PO_DISTRIBUTIONS_ALL, the base table that stores the accounting distribution lines generated for purchase orders, releases, and their associated shipments. The table is documented in ETRM as "For Internal Use Only," and serves as a transient staging area for data evaluated during PO Approval Submission Checks. Rows inserted into a GTT are visible only to the session or transaction that created them and are purged automatically at transaction commit or session termination, which makes the object unsuitable for persistent reporting.

From a heuristic Data Vault modeling perspective, the FK metadata classifies this object as standalone, and the documented relationship set is thin (PO_RELEASES_ALL, MTL_KANBAN_CARDS, IGF_AW_AWARD_ALL). Where it is populated transiently, it behaves most plausibly as a satellite-like staging structure keyed by PO_DISTRIBUTION_ID, rather than as a durable hub or link. This classification is a modeling suggestion only; the table carries no business-key enforcement beyond its unique index.

Key Information Stored

The documented schema exposes 99 columns, of which the following are the most operationally significant:

• PO_DISTRIBUTION_ID — Surrogate primary key; also the single unique index (PO_DISTRIBUTIONS_GT_U1), making it the business-key candidate for this staging row.
• PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID — Foreign references that anchor the distribution to its parent document, line, and shipment.
• PO_RELEASE_ID — Links the distribution to a blanket release; documented FK to PO_RELEASES_ALL.
• SET_OF_BOOKS_ID, CODE_COMBINATION_ID — Accounting context: ledger and the GL account combination charged.
• QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_BILLED, QUANTITY_CANCELLED — Quantity lifecycle across ordering, receipt, invoicing, and cancellation.
• AMOUNT_ORDERED, AMOUNT_DELIVERED, AMOUNT_BILLED, AMOUNT_CANCELLED — Corresponding monetary measures.
• ENCUMBERED_FLAG, ENCUMBERED_AMOUNT, UNENCUMBERED_QUANTITY, UNENCUMBERED_AMOUNT — Funds-check state used during approval validation.
• DESTINATION_TYPE_CODE, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY — Inventory or expense destination attributes.
• REQ_DISTRIBUTION_ID, REQ_HEADER_REFERENCE_NUM, REQ_LINE_REFERENCE_NUM — Requisition lineage for the distribution.
• PROJECT_ID, TASK_ID, EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE — Project accounting context where applicable.
• ORG_ID — Multi-org operating unit discriminator.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID — Concurrent program audit trail for the producing process.
• KANBAN_CARD_ID, AWARD_ID — Documented FKs to MTL_KANBAN_CARDS and IGF_AW_AWARD_ALL respectively.

Common Use Cases and Queries

The principal consumer is the PO Approval Submission Check process, which materialises distributions for a document under review, validates encumbrance and funds status, and then discards the rows. Diagnostic queries must be issued from the same session that populated the table, because GTT contents are session-scoped.

• Inspecting active rows during a debugging session: SELECT po_distribution_id, po_header_id, quantity_ordered, encumbered_amount FROM po_distributions_gt WHERE po_header_id = :header_id;
• Summing encumbered versus unencumbered amounts for a document before approval.
• Confirming that every distribution in PO_DISTRIBUTIONS_ALL has a matching staging row (a row-count reconciliation by PO_DISTRIBUTION_ID).
• Reviewing the producing concurrent request via REQUEST_ID and PROGRAM_ID to trace which approval check populated the table.

Because the object is internal and transient, it should not be referenced by custom reports, interfaces, or conversions; equivalent persistent data should be sourced from PO_DISTRIBUTIONS_ALL.

Related Objects

• PO_DISTRIBUTIONS_ALL — Base table whose structure this GTT mirrors and the authoritative persistent source.
• PO_RELEASES_ALL — Referenced via PO_RELEASE_ID.
• MTL_KANBAN_CARDS — Referenced via KANBAN_CARD_ID.
• IGF_AW_AWARD_ALL — Referenced via AWARD_ID for grants/awards distributions.
• PO_HEADERS_ALL and PO_LINES_ALL — Parent documents and lines via PO_HEADER_ID and PO_LINE_ID.
• PO_LINE_LOCATIONS_ALL — Shipment detail via LINE_LOCATION_ID.
• GL_CODE_COMBINATIONS — Account validation via CODE_COMBINATION_ID.
• FND_CONCURRENT_REQUESTS — Traceability of the populating approval-check program.