Results for “level_code_id”

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

Overview

PQH_DE_WRKPLC_VLDTN_LVLNUMS is a transactional table owned by the HR schema within the PQH (Public Sector HR) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description, "DE - Workplace Validation Level Numbers," identifies it as the repository that links a workplace validation version to the specific level numbers and level codes required during validation processing. The object carries a VALID status in the ETRM data dictionary and exposes eleven columns in the documented 12.2.2 physical schema.

From a dimensional-modeling perspective, the relationship metadata classifies this object as satellite-leaning. This is a heuristic suggestion rather than a declarative property: the table holds a single-column surrogate primary key plus descriptive and foreign-key attributes that qualify a parent record, which is characteristic satellite behavior. Under Data Vault 2.0 conventions it would typically be modeled as a satellite hung off PQH_DE_WRKPLC_VLDTN_VERS, with the level and code references resolved as links or lookups.

Key Information Stored

The surrogate primary key is WRKPLC_VLDTN_LVLNUM_ID, backed by the unique index PQH_DE_WRKPLC_VLDTN_LVLNUMS_PK. No additional unique indexes are documented, so there is no separate multi-column business key; the surrogate is the only documented candidate in the provided metadata.

• WRKPLC_VLDTN_LVLNUM_ID — surrogate primary key, uniquely identifying each row.
• WRKPLC_VLDTN_VER_ID — foreign key to PQH_DE_WRKPLC_VLDTN_VERS, anchoring the row to a specific workplace validation version.
• LEVEL_NUMBER_ID — foreign key to PQH_DE_LEVEL_NUMBERS, identifying the level number validated within the version.
• LEVEL_CODE_ID — foreign key to PQH_DE_LEVEL_CODES, identifying the associated level code.
• BUSINESS_GROUP_ID — multitenancy discriminator segregating rows by business group.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO-column audit trail.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications Framework to detect concurrent updates.

Together these columns define which level numbers and codes are in scope for a given workplace validation version, with the version foreign key providing the principal grouping.

Common Use Cases and Queries

The most common access pattern is resolving the level configuration for a workplace validation version. A typical join retrieves the level numbers and codes associated with a version:

• Listing all level-number rows for one workplace validation version, filtered on WRKPLC_VLDTN_VER_ID and BUSINESS_GROUP_ID.
• Joining to PQH_DE_LEVEL_NUMBERS and PQH_DE_LEVEL_CODES to produce a readable validation report of level numbers and their codes.
• Reconciling the validation version definition against the level setup during configuration or upgrade validation in 12.1.1 and 12.2.2.
• Auditing change history through LAST_UPDATE_DATE and LAST_UPDATED_BY, or detecting stale rows via OBJECT_VERSION_NUMBER.

A representative query pattern selects WRKPLC_VLDTN_LVLNUM_ID, WRKPLC_VLDTN_VER_ID, LEVEL_NUMBER_ID, and LEVEL_CODE_ID from this table and joins to PQH_DE_WRKPLC_VLDTN_VERS on WRKPLC_VLDTN_VER_ID, to PQH_DE_LEVEL_NUMBERS on LEVEL_NUMBER_ID, and to PQH_DE_LEVEL_CODES on LEVEL_CODE_ID, always constrained by BUSINESS_GROUP_ID for multitenancy. Analysts typically wrap this in a reporting view rather than querying the base table directly.

Related Objects

• PQH_DE_WRKPLC_VLDTN_VERS — parent table; joined on WRKPLC_VLDTN_VER_ID and the documented foreign key for this relationship.
• PQH_DE_LEVEL_NUMBERS — lookup; joined on LEVEL_NUMBER_ID.
• PQH_DE_LEVEL_CODES — lookup; joined on LEVEL_CODE_ID.
• PQH_DE_WRKPLC_VLDTN_LVLNUMS_PK — the primary key index enforcing uniqueness of WRKPLC_VLDTN_LVLNUM_ID.
• HR schema WHO-column conventions — FND-standard audit columns shared across all EBS transactional tables.

Because the metadata documents no additional dependent tables or public APIs, dependencies beyond the three foreign-key targets and the primary key index should be verified against the specific 12.1.1 or 12.2.2 instance before being relied upon.