Search Results time_entry_rule_group_name

Overview

APPS.HXC_TIME_ENTRY_RULE_GROUPS_V is a reporting and integration view in Oracle E-Business Suite that exposes Time Entry Rule Groups as defined within the Oracle Time and Labor (OTL) / Time and Labor Engine data model. In ETRM terminology, a "Time Entry Rule Group" is a named grouping of time entry rules used to control how timecards are captured, validated, and processed. The view is defined in the APPS schema and is intended for read-only consumption by reports, concurrent programs, interfaces, and integration components that must identify and reference these rule groups without directly accessing the underlying entity model.

The view is a simple, denormalized projection over a single base table. It does not perform joins, aggregation, or filtering beyond a fixed predicate restricting rows to a specific entity type. Its primary value is therefore abstraction: it presents a stable, human-readable name (TIME_ENTRY_RULE_GROUP_NAME) and a surrogate identifier (TIME_ENTRY_RULE_GROUP_ID) alongside standard Oracle EBS auditing and concurrency columns, allowing consumers to avoid embedding the filtering semantics of the base entity-group table into their own SQL. Because the view is owned by APPS and defined over a synonym, it is grantable to other schemas and usable across the standard EBS reporting stack.

Underlying Base Objects

The view is defined over the base object HXC_ENTITY_GROUPS, which is referenced in the documented metadata as a synonym. HXC_ENTITY_GROUPS is a generic entity-grouping table in the HXC (Time and Labor) schema family; it stores groups of entities of many different kinds, discriminated by the ENTITY_TYPE column. The view applies the fixed filter:

• WHERE heg.entity_type = 'TIME_ENTRY_RULES'

Consequently, every row returned by APPS.HXC_TIME_ENTRY_RULE_GROUPS_V corresponds to exactly one row in HXC_ENTITY_GROUPS whose entity type identifies it as a Time Entry Rule group. The view is a pure selection-and-rename projection: no columns are computed, and no other tables are joined. The HEG.ROWID is exposed as ROW_ID, preserving the physical row identifier of the underlying record, which can be useful for direct-row access or diagnostic purposes. Other entity types stored in the same base table are intentionally excluded, so the view is not a general-purpose entity-group listing.

Key Columns

The view exposes the following columns:

• ROW_ID — the ROWID of the underlying HXC_ENTITY_GROUPS row, providing a physical locator for the record.
• TIME_ENTRY_RULE_GROUP_ID — the surrogate primary key, aliased from HEG.ENTITY_GROUP_ID. This is the value typically stored as a foreign key by dependent time entry rule configurations.
• TIME_ENTRY_RULE_GROUP_NAME — the user-facing group name, aliased from HEG.NAME. This is the value displayed in setup forms and referenced in reports.
• OBJECT_VERSION_NUMBER — the optimistic locking / concurrency version number maintained by the EBS Object Version Number (OVN) pattern; it increments on each update to the underlying row.
• CREATED_BY, CREATION_DATE — standard audit columns identifying the user and timestamp of record creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns identifying the user and timestamp of the most recent update.
• LAST_UPDATE_LOGIN — the login identifier associated with the last update, supporting audit traceability.

Together these columns provide identification, display, audit, and concurrency information in a single flat structure.

Common Use Cases and Queries

Typical consumers use the view to populate LOVs, validate references, or resolve identifiers to names in extract queries. A basic retrieval of all rule groups follows:

• SELECT time_entry_rule_group_id, time_entry_rule_group_name FROM apps.hxc_time_entry_rule_groups_v ORDER BY time_entry_rule_group_name;

For incremental integration, the audit columns support change detection:

• SELECT time_entry_rule_group_id, time_entry_rule_group_name, last_update_date FROM apps.hxc_time_entry_rule_groups_v WHERE last_update_date >= :p_since_date;

For reference validation, the group ID can be joined to dependent rule definition tables to confirm that a configured rule points to a valid group. Because the view filters on entity_type = ‘TIME_ENTRY_RULES’, callers need not repeat this predicate and cannot accidentally retrieve unrelated entity groups. In practice, the view is best treated as the canonical read interface for Time Entry Rule Group metadata, while DML remains the responsibility of the base table and its supported APIs.