Results for “level_code”

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

Overview

PQH_DE_LEVEL_CODES is a Public Sector HR (PQH) configuration table in the Oracle E-Business Suite HR schema. It stores the "level code" definitions used by the Oracle HRMS Public Sector "DE" (data element / defense establishment) component, which governs position level numbering and validation rules for public-sector workforce structures. The table acts as a reference source that downstream validation records consume rather than as a transaction table. Physically, in the documented 12.2.2 schema it resides in the HR schema and contains 11 columns.

In Data Vault modeling terms, the mined foreign-key structure suggests a satellite-leaning classification. The table is keyed on a single surrogate column, LEVEL_CODE_ID, and carries a descriptive attribute (LEVEL_CODE) plus a foreign reference to a level-number parent. This pattern is consistent with an attached satellite that stores the descriptive context of a level-code hub, though it also carries its own parent reference. This is a modeling suggestion only; the physical table should be treated as a standard EBS reference entity.

Key Information Stored

The documented unique index PQH_DE_LEVEL_CODES_PK is defined on LEVEL_CODE_ID, which serves as the surrogate primary key. The remaining significant columns include:

• LEVEL_CODE_ID — the surrogate primary key and the column most commonly used in joins and lookups; it is the value users search for as "level_code_id".
• LEVEL_NUMBER_ID — a foreign key to the level-number parent record (documented FK from PQH_DE_LEVEL_CODES.LEVEL_NUMBER_ID). It groups each level code under a level number.
• LEVEL_CODE — the business-facing code value; a principal business-key candidate for user-facing lookups and reporting.
• DESCRIPTION — the human-readable name or description of the level code.
• GRADUAL_VALUE_NUMBER — a numeric value associated with the level, used in public-sector level or grade calculations.
• OBJECT_VERSION_NUMBER — optimistic locking column maintained by the EBS framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns capturing audit and concurrency context.

The documented business-key candidates are limited to PQH_DE_LEVEL_CODES_PK on LEVEL_CODE_ID; no additional unique index is documented, so LEVEL_CODE should be validated for uniqueness within its LEVEL_NUMBER_ID context before being treated as a natural key.

Common Use Cases and Queries

Typical usage involves resolving a level code into its description and parent level number for reporting, and validating level codes against the parent linkage used in workplace validation. A representative lookup joining the parent number is:

• SELECT lc.level_code_id, lc.level_code, lc.description, lc.gradual_value_number FROM hr.pqh_de_level_codes lc WHERE lc.level_number_id = :p_level_number_id;
• SELECT * FROM hr.pqh_de_level_codes WHERE level_code_id = :p_id; to retrieve a single configured level code.
• Reporting joins to the referencing validation table to confirm that a workplace validation level number points to a valid level code.

Because the table is small and configuration-driven, it is frequently used as a lookup source in concurrent programs, value-set queries, and extract scripts that populate downstream public-sector position and workplace records.

Related Objects

The documented relationships identify the principal dependent and parent objects:

• PQH_DE_WRKPLC_VLDTN_LVLNUMS — references this table via LEVEL_CODE_ID (PQH_DE_WRKPLC_VLDTN_LVLNUMS.LEVEL_CODE_ID → PQH_DE_LEVEL_CODES); the most significant dependent table.
• PQH_DE_LEVEL_CODES.LEVEL_NUMBER_ID — the parent reference column linking each level code to its level number record.
• PQH_DE_LEVEL_CODES_PK — the primary key index on LEVEL_CODE_ID that enforces uniqueness and supports joins.

Additional Public Sector HR (PQH_DE_*) tables that share the level-number or level-code domain should be reviewed in the same schema when building extracts, as they commonly join through LEVEL_CODE_ID or LEVEL_NUMBER_ID.