Search Results commitment_line_number




Overview
Explore in AI Chat

Overview

PABV_COMMITMENTS is a read-only Oracle EBS view owned by the APPS schema in the Projects (PA) module. The ETRM metadata lists its description simply as "Retrofitted," indicating the object was regenerated during a prior upgrade cycle rather than purpose-built for a single release. Functionally, the view presents commitment transaction line detail drawn from the Projects commitment ledger, joined to project-level information so that commitment records can be reported with the organizational context required by Multi-Org security.

The view exists to expose commitment data in a denormalized, reporting-friendly shape. It carries the operative field COMMITMENT_NUMBER (mapped internally from CMT_NUMBER), together with approved dates, promised dates, need-by dates, quantities, and raw, burdened, and denominated cost amounts in receipt, denominated, accounting, and project currencies. Because the join to PA_PROJECTS_ALL is enforced and the security predicate on the project organization identifier is required to be non-null, the view returns only commitments belonging to projects visible to the querying responsibility. This makes it suitable for both ad hoc reporting and as a source for integrations that require commitment visibility without reading the transaction table directly.

Underlying Base Objects

The view is defined over exactly two documented base objects, both referenced as synonyms in the APPS schema:

  • PA_COMMITMENT_TXNS (aliased PC) — the commitment transaction table supplying line identifiers, commitment numbers, dates, cost and quantity measures, currency attributes, expenditure type, organization, and distribution information.
  • PA_PROJECTS_ALL (aliased PPA) — the project definition table joined on PROJECT_ID, supplying the organization identifier used for operating-unit security.

The join condition is PC.PROJECT_ID = PPA.PROJECT_ID, combined with a security predicate that requires the project organization identifier to be non-null. The view is declared WITH READ ONLY, so no DML may be issued against it. Several columns are surfaced through Oracle lookups dynamically, resolved at runtime against PA_LOOKUPS and FND_LOOKUPS, which means displayed values reflect the language and lookup configuration of the session rather than stored codes.

Key Columns

Common Use Cases and Queries

Typical uses include commitment reporting by project and task, auditing pending or approved commitments, reconciliation of commitments to budgets, and extracts feeding external cost or procurement systems. Because the security predicate is embedded, queries automatically restrict to accessible operating units.

Retrieving a commitment by number:

SELECT commitment_number, commitment_line_number, raw_cost,
       burdened_cost, commitment_approved_date, project_id
  FROM apps.pabv_commitments
 WHERE commitment_number = :p_commitment_number;

Commitments by project and expenditure type:

SELECT project_id, expenditure_type, commitment_number,
       raw_cost, acct_raw_cost, commitment_need_by_date
  FROM apps.pabv_commitments
 WHERE project_id = :p_project_id
   AND expenditure_type = :p_expenditure_type
 ORDER BY commitment_need_by_date;

Because the view is read-only and resolves lookups at query time, it should not be used in update logic; instead, changes are applied to PA_COMMITMENT_TXNS and reflected automatically on subsequent queries.