Search Results pc_cur_conv_rejection_code

Overview

The view PA_FP_BUDGET_LINE_REJECTIONS_V (owner APPS, status VALID) is a reporting and integration object within the Oracle E-Business Suite Projects (PA) module. It exposes rejection details at both the resource assignment level and the task assignment level for self-service budgets and workplan entries. Its purpose is to surface, for each budget line held in PA_BUDGET_LINES, the cost and burden rejection codes generated during budget or workplan submission, together with human-readable rejection messages. This enables functional users, forms, and self-service pages to identify why a given budget line failed validation, rather than forcing them to inspect raw code columns directly.

The view is therefore a diagnostic layer over the budget lines table. It is used during budget entry and workplan processing to drive error messages back to the end user, and it can also be queried directly for reconciliation and reporting of rejected budget lines.

Underlying Base Objects

The view has been documented against the following referenced base objects: FND_NEW_MESSAGES (synonym), PA_BUDGET_LINES (synonym), PA_BUDGET_VERSIONS (synonym), PA_FIN_PLAN_UTILS2 (package), PA_RESOURCE_ASSIGNMENTS (synonym), PA_RESOURCE_LIST_MEMBERS (synonym), and DUAL (synonym).

The primary driving table is PA_BUDGET_LINES (aliased BL), joined to PA_BUDGET_VERSIONS (BV) on BUDGET_VERSION_ID and to PA_RESOURCE_ASSIGNMENTS (RAM) to obtain the TASK_ID. Rejection codes stored on the budget line, such as COST_REJECTION_CODE and BURDEN_REJECTION_CODE, are resolved to text using correlated subqueries against FND_NEW_MESSAGES, filtered by APPLICATION_ID = 275 (the PA application) and the session language via USERENV('LANG'). Two additional derived flags rely on self-joins back to PA_BUDGET_LINES to test for the existence of any rejected line for the same resource assignment, one of which uses the PA_FIN_PLAN_UTILS2 package functions GET_BDGT_START_DATE and GET_BDGT_END_DATE to restrict the check to the current budget period. PA_RESOURCE_LIST_MEMBERS and DUAL support the remaining selection and existence logic.

Key Columns

• BUDGET_VERSION_ID, PROJECT_ID, TASK_ID — identify the budget version, project, and task context of the rejected line.
• BUDGET_LINE_ID, RESOURCE_ASSIGNMENT_ID — the specific budget line and resource assignment affected.
• START_DATE, END_DATE, PERIOD_NAME — the date range and period for the rejected line.
• TXN_CURRENCY_CODE, PROJECT_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE — the transaction, project, and project-functional currency codes.
• COST_REJECTION_CODE / BURDEN_REJECTION_CODE — raw cost and burden rejection codes stored on the budget line.
• COST_REJECTION_MSG_DATA / BURDEN_REJECTION_MSG_DATA — the translated rejection message text from FND_NEW_MESSAGES.
• COST_REJECTION_FLAG — set to 'Y' when any budget line for the same version, currency, and resource assignment carries a cost rejection code.
• PERIOD_COST_REJECTION_FLAG — set to 'Y' when such a cost rejection falls within the current budget period boundaries returned by PA_FIN_PLAN_UTILS2.

Common Use Cases and Queries

A typical scenario is retrieving all rejected lines for a budget version so that messages can be presented to the user or extracted for audit:

• Display rejection messages: SELECT BUDGET_LINE_ID, COST_REJECTION_CODE, COST_REJECTION_MSG_DATA, BURDEN_REJECTION_CODE, BURDEN_REJECTION_MSG_DATA FROM PA_FP_BUDGET_LINE_REJECTIONS_V WHERE BUDGET_VERSION_ID = :p_version_id;
• Isolate assignment-level failures: SELECT RESOURCE_ASSIGNMENT_ID, TASK_ID, COST_REJECTION_FLAG, PERIOD_COST_REJECTION_FLAG FROM PA_FP_BUDGET_LINE_REJECTIONS_V WHERE PROJECT_ID = :p_project_id AND COST_REJECTION_FLAG = 'Y';
• Detect period-specific cost problems: filter on PERIOD_COST_REJECTION_FLAG = 'Y' to find lines rejected within the current budget period window computed by PA_FIN_PLAN_UTILS2.
• Currency analysis: group by TXN_CURRENCY_CODE to determine whether rejections are concentrated in a particular transaction currency.

Because rejection codes are resolved via FND_NEW_MESSAGES using the session language, queries return localized message text appropriate to the runtime environment, which makes the view suitable for embedded self-service UI logic as well as ad hoc reporting.