Results for “source_organization”

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

Overview

PA_CONTROL_ITEMS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered under the Projects (PA) product family. It exposes the attribute values of Control Items — the tracked issues, risks, action items, and change items managed through the Project Management control-item functionality. Control items are the structured records that project managers use to record, assign, track, and close outstanding items against a project, and each record carries a substantial set of descriptive, status, ownership, classification, and scheduling attributes.

The view is defined as a straightforward projection over the PA_CONTROL_ITEMS base entity, published for read access by reporting tools, concurrent programs, and external integrations. It is a documented, VALID object in ETRM for both 12.1.1 and 12.2.2, with the same column signature in each release. Because it is a view rather than a table, it carries no independent storage and no autonomous validation; it reflects the current committed state of the underlying control-item records at query time.

Typical consumers include Oracle Projects reporting, Oracle Discoverer or BI Publisher reports, and custom interfaces that need to read control-item detail without touching the base table directly.

Underlying Base Objects

The documented referenced base object is PA_CONTROL_ITEMS, accessed through a synonym in the APPS schema. The view text consists of a single SELECT projecting an explicit, ordered column list from that table, with no joins, unions, filters, or aggregation. Consequently:

• There is a one-to-one row correspondence between PA_CONTROL_ITEMS_V and PA_CONTROL_ITEMS; every control item appears exactly once.
• All columns are inherited directly from the base table without transformation, renaming, or derivation.
• Row-level security, business rules, and workflow state transitions are enforced by the control-item application logic against the base table, not by the view.
• Because no WHERE clause is applied, the view returns all control items across all projects visible to the querying user under standard APPS data privileges.

Key Columns

• CI_ID — Primary identifier of the control item; the join key to the base table and to related control-item children.
• HIGHLIGHTED_FLAG — The value commonly searched for against this view. It marks a control item as highlighted, allowing reports and lists to surface items requiring elevated visibility or attention.
• CI_TYPE_ID — Identifies the control-item type (for example issue or action item), governing which attributes are meaningful.
• CI_NUMBER — User-facing control-item number used in correspondence and search.
• STATUS_CODE / PROGRESS_STATUS_CODE / PROGRESS_AS_OF_DATE — Lifecycle status and the effective date of the reported progress.
• PROJECT_ID — The project against which the item is raised.
• OWNER_ID, CLOSED_BY_ID, CREATED_BY, LAST_UPDATED_BY — Party and user references for ownership and audit.
• SUMMARY / DESCRIPTION / STATUS_OVERVIEW / RESOLUTION — Free-text content for the item narrative and its resolution.
• CLASSIFICATION_CODE_ID, REASON_CODE_ID, RESOLUTION_CODE_ID, PRIORITY_CODE, EFFORT_LEVEL_CODE — Lookup and classification values used for categorization and filtering.
• DATE_REQUIRED, DATE_CLOSED — Target and actual closure dates.
• PRICE, PRICE_CURRENCY_CODE — Financial impact where the item carries a monetary amount.
• SOURCE_TYPE_CODE, SOURCE_NUMBER, SOURCE_DATE_RECEIVED, SOURCE_ORGANIZATION, SOURCE_PERSON, SOURCE_COMMENT — Provenance of the item from its originating source.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The DFF flexfield segment values.
• RECORD_VERSION_NUMBER, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_TYPE, OBJECT_ID — Concurrency, audit, and polymorphic association columns.

Standard audit and WHO columns are maintained by the base table and are available for filtering and incremental extracts.

Common Use Cases and Queries

Because the view is unfiltered, most production queries apply predicates to restrict scope. The highlighted-flag use case is the most direct:

SELECT ci_number, project_id, summary, status_code, owner_id, date_required
FROM apps.pa_control_items_v
WHERE highlighted_flag = 'Y'
ORDER BY project_id, date_required;

Reporting on open items by project and priority is equally common:

SELECT project_id, ci_number, priority_code, status_code, progress_as_of_date
FROM apps.pa_control_items_v
WHERE status_code NOT IN ('CLOSED','CANCELLED')
AND project_id = :p_project_id;

Integrations typically extract incrementally using the audit columns, for example restricting by LAST_UPDATE_DATE to retrieve records changed since the prior run, and selecting the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 columns to propagate descriptive flexfield data. Analysts should note that the view imposes no additional predicates, so any row-scoping, project-security filtering, or business-status exclusions must be written explicitly in the calling query.