Results for “eng_change_priorities”

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

Overview

ENG_CHANGE_PRIORITIES is an Engineering (ENG) module reference table that stores the valid priority classifications available for engineering change orders (ECOs) within Oracle E-Business Suite. Each row defines a named priority that can be assigned to an engineering change, allowing engineering organizations to rank and sequence change requests according to business urgency, regulatory deadlines, or manufacturing impact. Because priorities are defined per organization, the table supports multi-organization deployments in which each inventory organization maintains its own priority scheme.

From a dimensional modeling perspective, the heuristic Data Vault classification for this table is hub-leaning. This suggests the table behaves primarily as a hub entity whose business key — the combination of priority code and organization — uniquely identifies each priority definition, with descriptive and control attributes attached around it. It is a low-volume, slowly changing reference table rather than a transactional or association table.

Key Information Stored

The table contains 31 documented columns in the 12.2.2 physical schema. The most significant are:

• ENG_CHANGE_PRIORITY_CODE — the user-visible business identifier for the priority (for example, a code representing "High" or "Critical"). Together with ORGANIZATION_ID it forms the surrogate primary key ENG_CHANGE_PRIORITIES_PK.
• ORGANIZATION_ID — the inventory organization that owns the priority definition. This column is part of both the primary key and the unique index, confirming organization-level partitioning of priority codes.
• DESCRIPTION — the descriptive text presented to users when selecting a priority on an engineering change.
• PRIORITY_LEVEL — the numeric or ordinal ranking used to sort and compare priorities during reporting and approval routing.
• DISABLE_DATE — the date on which a priority becomes inactive and is no longer selectable for new engineering changes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified the record and when.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard flexible descriptive flexfield columns reserved for customer-specific extensions.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns identifying the process that last touched the row.
• ZD_EDITION_NAME — the editioning column introduced in the 12.2 online patching architecture, which participates in the unique index ENG_CHANGE_PRIORITIES_U1 alongside the priority code and organization identifier.

The surrogate primary key is ENG_CHANGE_PRIORITIES_PK over (ENG_CHANGE_PRIORITY_CODE, ORGANIZATION_ID). The unique index ENG_CHANGE_PRIORITIES_U1 over (ENG_CHANGE_PRIORITY_CODE, ORGANIZATION_ID, ZD_EDITION_NAME) represents the business-key candidate that enforces uniqueness across editions.

Common Use Cases and Queries

Typical usage centers on listing and validating the priorities available to a given organization. A common query lists active priorities ordered by rank:

• SELECT eng_change_priority_code, description, priority_level FROM eng.eng_change_priorities WHERE organization_id = :org_id AND (disable_date IS NULL OR disable_date > SYSDATE) ORDER BY priority_level.
• Joining to engineering changes to count ECOs by priority: SELECT p.description, COUNT(*) FROM eng.eng_change_priorities p, eng.eng_engineering_changes c WHERE c.priority_code = p.eng_change_priority_code AND c.organization_id = p.organization_id GROUP BY p.description.
• Validating that a priority code is defined before assignment during ECO entry or interface loading.

Reporting use cases include aging and workload analysis by priority level, identifying disabled or obsolete priorities that remain referenced by open changes, and auditing changes to priority definitions through the audit columns.

Related Objects

The primary dependent object is ENG_ENGINEERING_CHANGES, which references this table through PRIORITY_CODE and ORGANIZATION_ID. Additional significant related objects include:

• ENG_ENGINEERING_CHANGES — carries PRIORITY_CODE and ORGANIZATION_ID as foreign keys into this table; this is the principal consumer of priority definitions.
• ENG_ECO_PRIORITIES / related ECO setup views — commonly expose priority values for entry and validation in the Engineering workbench.
• FND_LOOKUP_VALUES — frequently used alongside for other ECO classification values; not a hard foreign key, but commonly reported together.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — provide the ORGANIZATION_ID context that scopes each priority definition.
• FND_CONCURRENT_PROGRAMS — joins through PROGRAM_ID / PROGRAM_APPLICATION_ID to identify the concurrent process responsible for the last update.

Because foreign keys strictly flow outward from ENG_ENGINEERING_CHANGES, ENG_CHANGE_PRIORITIES should be treated as a stable reference dimension in any reporting model, joined on both priority code and organization identifier.