Search Results current_funds_available

Overview

APPS.PSA_BC_RESULTS_GT is a global temporary table within the Oracle E-Business Suite Applications schema, registered under FND Design Data as PSA.PSA_BC_RESULTS_GT and holding VALID status across ETRM 12.1.1 and 12.2.2. It functions as the transient results staging area for the Budgetary Control (BC) engine, which is the component of the Funds Check and Funds Reservation architecture that evaluates transactions against control budgets and appropriations.

Structurally, the object is a global temporary table with a data duration of SYS$TRANSACTION. Each session sees only the rows it inserts, and those rows are purged automatically at transaction commit or rollback. Storage parameters are PCT Free 10 and PCT Used 40. Because the table holds intermediate, session-private output, it is never a system of record.

From a data-vault modeling perspective, the metadata's heuristic classification is standalone, meaning the object is not proposed as a hub, link, or satellite. That classification is consistent with its role as a technical work table rather than a persistent business entity. Although a foreign key is documented from ROW_ID to CS_SYSTEMS_ALL_B_TEMP, this reflects a temporary join key rather than a durable warehouse relationship.

The object is the direct carrier of the funds_check_status result. Column FUNDS_CHECK_STATUS holds the descriptive outcome string (up to 80 characters) and FUNDS_CHECK_STATUS_CODE holds the corresponding coded value, populated for every evaluated distribution line.

Key Information Stored

The table exposes 104 documented columns, of which the most operationally significant are:

• FUNDS_CHECK_STATUS_CODE / FUNDS_CHECK_STATUS — the coded and descriptive result of the funds check, the primary search term for this object.
• EFFECTIVE_STATUS — the status ultimately applied after boundary and tolerance logic.
• FUNDS_CHECK_LEVEL_CODE / FUNDS_CHECK_LEVEL_MEANING — the level at which the check was performed (for example, absolute, advisory, or track).
• BOUNDARY_CODE / BOUNDARY — indicates whether the transaction is within or breaches the control boundary.
• RESULT_CODE / RESULT_MESSAGE — diagnostic code and up to 2,000 characters of message text explaining failures.
• LEDGER_ID, PERIOD_NAME, BUDGET_VERSION_ID, FUNDING_BUDGET_NAME, BUDGET_TYPE, BUDGET_LEVEL — the budget context against which the check was executed.
• JE_HEADER_ID, JE_BATCH_ID, JE_HEADER_NAME, JOURNAL_LINE_NUMBER, CCID, ACCOUNT_SEGMENT_VALUE — the journal identity and account of the line under review.
• DEBIT_CREDIT_INDICATOR, AMOUNT, DEBIT_AMOUNT_ACCOUNTED, CREDIT_AMOUNT_ACCOUNTED — amounts and accounting direction.
• BUDGET_POSTED_BALANCE, BUDGET_APPROVED_BALANCE, BUDGET_PENDING_BALANCE, BUDGET_TOTAL_BALANCE — balance components used in the availability computation.
• CURRENT_FUNDS_AVAILABLE — the computed funds position at evaluation time.
• DOCUMENT_STATUS, ERROR_SOURCE — source-processing and error attribution columns.

No primary key or unique index is documented on the temporary structure. ROW_ID, EVENT_ID, and PACKET_ID act as session-scoped correlation keys rather than durable business keys; PACKET_ID in particular groups a set of lines evaluated as one request. The documented foreign key on ROW_ID to CS_SYSTEMS_ALL_B_TEMP is a transient linkage within the same session.

Common Use Cases and Queries

The principal use case is real-time diagnosis of funds check failures. A typical query pattern joins the transaction identity columns to the result columns for a given journal line:

• Retrieve all lines in a packet: SELECT je_header_id, journal_line_number, funds_check_status, funds_check_level_meaning, boundary, result_message FROM psa_bc_results_gt WHERE packet_id = :p_packet_id ORDER BY journal_line_number;
• Isolate failures: SELECT je_header_id, ccid, funds_check_status_code, current_funds_available, result_message FROM psa_bc_results_gt WHERE funds_check_status_code NOT IN ('A','P');
• Balance reconciliation for a budget version: aggregate BUDGET_POSTED_BALANCE and BUDGET_PENDING_BALANCE by BUDGET_VERSION_ID and PERIOD_NAME to confirm the figures used by the control engine.
• Extensibility review of encumbrance and obligation components using the OBLI_ENCUM_* and COMM_ENCUM_* columns.
• Error triage filtered by ERROR_SOURCE and DOCUMENT_STATUS when integrating external feeder systems.

Because data persists only for the transaction duration, queries must execute within the originating session; concurrent sessions cannot see one another's rows.

Related Objects

• CS_SYSTEMS_ALL_B_TEMP — joined via ROW_ID; supplies the temporary row correlation used by the BC engine.
• PSA_BC_RESULTS — the permanent counterpart table that persists the same result set for later reporting and audit.
• GL_JE_HEADERS / GL_JE_LINES — joined via JE_HEADER_ID and JE_HEADER_NAME to resolve document context.
• GL_CODE_COMBINATIONS — joined via CCID to obtain the account combination behind each checked line.
• GL_BUDGET_VERSIONS / GL_BUDGET_ASSIGNMENTS — resolve BUDGET_VERSION_ID and FUNDING_BUDGET_NAME.
• GL_LEDGERS — resolves LEDGER_ID to the ledger and its control configuration.
• FND_APPLICATION — resolves APPLICATION_ID and APPLICATION_SHORT_NAME for the originating module.
• PO_DISTRIBUTIONS_ALL / AP_INVOICE_DISTRIBUTIONS_ALL — source documents referenced through SOURCE_DISTRIBUTION_ID_NUM_* and PO_DIST_LINE_NUMBER.