Results for “expenditure_org_name”

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

Overview

PA_ACCUM_RSRC_CMT_TXNS_BASE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) product. It is classified in ETRM as a retrofitted object, indicating that it was introduced into the 12.1.1 code line through a retrofit rather than originating with the initial release, and it remains VALID in 12.2.2. The view exposes project–task–resource level commitment information, joining accumulated transaction data to commitment transaction lines so that purchasing commitments can be reported alongside the project and resource structures to which they apply.

Commitments in Oracle Projects represent outstanding purchase order, blanket release, or requisition amounts associated with a project. The PA_ACCUM_RSRC_CMT_TXNS_BASE_V view consolidates these commitments at the resource level, carrying both the transaction accumulation identifiers used by the Projects accumulation engine and the descriptive commitment-line attributes. Because the view is a denormalized, pre-joined read-only structure, it is used primarily for reporting, analytics, and downstream integration, and should not be treated as a transactional interface.

Underlying Base Objects

The documented base objects referenced by the view are HR_GENERAL (package), HR_ORGANIZATION_UNITS (view), HR_SECURITY (package), PA_COMMITMENT_TXNS (synonym), PA_LOOKUPS (view), PA_RESOURCE_ACCUM_DETAILS (synonym), PA_TASKS (synonym), and PA_TXN_ACCUM_DETAILS (synonym).

The view text links these sources as follows. PA_RESOURCE_ACCUM_DETAILS supplies the resource list member and transaction accumulation identifiers. PA_TXN_ACCUM_DETAILS bridges the accumulation record to the commitment line, filtered by LINE_TYPE = 'M', which is the code indicating a commitment (as opposed to an actual) line in the accumulation detail. PA_COMMITMENT_TXNS is the primary source of commitment attributes — vendor, commitment number and line, amounts, dates, and quantities. PA_TASKS provides task number and task name, HR_ORGANIZATION_UNITS provides the expenditure organization name, and the PA_LOOKUPS view is joined twice to translate the commitment line type and the commitment transaction source into their display meanings. The HR_GENERAL and HR_SECURITY packages appear in the dependency metadata to support organization security enforcement against the HR organization references.

Key Columns

• PROJECT_ID, TASK_ID, RESOURCE_LIST_MEMBER_ID — the project–task–resource key that establishes the reporting grain of the view.
• TXN_ACCUM_ID — the accumulation transaction identifier, linking the row to the Projects accumulation engine.
• VENDOR_ID, VENDOR_NAME, CMT_NUMBER, CMT_LINE_NUMBER — supplier and purchase document identification for the commitment.
• TOT_CMT_RAW_COST, TOT_CMT_BURDENED_COST — total commitment value at raw and burdened cost.
• CMT_CREATION_DATE, CMT_APPROVED_DATE, CMT_PROMISED_DATE, CMT_NEED_BY_DATE — lifecycle dates for the commitment.
• CMT_APPROVED_FLAG, LINE_TYPE, CMT_TYPE_CODE — status and classification attributes; LINE_TYPE is translated to its meaning through PA_LOOKUPS.
• TASK_NUMBER, TASK_NAME, EXPENDITURE_TYPE, ORGANIZATION_ID, EXPENDITURE_ORG_NAME — project and organization context.
• TOT_CMT_QUANTITY / QUANTITY_OUTSTANDING, UNIT_OF_MEASURE, AMOUNT_DELIVERED — committed and delivered quantities and measures.
• TRANSACTION_SOURCE, CMT_DISTRIBUTION_ID — the originating transaction source and the commitment distribution identifier.

Common Use Cases and Queries

Typical scenarios include outstanding commitment reporting by project and task, supplier exposure analysis, and reconciliation between commitment figures and the Projects accumulation tables. A representative query is:

• SELECT project_id, task_number, task_name, vendor_name, cmt_number, cmt_line_number, tot_cmt_raw_cost, tot_cmt_burdened_cost FROM pa_accum_rsrc_cmt_txns_base_v WHERE project_id = :p_project_id ORDER BY task_number, cmt_number;
• SELECT project_id, SUM(tot_cmt_raw_cost) FROM pa_accum_rsrc_cmt_txns_base_v WHERE cmt_approved_flag = 'Y' GROUP BY project_id;
• SELECT resource_list_member_id, vendor_name, cmt_need_by_date, tot_cmt_quantity, unit_of_measure FROM pa_accum_rsrc_cmt_txns_base_v WHERE txn_accum_id = :p_txn_accum_id;

Because the view enforces no filter of its own beyond the commitment line type, queries should always constrain on project, task, or accumulation identifiers to avoid full scans of the underlying accumulation and commitment tables.