Search Results effort_level_code




Overview
Explore in AI Chat

Overview

APPS.PA_CONTROL_ITEMS_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that exposes the contents of the PA_CONTROL_ITEMS table. Control items represent the action, issue, change, and risk tracking entities used throughout project delivery — records that capture deliverables, follow-up actions, open issues, change requests, and other items requiring monitoring through their life cycle. The view presents these records with a flat, denormalized column list suitable for concurrent program output, Oracle Reports, Oracle Discoverer / Oracle BI Publisher extracts, and third-party integration reads.

Because the view is defined as a simple projection over the base table with no joins, filters, or expressions, it is essentially a synonym-style access layer: any query, report, or interface that references PA_CONTROL_ITEMS_V sees exactly the same rows and columns as PA_CONTROL_ITEMS. The user's search term, PRICE_CURRENCY_CODE, appears explicitly in the view's column list, confirming that monetary context for control items is exposed at this layer.

Underlying Base Objects

The documented base object is PA_CONTROL_ITEMS, referenced through a synonym. The view's SELECT statement lists the base table's columns verbatim, ending with FROM PA_CONTROL_ITEMS. There are no outer joins, no lookup decoding, and no DECODE or CASE logic in the definition — all code columns are returned as raw IDs or codes rather than translated values. Consequently, consumers that need decoded status, priority, classification, or reason descriptions must join to the corresponding PA_LOOKUPS values or to the relevant reference tables themselves.

Key Columns

The view exposes the full column set of the control item, including:

Common Use Cases and Queries

Typical uses include open-item aging reports, project issue dashboards, change-request backlogs, and extraction of control items for data warehousing. A representative query retrieving priced items with their currency follows:

  • SELECT ci_number, summary, status_code, priority_code, price, price_currency_code, date_required
  • FROM apps.pa_control_items_v
  • WHERE project_id = :p_project_id
  •   AND price_currency_code IS NOT NULL
  • ORDER BY date_required;

To count open items by status and currency, the view can be aggregated directly on status_code and price_currency_code. Because no translation is applied, reports requiring descriptive status or priority text should join to the appropriate lookup views. All access should respect the Projects security model, and callers should be aware that the view reads the transaction table in real time.