Search Results amt_closed

Overview

PO.PO_ENCUMBRANCE_GT is a global temporary table in the Purchasing (PO) schema of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. It serves as a transient staging and processing structure used by the encumbrance accounting engine to accumulate, evaluate, and post purchasing commitment entries to General Ledger. Because it is defined with a data duration of SYS$TRANSACTION, the rows it holds are private to the session that inserted them and are automatically purged at the conclusion of the transaction. This design allows concurrent users to run encumbrance processing, funds checking, or period-end commitment adjustment routines simultaneously without contention or cross-session visibility of partially processed data.

From a dimensional modeling perspective, the table exhibits the characteristics of a standalone or transient staging structure rather than a durable entity; there are no enforceable foreign keys to persistent transactional tables in a way that would anchor it as a hub, link, or satellite. It should therefore be treated as an operational work table whose contents mirror a projection of purchasing activity at a specific point in the encumbrance generation cycle, rather than as a source of record.

Key Information Stored

The table carries 117 documented columns, but only a subset are central to its function. Its columns fall into document identifiers, accounting identifiers, monetary and quantity measures, and processing flags.

• Document identifiers: HEADER_ID, LINE_ID, LINE_LOCATION_ID, DISTRIBUTION_ID, and PO_RELEASE_ID tie each staging row back to the originating purchase order, release, line, shipment, and distribution.
• Cross-reference business keys: SEGMENT1 (the PO number), LINE_NUM, SHIPMENT_NUM, and DISTRIBUTION_NUM provide human-readable business identifiers for the same document chain.
• Accounting keys: CODE_COMBINATION_ID, BUDGET_ACCOUNT_ID, ENCUMBRANCE_TYPE_ID, and BUDGET_ACCOUNT_ID define the GL charge account and commitment classification. GL_ENCUMBERED_DATE and PERIOD_NAME/PERIOD_YEAR/PERIOD_NUM establish the accounting period.
• Monetary amounts: AMOUNT_TO_ENCUMBER, UNENCUMBERED_AMOUNT, ENCUMBERED_AMOUNT, AMOUNT_ORDERED, AMOUNT_DELIVERED, AMOUNT_BILLED, AMOUNT_CANCELLED, and the derived AMT_OPEN, AMT_ORDERED, AMT_CLOSED, and ENCUMBERED_AMOUNT_CHANGE track the commitment lifecycle.
• Quantity measures: QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_BILLED, QUANTITY_CANCELLED, and the projected QTY_ORDERED, QTY_CLOSED, QTY_OPEN.
• Accounting pairs: ENTERED_DR / ENTERED_CR and ACCOUNTED_DR / ACCOUNTED_CR carry the double-entry amounts in entered and functional currency, with CURRENCY_CODE and RATE providing conversion context.
• Processing flags: CANCEL_FLAG, CLOSED_CODE, ENCUMBERED_FLAG, SEND_TO_GL_FLAG, GL_STATUS_CODE, GL_RESULT_CODE, and UPDATE_ENCUMBERED_AMOUNT_FLAG direct downstream GL posting and error handling.

Four non-unique indexes are documented — PO_ENCUMBRANCE_GT_N1 on DISTRIBUTION_ID, N2 on SEQUENCE_NUM, N3 on ORIGIN_SEQUENCE_NUM, N4 on REFERENCE15, and N5 on REQ_DISTRIBUTION_ID — supporting retrieval by distribution, request sequencing, and requisition cross-reference. No unique index or declared primary key is documented, consistent with its role as a temporary accumulator.

Common Use Cases and Queries

The dominant use case is the encumbrance accounting process, which inserts purchasing distributions into the table, computes commitment amounts, and then drives GL journal creation. A frequent requirement is to inspect open commitment balances before period close:

• Query open amount by PO distribution: SELECT header_id, distribution_id, amt_open, amt_ordered, amt_closed FROM po_encumbrance_gt WHERE amt_open <> 0;
• Trace GL posting failures: SELECT distribution_id, gl_status_code, gl_result_code, result_text FROM po_encumbrance_gt WHERE gl_status_code = 'E';
• Reconcile entered versus accounted amounts: SELECT currency_code, SUM(entered_dr - entered_cr), SUM(accounted_dr - accounted_cr) FROM po_encumbrance_gt GROUP BY currency_code;
• Cross-reference a requisition to its encumbrance: SELECT * FROM po_encumbrance_gt WHERE req_distribution_id = :dist_id;

Because rows vanish at transaction end, queries are typically embedded inside the concurrent program or run immediately after the initiating session commits.

Related Objects

The documented foreign key relationships identify the most significant dependencies:

• PO.PO_RELEASES_ALL — joined via PO_RELEASE_ID for blanket release distributions.
• PO.PO_LINE_TYPES_B — joined via LINE_TYPE_ID to classify the purchase line.
• GL.GL_ENCUMBRANCE_TYPES — joined via ENCUMBRANCE_TYPE_ID to determine the commitment type.
• PO.PO_DISTRIBUTIONS_ALL — the persistent source of distribution rows staged into this table.
• PO.PO_HEADERS_ALL and PO.PO_LINES_ALL — linked through HEADER_ID and LINE_ID for document context.
• GL_JE_BATCHES / GL_JE_HEADERS / GL_JE_LINES — destination objects for the journal entries produced from these staged rows.
• GL_CODE_COMBINATIONS — joined via CODE_COMBINATION_ID to resolve the accounting flexfield.

The table is populated and consumed by the Purchase Order Encumbrance and Funds Checker concurrent programs rather than by a published PL/SQL API, and it should be regarded strictly as internal to the encumbrance subsystem.