Search Results funds_check_status_code

Overview

PA_BGT_ACCT_LINES_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module, documented as VALID in ETRM for releases 12.1.1 and 12.2.2. It presents project or task budget information at the accounting-line level, combining GL period, code combination identifier, budget and available amounts, accounted amounts, and funds check status. The view functions as a reporting and integration surface over the project budget accounting lines, exposing the monetary state of a budget version alongside its budgetary control outcome.

The view is particularly relevant to users searching on FUNDS_CHECK_STATUS_CODE, since it exposes both FUNDS_CHECK_STATUS_CODE and FUNDS_CHECK_RESULT_CODE for each budget accounting line. These columns allow reporting on whether budget lines have passed, failed, or are pending funds checking under budgetary control, which is essential for public sector and other organizations that enforce budget availability before committing or encumbering funds.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in APPS:

• PA_BUDGET_ACCT_LINES — the primary table holding one row per budget accounting line. The view selects BUDGET_ACCT_LINE_ID, BUDGET_VERSION_ID, CODE_COMBINATION_ID, GL_PERIOD_NAME, START_DATE, the previous and current version budget and available amounts, ACCOUNTED_AMOUNT, and the funds check columns from this table.
• PA_BUDGET_VERSIONS — joined on BUDGET_VERSION_ID, providing BUDGET_STATUS_CODE used to derive the current version available amount.

The join condition is BV.BUDGET_VERSION_ID = BAL.BUDGET_VERSION_ID. The view does not introduce aggregation; it is a one-to-one projection with a derived column, preserving the grain of PA_BUDGET_ACCT_LINES.

Key Columns

• ROW_ID — the ROWID of the underlying PA_BUDGET_ACCT_LINES row.
• BUDGET_ACCT_LINE_ID — primary identifier of the budget accounting line.
• BUDGET_VERSION_ID — the budget version to which the line belongs.
• CODE_COMBINATION_ID — the GL accounting flexfield combination charged by the budget line.
• GL_PERIOD_NAME and START_DATE — the GL period and start date associated with the line.
• PREV_VER_BUDGET_AMOUNT and PREV_VER_AVAILABLE_AMOUNT — budget and available amounts carried from the prior version.
• CURR_VER_BUDGET_AMOUNT — the current version budget amount.
• CURR_VER_AVAILABLE_AMOUNT — derived in the view: when the budget status code is 'B' (baselined), it returns CURR_VER_AVAILABLE_AMOUNT directly; otherwise it computes CURR_VER_BUDGET_AMOUNT minus the consumed prior-version amount (PREV_VER_BUDGET_AMOUNT minus PREV_VER_AVAILABLE_AMOUNT).
• ACCOUNTED_AMOUNT — the accounted amount recorded against the line.
• FUNDS_CHECK_STATUS_CODE — the funds check status for the line.
• FUNDS_CHECK_RESULT_CODE — the funds check result. Note that ETRM lists FUNDS_CHECK_REJECTION_CODE in the column listing while the view text exposes FUNDS_CHECK_RESULT_CODE; both should be verified against the deployed definition in the target instance.

Common Use Cases and Queries

Typical use cases include budgetary control reporting, funds check exception analysis, budget versus available balance reconciliation, and integration extracts feeding GL or custom dashboards. A representative query for funds check status is:

• SELECT budget_version_id, budget_acct_line_id, code_combination_id, gl_period_name, funds_check_status_code, funds_check_result_code, curr_ver_budget_amount, curr_ver_available_amount FROM pa_bgt_acct_lines_v WHERE funds_check_status_code = :p_status;
• Joining to PA_BUDGET_VERSIONS or PA_PROJECTS to attribute lines to a project or task.
• Aggregating curr_ver_budget_amount and curr_ver_available_amount by code_combination_id and gl_period_name for budget availability reporting.

Because the view is owned by APPS, queries should be qualified with APPS or accessed through a synonym in the reporting schema.