Results for “hxc_data_app_rule_usages”

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

Overview

HXC_DATA_APP_RULE_USAGES is a Time and Labor Engine (HXC) table that stores Data Approval Rule Usages. In Oracle EBS 12.1.1 and 12.2.2, it acts as the association table that binds a time entry rule to an approval style and, optionally, to a time recipient. It effectively defines which approval rule is applied, under what approval style, and directed to which recipient within the Time and Labor approval framework.

Given its three foreign key columns and no descriptive attributes of its own, the ETRM metadata classifies this object heuristically as a link table in a Data Vault modeling sense. It resolves many-to-many associations between HXC_TIME_ENTRY_RULES, HXC_APPROVAL_STYLES, and HXC_TIME_RECIPIENTS. The link classification is a modeling suggestion rather than a physical designation.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• DATA_APP_RULE_USAGE_ID — the surrogate primary key, generated by HXC_DATA_APP_RULE_USAGES_PK.
• TIME_ENTRY_RULE_ID — foreign key to HXC_TIME_ENTRY_RULES; identifies the time entry rule being applied.
• APPROVAL_STYLE_ID — foreign key to HXC_APPROVAL_STYLES; identifies the approval style governing the rule.
• TIME_RECIPIENT_ID — foreign key to HXC_TIME_RECIPIENTS; identifies the recipient of the rule's outcome.
• OBJECT_VERSION_NUMBER — optimistic locking column used for concurrent update control.
• CREATED_BY, CREATION_DATE — standard audit columns capturing creation user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the last modification details.
• ZD_EDITION_NAME — editioning column supporting Online Patching in EBS 12.2.2.

Business-key candidates are identified by the unique index HXC_DATA_APP_RULE_USAGES_PK, which in the documented 12.2.2 schema comprises DATA_APP_RULE_USAGE_ID and ZD_EDITION_NAME. The surrogate key remains the primary identifier, while the unique index enforces edition-aware uniqueness.

Common Use Cases and Queries

Typical usage involves determining the approval rule configuration for a given time entry rule, or reconstructing the recipient routing for approval styles. Sample query patterns include:

• Listing all recipients tied to a specific time entry rule: SELECT TIME_RECIPIENT_ID FROM HXC_DATA_APP_RULE_USAGES WHERE TIME_ENTRY_RULE_ID = :rule_id.
• Joining to HXC_APPROVAL_STYLES to resolve approval definitions: ... JOIN HXC_APPROVAL_STYLES s ON s.APPROVAL_STYLE_ID = u.APPROVAL_STYLE_ID.
• Reporting on approval rule coverage by joining to HXC_TIME_ENTRY_RULES and HXC_TIME_RECIPIENTS.
• Auditing configuration changes via CREATED_BY, LAST_UPDATED_BY, and their timestamps.

Related Objects

The following objects are directly related through documented foreign keys and the primary key:

• HXC_TIME_ENTRY_RULES — referenced via TIME_ENTRY_RULE_ID; supplies the rule definition.
• HXC_APPROVAL_STYLES — referenced via APPROVAL_STYLE_ID; supplies approval style configuration.
• HXC_TIME_RECIPIENTS — referenced via TIME_RECIPIENT_ID; supplies recipient routing.
• HXC_DATA_APP_RULE_USAGES_PK — the unique index backing the primary key.

These relationships make HXC_DATA_APP_RULE_USAGES a central junction for approval rule resolution in the Time and Labor approval engine.