Results for “cdl_rowid”

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

Overview

PA_RES_MAP_BTC_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. Its documented purpose is to select raw BTC (Burden Transaction Cost) cost distribution lines that require resource mapping during the Funds Checking process. In Oracle Projects, funds checking validates whether sufficient budgetary authority exists before an expenditure, requisition, or commitment is processed. During this validation the Funds Checking engine must translate raw distribution rows into the resource dimensions recognized by the budgetary control model — organization, job, expenditure type, expenditure category, person, and vendor. PA_RES_MAP_BTC_V supplies precisely that pre-mapped rowset.

Because it is a view rather than a table, it holds no data of its own; it is a query-time projection over Projects transaction tables combined with inline scalar subqueries. It is internal infrastructure rather than an end-user reporting object, and is consumed programmatically by Funds Checking logic and by the PA_FUNDS_CONTROL_UTILS package.

Underlying Base Objects

Per the documented view metadata, PA_RES_MAP_BTC_V references the following objects, all accessed through APPS synonyms: PA_COST_DISTRIBUTION_LINES and PA_COST_DISTRIBUTION_LINES_ALL, PA_EXPENDITURES_ALL, PA_EXPENDITURE_ITEMS and PA_EXPENDITURE_ITEMS_ALL, PA_EXPENDITURE_TYPES, PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, PA_TASKS, PA_BUDGET_VERSIONS, PA_BUDGET_ENTRY_METHODS, PA_BUDGETARY_CONTROL_OPTIONS, PA_IMPLEMENTATIONS, PA_AUD_COST_DIST_LINES, GL_PERIODS, GL_SETS_OF_BOOKS, and the PA_FUNDS_CONTROL_UTILS package. PA_COST_DISTRIBUTION_LINES and PA_EXPENDITURE_ITEMS supply the driving expenditure item rows; PA_EXPENDITURES_ALL supplies the incurred-by organization and person; PA_EXPENDITURE_TYPES supplies the expenditure category. PA_TASKS and PA_PROJECTS_ALL resolve task and top-task hierarchy, while the GL objects provide the GL start date for the applicable period.

Key Columns

• EXPENDITURE_ITEM_ID, PROJECT_ID, TASK_ID, TOP_TASK_ID — identity and hierarchy keys for the expenditure item being funds-checked.
• CDL_ROWID — the ROWID of the source cost distribution line, used by the Funds Checking process to update mapped rows in place.
• ORGANIZATION_ID — derived as NVL(EI1.OVERRIDE_TO_ORGANIZATION_ID, EXP.INCURRED_BY_ORGANIZATION_ID), the organization against which budget is checked.
• JOB_ID, PERSON_ID, EXPENDITURE_TYPE, EXPENDITURE_CATEGORY — the resource dimensions used for resource-list matching.
• VENDOR_ID — populated from PA_COST_DISTRIBUTION_LINES.SYSTEM_REFERENCE1 via a correlated subquery on BURDEN_SUM_SOURCE_RUN_ID; this is the column most often associated with the "system_reference1" search term.
• ENCUM_TYPE_ID — returned by PA_FUNDS_CONTROL_UTILS.GET_ENCUM_TYPE_ID using the project and the 'STD' encumbrance type.
• BUDGET_VERSION_ID, RESOURCE_LIST_ID, ENTRY_LEVEL_CODE — resolved from the current, baselined budget version for projects with budgetary control enabled and an external budget code of 'GL' or null.
• GL_START_DATE, SYSTEM_LINKAGE_FUNCTION, REQUEST_ID, LINE_NUM — supporting GL period, linkage, and request context.

Common Use Cases and Queries

The principal use case is diagnostic: isolating the rows and vendor values that Funds Checking will process for a given project, request, or expenditure item. A representative query follows.

• SELECT expenditure_item_id, project_id, task_id, organization_id, job_id, expenditure_type, person_id, vendor_id, encum_type_id FROM pa_res_map_btc_v WHERE project_id = :p_project_id;
• SELECT vendor_id, COUNT(*) FROM pa_res_map_btc_v GROUP BY vendor_id ORDER BY 2 DESC; — profile vendor usage driven by SYSTEM_REFERENCE1.
• SELECT cdl.system_reference1, cdl.burden_sum_source_run_id FROM pa_cost_distribution_lines cdl WHERE cdl.system_reference1 IS NOT NULL; — confirm the source values feeding the VENDOR_ID subquery.

Because the view is tightly bound to Funds Checking internals and its defining SQL may change between patch levels, it should be queried read-only and validated against the current release (12.1.1 or 12.2.2) before use in any diagnostic report.