Search Results pjm_project_commit_v




Overview
Explore in AI Chat

Overview

PJM_PROJECT_COMMIT_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PJM (Project Manufacturing) product family and exposes project-level commitment transaction data for use by the Web Inquiry interface. The view consolidates commitment records originating from Oracle Purchasing and Projects so that cost, quantity, currency, and approval information can be presented at the project and task level without requiring the caller to join the underlying PA commitment tables directly.

The object is documented as VALID in ETRM with the description "Project level commitments for the Web Inquiry." It is a read-only presentation layer: it performs no data manipulation and contains no business logic beyond joins, lookups decoding, currency formatting, and message resolution. Because it draws from the shared PA commitment schema, it can be queried by custom reports, OAF pages, or integration extracts that need a flattened, project-centric view of commitments.

Underlying Base Objects

The view is defined over several documented base objects: PA_COMMITMENT_TXNS (synonym), PA_TASKS (synonym), PA_TXN_ACCUM_DETAILS (synonym), PA_LOOKUPS (view), HR_ALL_ORGANIZATION_UNITS_TL (synonym), FND_CURRENCIES (synonym), FND_CURRENCY_CACHE (package), and FND_MESSAGE_CACHE (package). PA_COMMITMENT_TXNS is the driving table, supplying the commitment header and line attributes, amounts, dates, quantities, and currency columns. PA_TASKS is joined to resolve the task number and task name.

PA_TXN_ACCUM_DETAILS provides the transaction accumulation identifier used for expenditure linkage. PA_LOOKUPS is joined twice (aliased L1 and L2) to decode lookup meanings for commitment attributes, including the rejection code, while HR_ALL_ORGANIZATION_UNITS_TL supplies the organization unit name. FND_CURRENCIES and the FND_CURRENCY_CACHE package are used to derive currency formatting masks for the raw and burdened cost amounts, and FND_MESSAGE_CACHE.GET_STRING resolves the CMT_REJECTION_CODE into a readable message string for the 'PA' application.

Key Columns

Common Use Cases and Queries

The view is typically used to report open and approved commitments by project, to reconcile commitment amounts against budget, and to surface rejection information where CMT_REJECTION_CODE is populated. A representative query filtering on rejection code and project is:

  • SELECT project_id, cmt_number, cmt_line_number, vendor_name, tot_cmt_burdened_cost, cmt_rejection_code FROM pjm_project_commit_v WHERE cmt_rejection_code IS NOT NULL AND project_id = :project_id;
  • SELECT project_id, task_number, task_name, SUM(tot_cmt_burdened_cost) FROM pjm_project_commit_v GROUP BY project_id, task_number, task_name;
  • SELECT cmt_number, vendor_name, cmt_approved_date, cmt_promised_date, acct_exchange_rate FROM pjm_project_commit_v WHERE cmt_approved_flag = 'Y';

Because amounts are returned as formatted character strings via FND_CURRENCY_CACHE, consumers performing arithmetic should account for locale-specific formatting or query the underlying PA_COMMITMENT_TXNS numeric columns directly. Access should be limited to the APPS schema or granted via a synonym and appropriate grants, consistent with standard EBS security practice.