Search Results pa_status_cmt_base_v




Overview
Explore in AI Chat

Overview

PA_STATUS_CMT_BASE_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite. Its description is recorded as "10SC Only - Retrofitted - Retrofitted," indicating that the object originated in an earlier 10SC code line and was retrofitted into the EBS 11i/12.x data model rather than being designed natively for Release 12. The view exposes commitment (CMT) status information for project and task transactions, combining cost, currency, and exchange-rate attributes into a single reporting interface.

The view is a UNION ALL consolidation: its view text joins the output of PA_STATUS_PROJ_CMT_BASE_V with that of PA_STATUS_TASK_CMT_BASE_V. Each branch returns an identical column list, so the result set is a uniform commitment fact source spanning both project-level and task-level commitments. Because the underlying branches are status base views, PA_STATUS_CMT_BASE_V is intended for inquiry, reporting, and integration rather than transactional maintenance; consumers should treat it as read-only.

The view is significant for the search term "acct_rate_type" because it publishes ACCT_RATE_TYPE (alongside ACCT_RATE_DATE and ACCT_EXCHANGE_RATE), the rate type used to convert commitment amounts into the accounting currency.

Underlying Base Objects

The documented referenced base objects for this view are:

  • PA_STATUS_PROJ_CMT_BASE_V (VIEW) — project-level commitment branch
  • PA_STATUS_TASK_CMT_BASE_V (VIEW) — task-level commitment branch
  • PA_STATUS_RSRC_CMT_BASE_V (VIEW) — resource-level commitment branch referenced in the metadata
  • PA_STATUS (PACKAGE) — status logic the base views depend upon
  • HR_GENERAL (PACKAGE) and HR_SECURITY (PACKAGE) — security and general HR utilities applied for row-level access and organization context

The UNION ALL between the project and task branches is explicit in the view text, and the task branch text terminates at "FROM PA_STATUS_TASK_CMT_BASE_V UN" in the excerpt, confirming the union continues to the resource branch. The HR_SECURITY dependency means that query results are filtered by the operating unit and organization security profile of the session, and HR_GENERAL supplies organization-related lookups.

Key Columns

The view returns a broad commitment fact set. Identity and context columns include PROJECT_ID, TASK_ID, RESOURCE_LIST_MEMBER_ID, TXN_ACCUM_ID, TASK_NUMBER, TASK_NAME, EXPENDITURE_TYPE, ORGANIZATION_ID and EXPENDITURE_ORG_NAME, plus VENDOR_ID and VENDOR_NAME. Commitment descriptors include CMT_CREATION_DATE, CMT_TYPE_CODE, CMT_TYPE_CODE_M, CMT_NUMBER, CMT_LINE_NUMBER, CMT_APPROVED_FLAG, CMT_APPROVED_DATE, CMT_PROMISED_DATE, CMT_NEED_BY_DATE, CMT_REJECTION_CODE, TRANSACTION_SOURCE, TRANSACTION_SOURCE_M, QUANTITY_OUTSTANDING and UNIT_OF_MEASURE.

Cost and currency columns are organized in layers: TOT_CMT_RAW_COST and TOT_CMT_BURDENED_COST; DENOM_CURRENCY_CODE, DENOM_RAW_COST, DENOM_BURDENED_COST; ACCT_CURRENCY_CODE, ACCT_RAW_COST, ACCT_BURDENED_COST, ACCT_RATE_DATE, ACCT_RATE_TYPE, ACCT_EXCHANGE_RATE; RECEIPT_CURRENCY_CODE, RECEIPT_CURRENCY_AMOUNT, RECEIPT_EXCHANGE_RATE; and PROJECT_CURRENCY_CODE, PROJECT_RATE_DATE, PROJECT_RATE_TYPE, PROJECT_EXCHANGE_RATE. ACCT_RATE_TYPE therefore identifies the conversion rate type (for example Corporate or Spot) applied to derive accounting-currency commitment values, and it pairs with ACCT_EXCHANGE_RATE for audit and reconciliation.

Common Use Cases and Queries

Typical scenarios include unapproved and outstanding commitment reporting, commitment-to-actual variance analysis, and currency-conversion audit. A representative query filtering on the rate type is:

  • SELECT project_id, task_number, cmt_number, acct_currency_code, acct_rate_type, acct_exchange_rate, acct_burdened_cost FROM pa_status_cmt_base_v WHERE acct_rate_type = 'Corporate' AND cmt_approved_flag = 'N' ORDER BY project_id, task_number;
  • SELECT organization_id, expenditure_org_name, SUM(acct_burdened_cost) FROM pa_status_cmt_base_v WHERE cmt_approved_flag = 'Y' GROUP BY organization_id, expenditure_org_name;
  • SELECT cmt_type_code, cmt_type_code_m, COUNT(*), SUM(quantity_outstanding) FROM pa_status_cmt_base_v GROUP BY cmt_type_code, cmt_type_code_m;
  • SELECT cmt_number, project_rate_type, project_exchange_rate, acct_rate_type, acct_exchange_rate FROM pa_status_cmt_base_v WHERE transaction_source = 'PURCHASING';

Because access is governed by HR_SECURITY, results vary with the assigned security profile; reports should therefore avoid hard-coded organization assumptions and rely on the view's security filtering.