Search Results pa_status_task_cmt_base_v




Overview
Explore in AI Chat

Overview

PA_STATUS_TASK_CMT_BASE_V is an Oracle Applications (APPS) view within the Projects (PA) product family. Its ETRM description is limited to the notation "10SC Only," indicating that the view is a specialized or release-restricted construct rather than a general-purpose commitment reporting interface. It exposes commitment transaction detail at the project and task level, joining commitment lines to task attributes, organization names, and lookup meanings, while relying on the PA_STATUS package to constrain results to the current project and task context.

Functionally, the view presents a flattened, denormalized record set of project commitment transactions. Each row represents a commitment line with its burdened and raw costs, currency conversion attributes, approval and promise dates, and the associated task and organization identifiers. Because the WHERE clause references PA_STATUS.GETPROJID and PA_STATUS.GETTASKID, the view is context-dependent; it returns rows only for the project and task established in the session or calling program. This makes it unsuitable for broad ad hoc reporting without a controlling PL/SQL context, but well suited to embedded logic where the caller has already established project/task scope.

Underlying Base Objects

The view is defined over the following documented base objects:

The joins are inner joins throughout, so a commitment line without a matching task, expenditure accumulation detail, lookup meaning, or organization will not appear in the result set.

Key Columns

The view exposes a wide column set. Project and task identifiers (PROJECT_ID, TASK_ID) anchor the row. TXN_ACCUM_ID ties the commitment to its transaction accumulation detail. Commitment identity is carried by CMT_NUMBER and CMT_LINE_NUMBER. Financial amounts appear in multiple currencies: PROJ_RAW_COST and PROJ_BURDENED_COST for project currency, DENOM_RAW_COST and DENOM_BURDENED_COST for denominated currency, and ACCT_RAW_COST and ACCT_BURDENED_COST for accounting currency, each with corresponding currency codes, rate dates, rate types, and exchange rates. Receipt currency values are provided via RECEIPT_CURRENCY_CODE, RECEIPT_CURRENCY_AMOUNT, and RECEIPT_EXCHANGE_RATE. Dates include EXPENDITURE_ITEM_DATE, CMT_APPROVED_DATE, CMT_PROMISED_DATE, and CMT_NEED_BY_DATE. Descriptive fields include VENDOR_NAME, DESCRIPTION, TASK_NUMBER, TASK_NAME, EXPENDITURE_TYPE, ORGANIZATION_ID, CMT_APPROVED_FLAG, TOT_CMT_QUANTITY, UNIT_OF_MEASURE, CMT_REQUESTOR_NAME, and CMT_BUYER_NAME. Lookup-derived meanings are returned for line type and transaction source, and CMT_REJECTION_CODE and CMT_DISTRIBUTION_ID support downstream processing.

Common Use Cases and Queries

Typical usage is within project commitment inquiry and reporting extensions where the current project and task context has already been established. Because the view filters on PA_STATUS.GETPROJID and PA_STATUS.GETTASKID, it is generally queried from within PL/SQL or a form that sets that context. A representative query follows.

SELECT project_id, task_id, cmt_number, cmt_line_number, vendor_name, cmt_approved_flag, tot_cmt_quantity, unit_of_measure, proj_raw_cost, proj_burdened_cost, acct_raw_cost, acct_burdened_cost, cmt_approved_date, cmt_promised_date, cmt_need_by_date, expenditure_type, task_number, task_name FROM apps.pa_status_task_cmt_base_v ORDER BY task_id, cmt_number, cmt_line_number;

Additional scenarios include reconciling commitment quantities against approved supplier commitments, aggregating burdened cost by expenditure type for a given task, and exporting commitment detail for interface or validation routines. Analysts should note the inner-join behavior and the context dependency before relying on the view for global reporting, and should confirm availability, since the "10SC Only" designation in the ETRM metadata suggests the object may not exist or behave identically in every release.