Search Results hz_work_class_u1

Overview

The AR.HZ_WORK_CLASS table is a transaction-data table in the Oracle E-Business Suite (EBS) Trading Community Architecture (TCA) model, owned by the AR (Receivables) schema. It stores user-defined classification information describing the job title and work experience associated with a person's employment history. Because the TCA model permits a single employment history record to carry multiple distinct work classifications, the table is designed to hold one or more rows for each corresponding record in HZ_EMPLOYMENT_HISTORY. The flexibility of the design allows different implementations to represent classifications in whatever manner suits their business: one organization might use values such as "Electrician" and "Master," while another might encode the same concept as job codes and seniority indicators (for example, "EM3" and "over 20"). The object is registered in FND Design Data as AR.HZ_WORK_CLASS and holds a VALID status in both 12.1.1 and 12.2.2.

From a heuristic Data Vault modeling perspective—derived from the foreign key topology—this object is classified as satellite-leaning. It carries descriptive, non-key attributes about a parent entity (employment history), which is consistent with the role of a satellite rather than a hub or link.

Key Information Stored

The primary key is WORK_CLASS_ID, a NUMBER(15) surrogate identifier for a given class of work. The unique index HZ_WORK_CLASS_U1, defined as a NORMAL, UNIQUE index on WORK_CLASS_ID in tablespace APPS_TS_TX_IDX, confirms this column as the business-key candidate and the enforced uniqueness constraint. The core descriptive columns are WORK_CLASS_NAME (VARCHAR2(240)), the user-determined classification such as "bricklayer," "doctor," or "programmer"; and LEVEL_OF_EXPERIENCE (VARCHAR2(60)), a user-defined experience rating such as "journeyman," "trainee," or "exposure."

Relationship integrity is maintained through EMPLOYMENT_HISTORY_ID (NUMBER(15)), a foreign key to HZ_EMPLOYMENT_HISTORY. Standard WHO and concurrent-program audit columns are present: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and REQUEST_ID. The documented schema for 12.2.2 lists 18 columns total, including additional concurrency and program-tracking columns.

Common Use Cases and Queries

This table is typically queried to retrieve and report on the work classifications tied to a person's employment history—supporting HR analytics, resource-skill reporting, and TCA person profile screens. A common pattern joins the satellite to its parent:

• Retrieve all classes for a given employment history: SELECT WORK_CLASS_NAME, LEVEL_OF_EXPERIENCE FROM AR.HZ_WORK_CLASS WHERE EMPLOYMENT_HISTORY_ID = :p_id;
• Join to the parent to resolve the person and classification: SELECT eh.PERSON_ID, wc.WORK_CLASS_NAME, wc.LEVEL_OF_EXPERIENCE FROM AR.HZ_WORK_CLASS wc JOIN AR.HZ_EMPLOYMENT_HISTORY eh ON wc.EMPLOYMENT_HISTORY_ID = eh.EMPLOYMENT_HISTORY_ID;
• Lookup by primary key using the unique index: SELECT * FROM AR.HZ_WORK_CLASS WHERE WORK_CLASS_ID = :id;

Related Objects

• AR.HZ_EMPLOYMENT_HISTORY — parent table; joined on HZ_WORK_CLASS.EMPLOYMENT_HISTORY_ID = HZ_EMPLOYMENT_HISTORY.EMPLOYMENT_HISTORY_ID.
• FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN.
• HZ_WORK_CLASS_PK — primary key constraint on WORK_CLASS_ID.
• HZ_WORK_CLASS_U1 — the unique index supporting the primary key.