Results for “hr_s_user_entities”

40 results




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

Overview

HR_S_USER_ENTITIES is a Human Resources (PER) module table within the Oracle E-Business Suite, owned by the HR schema. It is documented in ETRM as a VALID, retrofitted object in both 12.1.1 and 12.2.2. The table records the user-defined entity definitions that the HR security and routing framework uses to associate an employee, applicant, or other system user with a routing entity — commonly leveraged by Oracle Approvals Management and HR security routing logic to determine how transactions flow to the correct approver or reviewer.

Under the heuristic Data Vault classification supplied in the ETRM metadata, HR_S_USER_ENTITIES is treated as a standalone object (i.e., it is not modeled as a dependent satellite of another hub through a composite foreign key chain). In Data Vault terms, it behaves most naturally as a reference/lookup hub: its surrogate primary key, USER_ENTITY_ID, uniquely identifies each user entity definition, while the operational attributes (legislation code, route, name, description) travel alongside it as descriptive properties.

Key Information Stored

The table carries 14 documented physical columns in 12.2.2. The surrogate primary key is USER_ENTITY_ID, which is also the column referenced by the foreign key into FF_USER_ENTITIES. This FK relationship makes FF_USER_ENTITIES the authoritative parent for the entity identity, while HR_S_USER_ENTITIES holds HR-specific context.

  • USER_ENTITY_ID — surrogate primary key; the FK back to FF_USER_ENTITIES.
  • BUSINESS_GROUP_ID — the HR business group (operating unit) that owns the definition; the principal partitioning key in a multi-org HR implementation.
  • LEGISLATION_CODE — the country/legislation under which the entity is valid, driving legislative-specific approval routing.
  • ROUTE_ID — identifies the routing definition applied to the entity, linking to the routing framework used for approval or notification delivery.
  • NOTFOUND_ALLOWED_FLAG — controls whether routing may proceed when the user entity cannot be resolved.
  • USER_ENTITY_NAME — the descriptive business name of the entity definition; a natural business-key candidate alongside BUSINESS_GROUP_ID.
  • ENTITY_DESCRIPTION — free-text description of the entity's purpose.
  • CREATOR_ID / CREATOR_TYPE — the identity and type of the creating party.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle WHO-column audit trail.

Common Use Cases and Queries

The most common reporting need is to resolve which routing entity applies to a given business group and legislation, and whether "not found" conditions are tolerated. A representative query joins the table to its parent:

  • SELECT ue.USER_ENTITY_ID, ue.USER_ENTITY_NAME, ue.LEGISLATION_CODE, ue.ROUTE_ID, ue.NOTFOUND_ALLOWED_FLAG FROM HR.HR_S_USER_ENTITIES ue WHERE ue.BUSINESS_GROUP_ID = :p_bg_id AND ue.LEGISLATION_CODE = :p_leg_code;
  • Join to FF_USER_ENTITIES on USER_ENTITY_ID to reconcile the HR-specific route and legislation attributes against the core entity definition.
  • Audit queries using CREATION_DATE, LAST_UPDATE_DATE and LAST_UPDATED_BY to detect newly configured or recently modified entities.
  • Diagnostic queries filtering on NOTFOUND_ALLOWED_FLAG = 'N' to identify strict routing configurations that block transactions when a user entity cannot be resolved.

Related Objects

  • FF_USER_ENTITIES — parent table; joined via HR_S_USER_ENTITIES.USER_ENTITY_ID = FF_USER_ENTITIES.USER_ENTITY_ID.
  • FND_USER — typically referenced by CREATOR_ID/LAST_UPDATED_BY for audit identification.
  • PER_BUSINESS_GROUPS — provides the business group context for BUSINESS_GROUP_ID.
  • FND_FLEX_VALUES / FND_ID_FLEX_STRUCTURES — relevant where LEGISLATION_CODE derives from a key flexfield value set.
  • HR_S_USER_ENTITY_ROUTES — associated routing detail (where present in the HR security schema).

Because the ETRM metadata classifies the object as standalone with only one documented foreign key, the primary integrity dependency to observe is the FF_USER_ENTITIES relationship; all other associations should be validated against the live data model before being relied upon.