Results for “orig_system_code”

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

Overview

PA_CONTROL_ITEMS is a transactional table in the Oracle Projects (PA) schema that stores user-defined control items associated with projects. Control items represent issues, action items, change requests, or risks that must be tracked, categorized, and resolved throughout the project lifecycle. Each record belongs to a project (via PROJECT_ID) and is classified by an item type defined in PA_CI_TYPES_B through the CI_TYPE_ID column. Items are further categorized using Classification, Reason, and Priority attributes, enabling structured triage and reporting of project issues.

Functionally, this table supports the Project Issue and Change Management business process. Control items can carry financial impact (through related rows in PA_CI_IMPACTS and PA_BUDGET_VERSIONS), status transitions (via PA_OBJ_STATUS_CHANGES), and comments (via PA_CI_COMMENTS). The heuristic Data Vault classification is satellite-leaning, which suggests this table behaves like a descriptive satellite whose natural parent hub is the project (or the control item itself acting as a business-key hub keyed on CI_ID). Practitioners modeling this data should treat CI_ID as the anchor key and the numerous descriptive and status columns as satellite attributes.

Key Information Stored

The table contains 69 documented columns. The surrogate primary key is CI_ID, enforced by the unique index PA_CONTROL_ITEMS_PK. Two unique indexes identify business-key candidates: PA_CONTROL_ITEMS_U1 (CI_ID) and PA_CONTROL_ITEMS_U2 (ORIGINAL_CI_ID, VERSION_NUMBER), the latter supporting control item versioning and change-request lineage.

• CI_ID — Primary surrogate key uniquely identifying a control item.
• PROJECT_ID — Foreign key to PA_PROJECTS_ALL; the owning project.
• CI_TYPE_ID — Foreign key to PA_CI_TYPES_B; determines the control item type.
• CI_NUMBER — User-facing control item number.
• SUMMARY and DESCRIPTION — Short and long descriptions of the item.
• STATUS_CODE and PROGRESS_STATUS_CODE — Foreign keys to PA_PROJECT_STATUSES; workflow state of the item.
• CLASSIFICATION_CODE_ID, REASON_CODE_ID, PRIORITY_CODE, EFFORT_LEVEL_CODE — Categorization attributes.
• OWNER_ID — Foreign key to HZ_PARTIES; the person responsible for the item.
• DATE_REQUIRED, DATE_CLOSED, CLOSED_BY_ID — Lifecycle dates and closure metadata.
• PRICE and PRICE_CURRENCY_CODE (FK to FND_CURRENCIES) — Monetary value attached to the item.
• ORIGINAL_CI_ID, VERSION_NUMBER, CURRENT_VERSION_FLAG, VERSION_COMMENTS — Versioning lineage for change-controlled items.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — DFF extensibility columns.

Common Use Cases and Queries

Typical scenarios include open issue dashboards, change-request tracking, and impact reporting. A common query pattern joins the table to projects and item types:

• List open control items for a project: SELECT CI_ID, CI_NUMBER, SUMMARY, PRIORITY_CODE FROM PA_CONTROL_ITEMS WHERE PROJECT_ID = :project_id AND STATUS_CODE <> 'CLOSED';
• Current-version change requests: filter on CURRENT_VERSION_FLAG = 'Y' and group by ORIGINAL_CI_ID.
• Owner workload: join OWNER_ID to HZ_PARTIES to report items per assignee.
• Financial exposure: join to PA_CI_IMPACTS and PA_BUDGET_VERSIONS on CI_ID to aggregate cost impact.
• Status history: join to PA_OBJ_STATUS_CHANGES on PCM_CI_ID.

Related Objects

The most significant related tables are linked through documented foreign keys:

• PA_PROJECTS_ALL — via PROJECT_ID; the parent project.
• PA_CI_TYPES_B — via CI_TYPE_ID; item type lookup.
• PA_PROJECT_STATUSES — via STATUS_CODE and PROGRESS_STATUS_CODE.
• HZ_PARTIES — via OWNER_ID, LAST_MODIFIED_BY_ID, and CLOSED_BY_ID.
• PA_CI_ACTIONS, PA_CI_COMMENTS, PA_CI_IMPACTS, PA_CI_SUPPLIER_DETAILS — child tables keyed by CI_ID.
• PA_BUDGET_VERSIONS — via CI_ID; links control items to budget impact.
• PA_OBJECT_RELATIONSHIPS — via OBJECT_ID_TO1 and OBJECT_ID_FROM1.
• PA_OBJ_STATUS_CHANGES — via PCM_CI_ID; status transition history.
• PA_PROJECT_FUNDINGS and PA_FP_MERGED_CTRL_ITEMS — via CI_ID.