Search Results burden_amt_disp_method

Overview

APPS.PA_RES_MAP_BTC_V is an internal Oracle E-Business Suite view owned by the APPS schema and defined under FND Design Data identifier PA.PA_RES_MAP_BTC_V. It is classified with a status of VALID and is documented as an Oracle Internal Use Only object: Oracle Corporation does not support direct data access except through standard Oracle Applications programs. The view functions as a resource-mapping layer used in the budgetary control (BTC) processing path for Oracle Projects, exposing expenditure and cost distribution attributes that are resolved against budgetary control options, budget entry methods, budget versions, and implementation settings before funds checking is performed.

Columns published by the view include identifiers such as EXPENDITURE_ITEM_ID, PROJECT_ID, TASK_ID, TOP_TASK_ID, ORGANIZATION_ID, JOB_ID, PERSON_ID, BUDGET_VERSION_ID, RESOURCE_LIST_ID, PO_LINE_ID, DR_CODE_COMBINATION_ID, and ORG_ID, together with descriptive attributes such as EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, SYSTEM_LINKAGE_FUNCTION, ENTRY_LEVEL_CODE, SYSTEM_REFERENCE1 through 3, EI_ADJUSTMENT_TYPE, PROJECT_TYPE, and BURDEN_AMT_DISP_METHOD. A CDL_ROWID column carries the ROWID of the associated cost distribution line. The view is therefore a denormalised staging structure in which transactional expenditure lines are paired with the control metadata required to determine whether and how an encumbrance or funds check applies.

Underlying Base Objects

In 12.2.2 the view resolves to the following documented base objects: GL_PERIODS, GL_SETS_OF_BOOKS, PA_AUD_COST_DIST_LINES, PA_BUDGETARY_CONTROL_OPTIONS, PA_BUDGET_ENTRY_METHODS, PA_BUDGET_VERSIONS, PA_COST_DISTRIBUTION_LINES, PA_COST_DISTRIBUTION_LINES_ALL, PA_EXPENDITURES_ALL, PA_EXPENDITURE_ITEMS, PA_EXPENDITURE_ITEMS_ALL, PA_EXPENDITURE_TYPES, PA_FUNDS_CONTROL_UTILS, PA_IMPLEMENTATIONS, PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, and PA_TASKS. All references except GL_SETS_OF_BOOKS and PA_FUNDS_CONTROL_UTILS are synonyms or views; PA_FUNDS_CONTROL_UTILS is a PL/SQL package and PA_IMPLEMENTATIONS supplies the operating-unit configuration.

The transactional core is drawn from PA_COST_DISTRIBUTION_LINES and its _ALL variant, joined to PA_EXPENDITURE_ITEMS(_ALL) and PA_EXPENDITURES_ALL. Project, task, and project type context derives from PA_PROJECTS_ALL, PA_TASKS, and PA_PROJECT_TYPES_ALL. Fiscal context for GL_START_DATE is obtained through GL_SETS_OF_BOOKS and GL_PERIODS. The budgetary control dimensions are supplied by PA_BUDGETARY_CONTROL_OPTIONS, PA_BUDGET_ENTRY_METHODS, and PA_BUDGET_VERSIONS, while PA_AUD_COST_DIST_LINES retains the audit image of the same lines. The presence of these control tables explains why the view is restricted to internal consumption.

Key Columns

• EXPENDITURE_ITEM_ID / CDL_ROWID: Identify the expenditure item and its originating cost distribution line; these are the join keys back to transaction detail.
• PROJECT_ID, TASK_ID, TOP_TASK_ID, ORGANIZATION_ID, JOB_ID, PERSON_ID: Provide the full project, task hierarchy, organisation, and resource context required for burdening and funds checking.
• ENCUM_TYPE_ID: The encumbrance type identifier, used to classify the encumbrance against which the expenditure is being validated. This is the column most frequently sought when diagnosing budgetary control errors.
• EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, EI_ADJUSTMENT_TYPE: Define the cost classification of the line and whether it represents an adjustment.
• BUDGET_VERSION_ID, RESOURCE_LIST_ID, ENTRY_LEVEL_CODE, BURDEN_AMT_DISP_METHOD: Determine the budget version, resource list, entry level, and burden display behaviour applied during processing.
• SYSTEM_LINKAGE_FUNCTION, SYSTEM_REFERENCE1–3, PO_LINE_ID, VENDOR_ID: Link the expenditure to source documents such as purchasing, thereby resolving committed cost to a specific purchase order line.
• GL_START_DATE, DR_CODE_COMBINATION_ID, ORG_ID: Supply the accounting date, debit code combination, and operating unit for GL posting.
• PROJECT_TYPE: Carries the project type classification used in funds control rules.

Common Use Cases and Queries

Typical internal usage includes diagnosing funds check failures, tracing encumbrance creation during purchasing-to-projects cost collection, and validating budget entry behaviour. The following query lists encumbrance types for a given project:

SELECT expenditure_item_id, task_id, encum_type_id,
       expenditure_type, gl_start_date, org_id
FROM   apps.pa_res_map_btc_v
WHERE  project_id = :p_project_id
AND    encum_type_id IS NOT NULL;

Because the object is marked Oracle Internal Use Only, organisations should not build supported custom reports directly upon it. Querying it is appropriate for troubleshooting and research, with any persistent extension implemented through supported Oracle Projects APIs or the corresponding public views.