Results for “cmt_line_number”

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

Overview

GMS_COMMITMENT_TXNS_V is a Grants Accounting (GMS) reporting view owned by the APPS schema. The view consolidates outstanding project-related commitment costs, giving grant administrators and project accountants a single, denormalized source for encumbrance and obligation data tied to sponsored projects. Because commitments represent purchase requisitions, purchase orders, and other pre-invoice obligations, the view is central to funds-availability analysis, award budget monitoring, and period-end commitment reporting.

The view is defined as a UNION ALL of two underlying sources: the primary commitment transaction stream and the override stream exposed through GMS_COMMITMENTS_OVERRIDE_V. This union lets the view surface both standard commitment records and manually overridden commitment values without the caller needing to reconcile them separately. Columns are largely sourced from Oracle Purchasing and Projects commitment tables, with currency amounts wrapped by PA_CURRENCY.ROUND_CURRENCY_AMT to enforce project accounting round-off conventions.

Underlying Base Objects

The documented metadata lists a broad set of referenced objects rather than a single base table, reflecting the computed nature of the view. Key dependencies include:

• GMS_COMMITMENTS_OVERRIDE_V (VIEW) — the second leg of the union, supplying overridden commitment rows.
• GMS_ENC_PSI_V (VIEW) — encumbrance/project-summary detail.
• PA_CURRENCY, PA_MULTI_CURRENCY — currency conversion and rounding routines applied to raw, burdened, denominated, and receipt amounts.
• PA_BURDEN_CMTS, PA_CMT_UTILS, PA_ACCUM_UTILS — burdening and commitment accumulation logic.
• PA_EXPENDITURE_TYPES, PA_COST_BASE_EXP_TYPES, PA_IND_COST_CODES, PA_IND_COMPILED_SETS, PA_COMPILED_MULTIPLIERS — expenditure type, cost code, and indirect-cost multiplier resolution.
• PA_FUNDS_CONTROL_UTILS, PA_TASK_UTILS, PA_PJC_CWK_UTILS, PA_UTILS4 — funds control and task/project utility logic.
• AP_INVOICES_PKG, HR_GENERAL, HR_SECURITY, FND_PROFILE, GMS_COST_PLUS_EXTN — invoicing, security, profile, and extension hooks.

Because these are packages, synonyms, and views rather than a single physical table, the view is effectively a computed reporting layer over the Projects commitment engine.

Key Columns

• CMT_HEADER_ID / CMT_DISTRIBUTION_ID — the commitment header and distribution identifiers; CMT_HEADER_ID is the value most commonly used for lookups and joins back to Purchasing documents.
• CMT_NUMBER, CMT_LINE_NUMBER — human-readable commitment document and line references.
• PROJECT_ID, TASK_ID — project and task context for the commitment.
• TRANSACTION_SOURCE, LINE_TYPE, SYSTEM_LINKAGE_FUNCTION — classify the origin and nature of the transaction.
• EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, REVENUE_CATEGORY — cost classification for reporting.
• ACCT_RAW_COST, ACCT_BURDENED_COST, DENOM_RAW_COST, DENOM_BURDENED_COST — rounded raw and burdened costs in accounted and denominated currency.
• QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_INVOICED, QUANTITY_OUTSTANDING_DELIVERY, QUANTITY_OUTSTANDING_INVOICE, QUANTITY_CANCELLED, QUANTITY_OVERBILLED — lifecycle quantities with matching amount columns.
• CMT_APPROVED_FLAG, CMT_APPROVED_DATE, CMT_PROMISED_DATE, CMT_NEED_BY_DATE — approval and scheduling attributes.
• VENDOR_ID, VENDOR_NAME, ORGANIZATION_ID — supplier and inventory organization context.
• ACCT_CURRENCY_CODE, DENOM_CURRENCY_CODE, RECEIPT_CURRENCY_CODE plus exchange rate columns — multi-currency support.

Common Use Cases and Queries

Typical scenarios include outstanding commitment reporting by project/award, funds-availability checks before new requisitions, and reconciliation of ordered versus invoiced quantities. A query keyed on CMT_HEADER_ID — the term searched — is common when tracing a specific commitment document.

SELECT cmt_header_id, cmt_number, project_id, task_id,
       expenditure_type, acct_raw_cost, acct_burdened_cost,
       quantity_ordered, quantity_invoiced
FROM   apps.gms_commitment_txns_v
WHERE  cmt_header_id = :p_cmt_header_id;

SELECT project_id, task_id, expenditure_type,
       SUM(acct_burdened_cost) outstanding_cost
FROM   apps.gms_commitment_txns_v
WHERE  cmt_approved_flag = 'Y'
GROUP  BY project_id, task_id, expenditure_type;

Because security and profile checks are embedded via HR_SECURITY and FND_PROFILE, results are naturally filtered according to the operating unit and security context of the querying user.