Search Results encumbered_amount_change

Overview

PO.PO_ENCUMBRANCE_GT1 is a global temporary table (GTT) in the Oracle E-Business Suite Purchasing (PO) schema. It is defined with a data duration of SYS$TRANSACTION, meaning that rows are visible only to the session that inserts them and are purged automatically at transaction commit or rollback. This design makes the table a session-scoped staging area used by Purchasing encumbrance and funds-checking programs rather than a persistent transactional store.

Its role is to hold intermediate encumbrance calculations for purchase orders, releases, and requisition distributions before those amounts are validated, adjusted, and ultimately transferred to General Ledger (GL) or Project Accounting via subledger accounting. The table carries a wide column set (123 documented columns) covering header/line identity, accounting flexfield references, quantity and amount buckets, currency attributes, project/task context, and GL posting status codes.

Under a heuristic Data Vault classification, the object behaves as a transient staging construct rather than a conformed hub, link, or satellite. It carries both descriptive attributes and foreign-key style references, but because its rows are session-scoped and non-durable, it is best modeled as a working set that feeds persistent hubs and links rather than as a durable DV entity.

Key Information Stored

The table's most significant columns fall into several functional groups. Identity and lineage columns include DISTRIBUTION_ID, which is indexed by PO_ENCUMBRANCE_GT1_N1 and serves as a primary surrogate-style key for the row; LINE_ID, LINE_LOCATION_ID, HEADER_ID, and PO_RELEASE_ID which anchor the row to its parent purchasing document hierarchy; and SOURCE_DISTRIBUTION_ID, REQ_DISTRIBUTION_ID, and FROM_HEADER_ID which preserve the originating requisition or prior document.

Business-key candidates visible through unique and non-unique indexes include DISTRIBUTION_ID, SEQUENCE_NUM (index PO_ENCUMBRANCE_GT1_N2), ORIGIN_SEQUENCE_NUM (PO_ENCUMBRANCE_GT1_N3), and REQ_DISTRIBUTION_ID (PO_ENCUMBRANCE_GT1_N5). These index columns plus REFERENCE15 (PO_ENCUMBERANCE_GT1_N4) support program-level lookups and multi-pass encumbrance processing.

Amount and quantity columns hold the encumbrance math: AMOUNT_TO_ENCUMBER, ENCUMBERED_AMOUNT, UNENCUMBERED_AMOUNT, AMOUNT_ORDERED, AMOUNT_DELIVERED, AMOUNT_BILLED, AMOUNT_CANCELLED, alongside the parallel quantity buckets (QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_BILLED, QUANTITY_CANCELLED, QUANTITY_ON_LINE). Control flags such as ENCUMBERED_FLAG, ENCUMBRANCE_REQUIRED_FLAG, PREVENT_ENCUMBRANCE_FLAG, and the user-referenced UPDATE_ENCUMBERED_AMOUNT_FLAG govern whether and how encumbered amounts are recalculated. GL-facing fields include GL_ENCUMBERED_DATE, GL_STATUS_CODE, GL_RESULT_CODE, CODE_COMBINATION_ID, ENCUMBRANCE_TYPE_ID, PERIOD_NAME, and the debit/credit distribution of ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, and ACCOUNTED_CR.

Common Use Cases and Queries

Because the table is a GTT, all queries must run within the same session that populated it. Typical usage appears inside the Oracle Purchasing encumbrance and funds-check processing, where populated rows are inspected before posting. Diagnostic SQL commonly joins DISTRIBUTION_ID back to its origin distribution and filters on the controlling flags.

• Detecting rows flagged for recalculation: SELECT DISTRIBUTION_ID, ENCUMBERED_AMOUNT, AMOUNT_TO_ENCUMBER FROM PO.PO_ENCUMBRANCE_GT1 WHERE UPDATE_ENCUMBERED_AMOUNT_FLAG = 'Y';
• Reconciling amount versus quantity buckets, or summing ENCUMBERED_AMOUNT by ENCUMBRANCE_TYPE_ID.
• Reviewing GL posting outcomes by selecting GL_STATUS_CODE, GL_RESULT_CODE, CODE_COMBINATION_ID, and PERIOD_NAME for a given distribution.
• Identifying encumbrance-relevant rows using ENCUMBRANCE_REQUIRED_FLAG and PREVENT_ENCUMBRANCE_FLAG before promoting changes.

Reporting tools that require durable encumbrance history should query the permanent encumbrance tables rather than this GTT, because session data is destroyed at transaction completion.

Related Objects

The documented foreign keys identify three principal parent tables. PO_RELEASE_ID references PO_RELEASES_ALL, tying rows to release documents. LINE_TYPE_ID references PO_LINE_TYPES_B, categorizing the purchasing line. ENCUMBERANCE_TYPE_ID references GL_ENCUMBRANCE_TYPES, defining the GL encumbrance category used for posting.

Other significant related objects include the Purchasing line and distribution tables (PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL) referenced via LINE_ID, LINE_LOCATION_ID, and DISTRIBUTION_ID, and requisition distributions via REQ_DISTRIBUTION_ID. General Ledger interaction occurs through CODE_COMBINATION_ID, ENCUMBRANCE_TYPE_ID, and the GL posting status columns, while project context is carried through PROJECT_ID, TASK_ID, AWARD_NUM, and EXPENDITURE_TYPE. These relationships position PO_ENCUMBRANCE_GT1 as the bridge between Purchasing document distributions and General Ledger encumbrance accounting.