Results for “occ_code”

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

Overview

GHR_MASS_TRANSFER_CRITERIA is a table owned by the HR schema within the GHR — US Federal Human Resources product family. It stores the additional selection criteria associated with a mass transfer action. In the context of Oracle EBS 12.1.1 and 12.2.2, mass transfer functionality allows a set of employees to be moved between organizational units, positions, or assignment structures in a single administrative action; this table captures the filter conditions that refine which records are included in that action beyond the primary parameters held on the parent record.

From a dimensional modeling perspective, the ETRM metadata classifies this object as satellite-leaning based on its foreign key structure. This is a modeling suggestion rather than a physical designation: the table carries descriptive, action-specific attributes that contextualize a parent entity, and it depends on a single parent through a foreign key. It is therefore best understood as a child detail table, or satellite, of the mass transfer header rather than an independent hub or a many-to-many link.

Key Information Stored

The documented physical schema contains eight columns. The most significant are:

• MASS_TRANSFER_CRITERIA_ID — the surrogate primary key, enforced by the GHR_MASS_TRANSFER_CRITERIA_PK unique index. This is the system-generated identifier for an individual criterion row.
• MASS_TRANSFER_ID — the foreign key referencing GHR_MASS_TRANSFERS. This column ties each criterion back to its parent mass transfer action and is the principal join path for reporting.
• OCC_CODE — the occupational code criterion, used in US Federal HR to restrict the transfer population to one or more occupations. This is the only business-domain attribute column documented for the table; the remaining columns are standard WHO/audit fields.
• LAST_UPDATE_DATE, CREATION_DATE — standard Oracle Applications date stamps recording when the row was created and last modified.
• CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns identifying the application user and login session responsible for the insert and most recent update.

The only unique index documented is the primary key index on MASS_TRANSFER_CRITERIA_ID. No separate business-key unique index is documented, which indicates that the natural business identity of a criterion is the combination of its parent mass transfer and the occupational code it carries, rather than a single standalone business identifier column.

Common Use Cases and Queries

Typical usage centers on auditing and reproducing mass transfer actions: verifying which occupational codes were applied as filters, reconciling the population affected by a transfer, and validating that no unintended criteria were retained on a saved action.

A representative query joining criteria to their parent mass transfer:

• SELECT c.mass_transfer_criteria_id, c.mass_transfer_id, c.occ_code, c.creation_date, c.created_by FROM hr.ghr_mass_transfer_criteria c WHERE c.mass_transfer_id = :p_mass_transfer_id;

Aggregate reporting to count criteria per action, useful when auditing how finely transfers were scoped:

• SELECT mass_transfer_id, COUNT(*) criteria_count, COUNT(DISTINCT occ_code) occ_count FROM hr.ghr_mass_transfer_criteria GROUP BY mass_transfer_id;

Because the table is a detail table, no direct concurrent program or public API is documented for it; inserts and updates normally occur through the mass transfer application flow, and direct DML should be restricted to controlled data-fix scenarios.

Related Objects

The following objects are the most significant in relation to GHR_MASS_TRANSFER_CRITERIA:

• GHR_MASS_TRANSFERS — the parent table, referenced through GHR_MASS_TRANSFER_CRITERIA.MASS_TRANSFER_ID. This is the mandatory join for any meaningful query against the criteria table.
• GHR_MASS_TRANSFER_CRITERIA_PK — the primary key index on MASS_TRANSFER_CRITERIA_ID, used for direct row lookups.
• PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F — the assignment and person tables typically evaluated against the recorded occupational code criteria during transfer processing.
• HR_ORGANIZATION_UNITS and PER_JOBS — organizational and job reference objects commonly joined to interpret the scope of a transfer action.
• FND_USER — the standard audit lookup for CREATED_BY and LAST_UPDATED_BY.

Together these objects support tracing a mass transfer from its header, through its selection criteria, to the employee population ultimately affected.