Search Results rule_usage_name




Overview
Explore in AI Chat

Overview

HXC_TIME_ENTRY_RULES_V is a seed data view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the definition of time entry rules maintained by the Time and Labor Engine (HXC) product, denormalizing each rule row with the descriptive meaning of its usage code, the name of its associated mapping, and the name and description of its associated Oracle Fast Formula. The view serves as the primary read-only access point for time entry rule configuration and is used both by application forms and by reporting and integration queries that need rule definitions in a human-readable form.

The view exposes the full set of DFF attribute columns (ATTRIBUTE1 through ATTRIBUTE30 plus ATTRIBUTE_CATEGORY), the standard WHO audit columns, and OBJECT_VERSION_NUMBER, which supports optimistic locking in the underlying table. Because displayed values such as RULE_USAGE_NAME and MAPPING_NAME are resolved within the view, consumers avoid joins to lookup and mapping tables.

The column MAPPING_NAME is particularly significant: it is the denormalized display name of the mapping referenced by the rule's MAPPING_ID. Users searching on this term are typically locating the mapping assigned to a given time entry rule.

Underlying Base Objects

The view is defined over the following documented base objects:

All base object joins to the mapping and formula tables are outer joins, so rules without a mapping or formula definition are still returned.

Key Columns

  • ROW_ID — ROWID of the underlying HXC_TIME_ENTRY_RULES row, used as a unique identifier.
  • TIME_ENTRY_RULE_ID — primary key of the rule.
  • NAME — user-defined name of the time entry rule.
  • RULE_USAGE — lookup code describing how the rule is applied.
  • RULE_USAGE_NAME — decoded meaning of RULE_USAGE from HXC_LOOKUPS.
  • BUSINESS_GROUP_ID — operating unit or business group context of the rule.
  • LEGISLATION_CODE — legislative context.
  • MAPPING_ID — foreign key to the mapping assigned to the rule.
  • MAPPING_NAME — name of the referenced mapping, joined from HXC_MAPPINGS; returned as NULL when no mapping is assigned.
  • FORMULA_ID, FORMULA_NAME, FF_DESCRIPTION — the attached Fast Formula and its descriptive text.
  • DESCRIPTION — free-text description of the rule.
  • START_DATE / END_DATE — effective date range of the rule.
  • OBJECT_VERSION_NUMBER — version counter for concurrent update control.
  • ATTRIBUTE_CATEGORY / ATTRIBUTE1–30 — descriptive flexfield context and segment values.
  • CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — WHO audit columns.

Common Use Cases and Queries

Typical scenarios include listing rules for a business group, identifying which rules reference a specific mapping, and auditing appended descriptive flexfield values.

SELECT time_entry_rule_id,
       name,
       rule_usage_name,
       mapping_id,
       mapping_name,
       formula_name,
       start_date,
       end_date
FROM   apps.hxc_time_entry_rules_v
WHERE  business_group_id = :p_business_group_id
AND    SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);

To search on the mapping dimension — the term most often associated with this view:

SELECT time_entry_rule_id,
       name,
       rule_usage_name,
       mapping_name
FROM   apps.hxc_time_entry_rules_v
WHERE  UPPER(mapping_name) LIKE UPPER('%' || :p_mapping_name || '%');

Because MAPPING_ID and MAPPING_NAME are outer-joined, rules without an assigned mapping are still returned with a NULL MAPPING_NAME, which is useful when reconciling incomplete rule configuration.