Search Results ff_description

Overview

APPS.HXC_TIME_ENTRY_RULES_V is a reporting and integration view in the Oracle E-Business Suite Time and Labor (OTL / HXC) module. It presents configuration data describing time entry rules, their approval usage classification, and the formula logic attached to each rule. The view denormalizes the underlying HXC_TIME_ENTRY_RULES table by joining lookup translations, mapping definitions, and formula definitions into a single flat structure, avoiding the need for consumers to perform those joins independently. Because it carries no business logic beyond decoding, it is safe to use in custom reports, extracts, BI Publisher data sets, and inbound or outbound integration queries where rule metadata must be presented in a human-readable form.

Underlying Base Objects

The view is defined over three principal sources with outer joins, plus one scalar subquery:

• HXC_TIME_ENTRY_RULES (accessed as a synonym) — the driving table; every row in the view corresponds to one rule definition record.
• FF_FORMULAS_F (synonym) — outer-joined on FORMULA_ID and constrained by START_DATE falling between the formula's EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, so the effective version of the formula is returned.
• HXC_MAPPINGS (synonym) — outer-joined on MAPPING_ID to supply the mapping name.
• HXC_LOOKUPS (view) — used in a scalar subquery against LOOKUP_TYPE = 'HXC_APPROVAL_RULE_USAGE' to translate the stored RULE_USAGE code into a meaning.
• FND_GLOBAL (package) — documented as a referenced object, supporting the standard multi-org / session context used throughout HXC views.

All joins to FF_FORMULAS_F and HXC_MAPPINGS are outer joins, so a rule remains visible even when no formula or mapping is associated.

Key Columns

• TIME_ENTRY_RULE_ID / NAME / DESCRIPTION — primary identifier and descriptive attributes of the rule.
• RULE_USAGE / RULE_USAGE_NAME — the raw lookup code and its decoded meaning drawn from HXC_APPROVAL_RULE_USAGE; this is the column of interest for approval-rule usage analysis.
• MAPPING_ID / MAPPING_NAME — the mapping referenced by the rule and its name.
• FORMULA_ID / FORMULA_NAME / FF_DESCRIPTION — the effective formula attached to the rule and its description.
• BUSINESS_GROUP_ID / LEGISLATION_CODE — organizational and legislative scoping of the rule.
• START_DATE / END_DATE — the validity window of the rule.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the descriptive flexfield columns propagated from the base table.

Common Use Cases and Queries

The view is typically queried to list which rules exist per usage, to audit formula assignments, or to reconcile mappings against rules. The following examples reflect the documented structure.

• List rules by approval usage:

  SELECT rule_usage_name, name, start_date, end_date
  FROM   apps.hxc_time_entry_rules_v
  WHERE  rule_usage = 'APPROVAL'
  ORDER  BY name;

• Identify rules with no formula attached (outer-join evidence):

  SELECT name, mapping_name
  FROM   apps.hxc_time_entry_rules_v
  WHERE  formula_id IS NULL;

• Extract usage distribution for a business group:

  SELECT rule_usage_name, COUNT(*)
  FROM   apps.hxc_time_entry_rules_v
  WHERE  business_group_id = :p_bg
  GROUP  BY rule_usage_name;

Because RULE_USAGE_NAME is derived from HXC_APPROVAL_RULE_USAGE, a query on that column will return NULL for any code not present in the lookup, which is a useful integrity check.