Search Results commitment_need_by_date




Overview
Explore in AI Chat

Overview

APPS.PABV_COMMITMENTS is a read-only Oracle EBS view that exposes project commitment transaction lines for reporting and integration purposes. It is defined in the Projects (PA) module and is primarily consumed by Oracle Subledger Accounting (SLA) and by ETRM-based reporting for commitment (encumbrance) accounting. The view is a join of PA_COMMITMENT_TXNS and PA_PROJECTS_ALL, filtered so that only commitments for projects with a non-null operating unit (ORG_ID) are returned. Because the view carries the "WITH READ ONLY" clause, it cannot be used for DML; it is strictly a query object.

The naming convention (PABV) indicates a "Business View" published for external or downstream consumption rather than for internal product logic. The user query "dev committed" maps to this object in the sense of "committed costs" viewable at the development/commitment level, where commitment lines represent purchase requisition, purchase order, or other commitment transactions associated with a project and task.

Underlying Base Objects

Two base tables, referenced as APPS synonyms, underlie the view:

  • PA_COMMITMENT_TXNS — the primary commitment transaction table storing one row per commitment line (CMT_LINE_ID), with raw, burdened, and quantity amounts by currency and rate type.
  • PA_PROJECTS_ALL — the projects table supplying project-level context and the ORG_ID used for security filtering.

The join is on PC.PROJECT_ID = PPA.PROJECT_ID, and the view enforces row-level security through the predicate on PPA.ORG_ID, which restricts rows to the operating unit(s) accessible to the querying user. The view therefore inherits the referential relationship between a commitment line and its parent project.

Key Columns

Common Use Cases and Queries

The view is used to report committed costs against projects for encumbrance and budget-versus-commitment analysis, to feed SLA commitment accounting, and to reconcile commitment totals with expenditure transactions. A basic query retrieving commitment lines for a specific project follows:

  • SELECT cmt_number, cmt_line_number, transaction_source, tot_cmt_raw_cost, tot_cmt_burdened_cost, tot_cmt_quantity, cmt_approved_flag, expenditure_item_date FROM apps.pabv_commitments WHERE project_id = :p_project_id ORDER BY cmt_creation_date;
  • SELECT project_id, task_id, expenditure_type, SUM(tot_cmt_burdened_cost) FROM apps.pabv_commitments WHERE cmt_approved_flag = 'Y' GROUP BY project_id, task_id, expenditure_type;
  • SELECT * FROM apps.pabv_commitments WHERE cmt_need_by_date BETWEEN :p_from_date AND :p_to_date;

Because the view applies an ORG_ID security predicate, results are automatically constrained to the operating units available to the session. This makes the view suitable for direct use in concurrent report programs and BI Publisher data models without additional org-level security logic. The "WITH READ ONLY" behavior ensures the object is used exclusively for inquiry and reporting, not for transactional updates.