Results for “pa_status_proj_cmt_base_v”

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

Overview

PA_STATUS_PROJ_CMT_BASE_V is an Oracle Projects (PA) view owned by the APPS schema. Its ETRM description states "10SC Only - Retrofitted", indicating it originated as a customer-specific (10SC) extension that was subsequently retrofitted into the standard Oracle E-Business Suite environment. The object is documented with a VALID status in both Oracle EBS 12.1.1 and 12.2.2, and its implementation text confirms a standard APPS.PA_STATUS_PROJ_CMT_BASE_V deployment.

The view consolidates project commitment transaction data — purchase order, requisition, and other commitment lines — enriched with task, organization, and lookup descriptions. It is scoped to a single project through the predicate CT.PROJECT_ID = PA_STATUS.GETPROJID, which calls the PA_STATUS package to resolve the current project context. This design makes the view a reporting and integration surface for commitment information presented in project status and commitment detail inquiries, rather than a general-purpose commitment extract.

Underlying Base Objects

The view joins five principal sources and has a documented dependency list that also includes several package and security objects:

• PA_COMMITMENT_TXNS (synonym) — the driving table, aliased CT, supplying commitment header and line attributes.
• PA_TXN_ACCUM_DETAILS (synonym) — aliased TAD, joined via CMT_LINE_ID with the filter TAD.LINE_TYPE = 'M'.
• PA_LOOKUPS (view) — joined twice as L and L2 to decode COMMITMENT LINE TYPE and COMMITMENT TXN SOURCE.
• PA_TASKS (synonym) — aliased T, outer-joined on TASK_ID to supply task number and name.
• HR_ORGANIZATION_UNITS (view) — aliased O, joined on ORGANIZATION_ID for the expenditure organization name.
• PA_STATUS (package) — provides GETPROJID, the project context driver.
• HR_GENERAL and HR_SECURITY (packages) — documented dependencies providing organizational security and name resolution support.

Key Columns

The projection exposes commitment identity, cost, date, and dimension attributes. Notable documented columns include:

• PROJECT_ID, TASK_ID, RESOURCE_LIST_MEMBER_ID, TXN_ACCUM_ID — keys linking the row to project, task, and transaction accumulator context.
• VENDOR_ID, VENDOR_NAME, CMT_NUMBER, CMT_LINE_NUMBER — supplier and commitment document identifiers.
• TOT_CMT_RAW_COST, TOT_CMT_BURDENED_COST — total commitment raw and burdened amounts.
• DENOM_RAW_COST, DENOM_BURDENED_COST, ACCT_RAW_COST, ACCT_BURDENED_COST, PROJECT_EXCHANGE_RATE — currency-denominated and accounted cost values with associated rate dates, rate types, and exchange rates.
• CMT_CREATION_DATE, CMT_APPROVED_DATE, CMT_PROMISED_DATE, CMT_NEED_BY_DATE — commitment lifecycle dates.
• LINE_TYPE and CMT_TYPE_CODE_M — decoded meanings from PA_LOOKUPS.
• TASK_NUMBER, TASK_NAME, EXPENDITURE_TYPE, ORGANIZATION_ID, EXPENDITURE_ORG_NAME, QUANTITY_OUTSTANDING, UNIT_OF_MEASURE — descriptive and quantity attributes.

Common Use Cases and Queries

The view is typically used to report outstanding commitments against a project in its native currency and accounted currency, and to reconcile commitment totals with transaction accumulators. A representative query is:

SELECT project_id, cmt_number, cmt_line_number, vendor_name, tot_cmt_raw_cost, tot_cmt_burdened_cost, task_number, expenditure_org_name FROM apps.pa_status_proj_cmt_base_v;

Because the view filters on PA_STATUS.GETPROJID, callers must establish the project context through the PA_STATUS package before the query returns rows. Typical scenarios include project status commitment drill-downs, commitment-versus-budget analysis, and integration extracts feeding downstream reporting where a single-project commitment snapshot is required.