Results for “ccid_gen_rej_message”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_BUDGET_LINES_DIST_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents project or task budget information at the individual budget line level, combining budget line amounts with the associated resource assignment, resource list member, task, and accounting code combination. The view is primarily consumed by Oracle's budget distribution and code combination generation logic, where cost, burdened cost, and revenue amounts are broken out by period and mapped to an accounting flexfield combination.

The view derives its name from the "dist" (distribution) concept: each row represents a distribution of a budget line across a period, resource, and accounting combination. Because it exposes CCID_GEN_REJ_MESSAGE — the rejection message raised during code combination generation — the view is instrumental for diagnosing why a budget line failed to acquire a valid CODE_COMBINATION_ID during the Generate CCIDs process. This makes it a key reference for both period-end budget processing and troubleshooting rejected accounting distributions.

Underlying Base Objects

The view is defined over four base tables, accessed through APPS synonyms, plus one PL/SQL package:

• PA_BUDGET_LINES — the driving table, supplying resource assignment, code combination, period, and amount columns.
• PA_RESOURCE_ASSIGNMENTS — joined on RESOURCE_ASSIGNMENT_ID to supply the budget version, project, and task identifiers.
• PA_RESOURCE_LIST_MEMBERS — joined on RESOURCE_LIST_MEMBER_ID to supply the resource alias/name; records flagged with MIGRATION_CODE = 'N' are excluded.
• PA_TASKS — outer-joined on TASK_ID to supply TASK_NUMBER and parent task hierarchy.
• PA_TASK_UTILS — package invoked via PA_TASK_UTILS.SORT_ORDER_TREE_WALK to compute the hierarchical SORT_ORDER used to order tasks in a tree-walk sequence.

The task join is an outer join (T.TASK_ID = T.TASK_ID(+)), so budget lines without a task still appear, defaulting to a sort order of '1'. The constructed ROWID and full hierarchy walk mean the view is read-only and cannot be updated directly.

Key Columns

• RESOURCE_ASSIGNMENT_ID / BUDGET_VERSION_ID / PROJECT_ID / TASK_ID — core identifiers linking the budget line to its budget version, project, and task.
• TASK_NUMBER and SORT_ORDER — the task identifier and its tree-walk ordering, enabling hierarchical budget reporting.
• CODE_COMBINATION_ID — the accounting flexfield combination charged by the line.
• RESOURCE_LIST_MEMBER_ID / RESOURCE_NAME (aliased from M.ALIAS) — the budgeted resource.
• PERIOD_NAME / PERIOD_START_DATE — the budget period and its start date.
• RAW_COST, BURDENED_COST, REVENUE — the budgeted amounts for the line.
• CCID_GEN_REJ_MESSAGE — the rejection message returned when code combination generation fails for the line; a NULL value indicates successful generation.

Common Use Cases and Queries

The view is commonly queried to review budget line distributions, validate accounting combinations, and, critically, to surface rejected CCID generations. A representative query to locate rejected budget lines follows:

• SELECT project_id, task_number, period_name, resource_name, raw_cost, burdened_cost, revenue, code_combination_id, ccid_gen_rej_message FROM pa_budget_lines_dist_v WHERE ccid_gen_rej_message IS NOT NULL;
• Budget review by period: SELECT project_id, task_number, period_name, resource_name, raw_cost FROM pa_budget_lines_dist_v WHERE project_id = :project_id ORDER BY sort_order, period_name;
• Distribution totals: SELECT code_combination_id, SUM(raw_cost) FROM pa_budget_lines_dist_v GROUP BY code_combination_id;

Note that the view does not filter by project or budget version at runtime, so predicates on PROJECT_ID and BUDGET_VERSION_ID should always be supplied for performance. Because it spans resource assignments and task hierarchies, its results reflect the same logic used internally by the budget distribution process, making it a reliable diagnostic and reporting source in Oracle EBS 12.1.1 and 12.2.2.