Results for “oke_priority_codes_b”

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

Overview

OKE_PRIORITY_CODES_B is a foundational reference table in the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It stores the master definitions of priority codes that govern the ranking, ordering, and processing behavior of contract documents managed within Project Contracts. Priority codes act as controlled lookup values that drive how the application sequences, classifies, and applies business logic to contract headers, deliverables, and related records.

The table is owned by the OKE schema and is present in both EBS 12.1.1 and 12.2.2, where it is documented as VALID. It exposes 25 physical columns and is qualified by a single-column primary key, OKE_PRIORITY_CODES_PK, defined on PRIORITY_CODE. A unique index, OKE_PRIORITY_CODES_U1, also exists on PRIORITY_CODE, confirming that priority code values are unique within the table and function as the business-key candidate, while the primary key serves as the row identifier.

From a Data Vault modeling perspective, the metadata's FK structure classifies this object as hub-leaning. This suggests OKE_PRIORITY_CODES_B behaves primarily as a hub: a canonical list of unique business keys (priority codes) that other tables reference through foreign keys, rather than as a transactional satellite of descriptive history.

Key Information Stored

• PRIORITY_CODE — The primary key and business key. Holds the unique identifier for each priority code and is the column referenced by dependent tables.
• PRIORITY_TYPE_CODE — Classifies the priority code into a category or type, allowing the application to distinguish among different classes of priority behavior.
• START_DATE_ACTIVE — The date on which the priority code becomes active and available for use.
• END_DATE_ACTIVE — The date on which the priority code is retired or expires. Together with START_DATE_ACTIVE it defines the effective period.
• CREATION_DATE, CREATED_BY — Standard audit columns capturing when and by whom the record was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard who-columns recording the most recent modification and session context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Fifteen flexible descriptive (DFF) columns plus a category column that support configurable, site-specific extensions without schema changes.

The audit and descriptive-flexfield columns mirror the standard EBS WHO/DFF column set and should be excluded from any business-key determination. PRIORITY_CODE alone is the meaningful identifier.

Common Use Cases and Queries

Priority codes are typically consumed during contract validation, defaulting, and ordering logic. Report developers frequently join the table to contract headers to resolve human-readable priority descriptions and to filter for currently active codes.

To list active priority codes for a given point in time:

• SELECT priority_code, priority_type_code
FROM oke.oke_priority_codes_b
WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

To resolve priority information for contract headers, join on the PRIORITY_CODE column exposed by OKE_K_HEADERS and its history table:

• SELECT h.header_id, h.priority_code, p.priority_type_code
FROM oke.oke_k_headers h
JOIN oke.oke_priority_codes_b p
ON h.priority_code = p.priority_code;

Common reporting scenarios include auditing the effective-dating of codes, identifying expired priorities still referenced by open contracts, and validating that no header references an inactive or nonexistent code. Because the flexfield attributes are site-configurable, they may also be queried for client-specific reporting not covered by the base columns.

Related Objects

The FK relationship data identifies the principal dependencies on this table:

• OKE_K_HEADERS — The contract headers table; references OKE_PRIORITY_CODES_B via OKE_K_HEADERS.PRIORITY_CODE. This is the primary transactional consumer of priority codes.
• OKE_K_HEADERS_H — The history/audit counterpart of OKE_K_HEADERS, referencing the same table via OKE_K_HEADERS_H.PRIORITY_CODE. It preserves historical priority-code assignments.

These two foreign-key relationships establish OKE_PRIORITY_CODES_B as a referenced hub within the Project Contracts data model. Analysts working with contract headers, their versions, or contract history should account for this table when interpreting priority values, since any code appearing in a header must resolve to a row here. Effective-dating on START_DATE_ACTIVE and END_DATE_ACTIVE should be considered when reconciling historical contract records against the current set of valid quick codes.