Search Results requestor_name




Overview
Explore in AI Chat

Overview

The view APPS.PJM_REQ_COMMITMENTS_STUB_V is a component of the Oracle Project Manufacturing (PJM) module delivered with Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose project-related purchase requisition distribution information for non-project manufacturing customers. In other words, the view is a compatibility or placeholder construct: it supplies the column interface and naming conventions expected by PJM reporting and integration logic, but it is intentionally defined to return no rows for organizations that do not use the Project Manufacturing functionality.

The presence of the _STUB_V suffix is significant. Oracle frequently deploys stub views to satisfy dependencies in forms, concurrent programs, or APIs that reference a fixed column list, while deferring the actual data retrieval to a customer-specific or product-specific implementation. For project manufacturing customers, the corresponding real view is populated from requisition distribution and commitment data; for others, this stub preserves object validity and prevents compilation or runtime errors.

Underlying Base Objects

According to the documented metadata, the view is defined exclusively over the synonym PA_IMPLEMENTATIONS_ALL, which resolves to the Oracle Projects implementation table. This is a conventional Oracle technique: the stub selects literal padding strings and typed NULL values from PA_IMPLEMENTATIONS_ALL while imposing the predicate WHERE 1 = 2. Because the predicate is always false, the query returns zero rows regardless of how many project implementation records exist.

  • PA_IMPLEMENTATIONS_ALL — the only referenced base object; used solely as a valid FROM clause source so the view can be created and validated.
  • Predicate 1 = 2 — guarantees an empty result set, confirming the stub nature of the view.
  • Literal padding — each column is represented by RPAD('*', n, ' ') or TO_NUMBER(NULL)/TO_DATE(NULL), preserving the exact data type and width of the expected column definitions.

Because no requisition, commitment, or project transaction table is joined, the view carries no transactional data of its own.

Key Columns

The column list mirrors the requisition distribution interface and is dominated by fields familiar to purchasing and projects users. The column REQ_LINE — the term for which the user searched — represents the requisition line number within the requisition header. Supporting attributes include:

Common Use Cases and Queries

The principal use case is diagnostic. A developer or DBA investigating a requisition-related commitment report can query the view to confirm that the stub is active and returning no data, which distinguishes a "no data because the feature is not implemented" condition from a genuine extraction failure. A typical verification query is:

  • SELECT COUNT(*) FROM apps.pjm_req_commitments_stub_v; — expected result is zero.
  • SELECT req_number, req_line, project_number, task_number, amount FROM apps.pjm_req_commitments_stub_v WHERE req_line IS NOT NULL; — returns no rows, confirming the stub predicate.
  • SELECT text FROM all_views WHERE view_name = 'PJM_REQ_COMMITMENTS_STUB_V'; — retrieves the defining SQL for audit purposes.

Integrations that reference REQ_LINE and the other columns listed above should be reviewed carefully: if a report is configured to read from this view and the organization is not a project manufacturing customer, the empty result is by design rather than an error. Where actual requisition commitment data is required, the appropriate source is the underlying purchasing and projects commitment tables, not this stub. The view should therefore be treated as an interface contract rather than a reporting source.