Search Results funds_check_rejection_code

Overview

APPS.PA_BGT_ACCT_LINES_V is a supplementary view in the Oracle E-Business Suite Applications schema (APPS), registered under the FND Design Data reference PA.PA_BGT_ACCT_LINES_V and reported with status VALID. It belongs to the Oracle Projects (PA) module and is intended to simplify form coding by presenting a flattened, denormalized projection of budget account line data. Oracle classifies it as a supplementary view and explicitly warns that it should not be queried or altered directly because its definition may change dramatically in subsequent minor or major releases. Consequently, it is best treated as an internal implementation object supporting Oracle Projects budget entry and funds check validation screens rather than as a supported integration interface.

The object is relevant to the search term "funds_check_rejection_code" because it exposes the FUNDS_CHECK_REJECTION_CODE column alongside FUNDS_CHECK_STATUS_CODE, allowing a form or report to display both the outcome of a budgetary funds check and the specific rejection reason associated with a budget account line.

Underlying Base Objects

According to the documented dependencies, PA_BGT_ACCT_LINES_V is defined over two base objects in the APPS schema, both referenced through synonyms:

• PA_BUDGET_ACCT_LINES — the transaction table holding budget account line records, including amounts, code combination identifiers, and funds check status and rejection information.
• PA_BUDGET_VERSIONS — the budget version header table that provides version context such as the version identifier and period information used to join line data to a specific budget version.

The view joins these tables to present each budget account line together with its associated version context. No other database object in the documented metadata references PA_BGT_ACCT_LINES_V, confirming its role as a leaf-level, form-support object rather than a shared dependency for downstream views.

Key Columns

• ROW_ID (ROWID) — the physical row identifier of the underlying budget account line.
• BUDGET_ACCT_LINE_ID (NUMBER) — primary identifier for the budget account line.
• BUDGET_VERSION_ID (NUMBER) — identifies the budget version to which the line belongs; joins to PA_BUDGET_VERSIONS.
• CODE_COMBINATION_ID (NUMBER) — the accounting flexfield combination against which the budget line is recorded.
• GL_PERIOD_NAME (VARCHAR2) and START_DATE (DATE) — the GL period and start date associated with the line.
• PREV_VER_BUDGET_AMOUNT / PREV_VER_AVAILABLE_AMOUNT — budget and available amounts carried from the previous version.
• CURR_VER_BUDGET_AMOUNT / CURR_VER_AVAILABLE_AMOUNT — budget and available amounts for the current version.
• ACCOUNTED_AMOUNT (NUMBER) — the accounted amount on the line.
• FUNDS_CHECK_STATUS_CODE (VARCHAR2) — status outcome of the funds check performed against the line.
• FUNDS_CHECK_REJECTION_CODE (VARCHAR2) — the rejection code returned when the funds check fails, indicating why the line was rejected.

Common Use Cases and Queries

Typical usage is diagnostic or investigative: identifying lines whose funds check was rejected and understanding the reason. Although Oracle discourages direct querying, the following pattern is commonly used for troubleshooting and is consistent with the documented query text:

• Listing rejected budget account lines with their rejection codes and version context.
• Aggregating budgeted and available amounts by budget version and code combination.
• Comparing previous-version and current-version budget and available amounts to explain rejection thresholds.

Sample SQL:

SELECT budget_acct_line_id, budget_version_id, code_combination_id, gl_period_name, funds_check_status_code, funds_check_rejection_code, curr_ver_budget_amount, curr_ver_available_amount FROM apps.pa_bgt_acct_lines_v WHERE funds_check_rejection_code IS NOT NULL;

Because the view is documented as subject to change, production reporting and integrations should preferably be built against the underlying PA_BUDGET_ACCT_LINES and PA_BUDGET_VERSIONS tables rather than this view.