Search Results hxc_app_comp_notif_usages




Overview
Explore in AI Chat

Overview

The HXC_APP_COMP_NOTIF_USAGES table is a reference and configuration object within the Oracle E-Business Suite Time and Labor Engine (product code HXC). It records the usage relationships between approval components and application component notifications, defining which notification definitions are consumed or enabled for a given approval component. In release 12.1.1 and 12.2.2 the table resides in the HXC schema and is classified as VALID. Its documented physical schema (ETRM 12.2.2) contains five columns, with a single foreign key relationship to HXC_APPROVAL_COMPS.

From a Data Vault modeling perspective, the object is heuristically classified as standalone based on its mined foreign-key structure. This classification is a modeling suggestion rather than a physical constraint: the table functions less as an independent hub and more as an association linking approval components to notification definitions, which aligns it conceptually with a link structure or an attribute-bearing satellite. Its narrow column set and enablement flag suggest it acts primarily as a configuration intersection rather than a transactional fact.

Key Information Stored

The documented schema exposes five columns, of which the following carry the principal business meaning:

  • APPROVAL_COMP_ID — The identifier of the approval component. This column is a documented foreign key to HXC_APPROVAL_COMPS, anchoring each row to a specific approval component definition.
  • APPROVAL_COMP_OVN — The object version number for the approval component, used by the Oracle Applications framework for optimistic locking and concurrency control on the parent approval component record.
  • COMP_NOTIFICATION_ID — The identifier of the application component notification associated with the usage relationship. This is a business-key candidate identifying which notification definition is being referenced.
  • COMP_NOTIFICATION_OVN — The object version number for the notification component, providing the same optimistic-locking semantics at the notification end of the relationship.
  • ENABLED_FLAG — A status indicator that governs whether the notification usage pairing is active. Values are typically 'Y' and 'N', and only enabled rows participate in runtime notification dispatch logic.

The metadata does not document a distinct single surrogate primary key column beyond the identifier pair; the combination of APPROVAL_COMP_ID and COMP_NOTIFICATION_ID effectively serves as the composite business key that determines uniqueness of a usage pairing.

Common Use Cases and Queries

This table is consulted during Time and Labor approval processing when the engine must determine which notification definitions are enabled for a given approval component. Typical scenarios include auditing notification configuration before or after an upgrade, troubleshooting missing or suppressed notifications, and building configuration reports for functional administrators.

A representative query joins the usage rows back to the parent approval component:

  • SELECT u.approval_comp_id, u.comp_notification_id, u.enabled_flag FROM hxc.hxc_app_comp_notif_usages u WHERE u.enabled_flag = 'Y';
  • SELECT a.*, u.comp_notification_id FROM hxc.hxc_approval_comps a JOIN hxc.hxc_app_comp_notif_usages u ON u.approval_comp_id = a.approval_comp_id WHERE u.enabled_flag = 'Y';

Reporting use cases include producing a matrix of approval components versus enabled notifications, verifying that no orphaned usage rows exist after configuration changes, and extracting configuration data for migration between environments. Because the object is low-volume reference data, queries are inexpensive and suitable for both online diagnostics and scheduled audit reports.

Related Objects

The following objects are the most significant dependencies and join partners:

  • HXC_APPROVAL_COMPS — The parent table referenced by the APPROVAL_COMP_ID foreign key; supplies approval component definitions against which usage rows are anchored.
  • HXC_TIME_ATTRIBUTE_* family tables — Often queried alongside usage configuration when diagnosing Time and Labor rule and notification behavior.
  • HXC_APPLICATION_COMPONENTS — Provides the broader application component context referenced by notification identifiers in the Time and Labor Engine.
  • Time and Labor notification and approval concurrent programs — Consume the enabled usage pairings at runtime to determine dispatch behavior.
  • Oracle Applications object version number framework (OVN) — Governs the APPROVAL_COMP_OVN and COMP_NOTIFICATION_OVN columns during DML.

Because the Data Vault classification is standalone, no other mined foreign keys extend from this table beyond the approval component reference, keeping its dependency surface narrow and predictable.