Results for “application_update_process”

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

Overview

HXC_TIME_RECIPIENTS is a core configuration table within the Oracle Time and Labor Engine (HXC) product family. It stores the definition of time recipients — the entities, applications, or functional targets that participate in time-related retrieval, approval, and validation processing flows. In Oracle EBS 12.1.1 and 12.2.2, this table acts as a central registry that ties together approval components, retrieval rules, retrieval processes, and period summarization logic. Each row represents a distinct recipient configuration, identified by a surrogate primary key and qualified by an application context and, in the 12.2.2 schema, an edition name.

The table resides in the HXC schema and is owned by the Time and Labor Engine module. With 17 documented columns and a single-column surrogate key, the table functions as a lookup and configuration hub. From a Data Vault modeling perspective, the metadata's heuristic classification is hub-leaning: the table is best modeled as a hub keyed on TIME_RECIPIENT_ID, since multiple dependent tables reference it through foreign keys and it carries relatively stable descriptive attributes.

Key Information Stored

The primary key is defined by HXC_TIME_RECIPIENTS_PK, built on TIME_RECIPIENT_ID and, in the 12.2.2 physical schema, ZD_EDITION_NAME. TIME_RECIPIENT_ID is the surrogate identifier; ZD_EDITION_NAME supports Oracle's edition-based redefinition (EBR) strategy for online patching. The documented business-facing identifier is NAME, which carries the user-recognizable recipient name.

The most significant attributes include:

• TIME_RECIPIENT_ID — surrogate primary key and the join column referenced by all dependent tables.
• NAME — human-readable recipient name.
• APPLICATION_ID — identifies the owning application context.
• APPL_DYNAMIC_TEMPLATE_PROCESS — process hook for dynamic template handling.
• APPLICATION_RETRIEVAL_FUNCTION — the function invoked for retrieval operations.
• APPLICATION_UPDATE_PROCESS — the process invoked when recipient data is updated.
• APPL_VALIDATION_PROCESS — the validation routine applied to recipient data.
• APPLICATION_PERIOD_FUNCTION — the function governing period-level processing.
• EXTENSION_FUNCTION1 and EXTENSION_FUNCTION2 — extension points for application-specific logic.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ZD_EDITION_NAME — EBR edition discriminator (12.2.2).

Only TIME_RECIPIENT_ID combined with ZD_EDITION_NAME is documented as a unique index candidate; NAME is not declared unique in the metadata, so it should be treated as a descriptive label rather than a guaranteed business key.

Common Use Cases and Queries

Developers and functional analysts query HXC_TIME_RECIPIENTS to enumerate configured time recipients, trace which application function/process hooks are wired to each recipient, and validate approval and retrieval configurations. A typical lookup joins the table to dependent components:

• Listing all recipients with their owning application: SELECT TIME_RECIPIENT_ID, NAME, APPLICATION_ID FROM HXC.HXC_TIME_RECIPIENTS ORDER BY NAME;
• Finding approval components and their recipients: SELECT r.NAME, a.TIME_RECIPIENT_ID FROM HXC.HXC_TIME_RECIPIENTS r JOIN HXC.HXC_APPROVAL_COMPS a ON a.TIME_RECIPIENT_ID = r.TIME_RECIPIENT_ID;
• Auditing retrieval rule components tied to each recipient: join HXC_RETRIEVAL_RULE_COMPS on TIME_RECIPIENT_ID.
• Period summarization reporting: join HXC_APP_PERIOD_SUMMARY and HXC_APP_PERIOD_SUMMARY_AR on TIME_RECIPIENT_ID.

Because the table is configuration-oriented and low-volume, queries are typically used for diagnostics, setup verification, and impact analysis before changing a recipient definition. Filtering by APPLICATION_ID is useful when isolating recipients for a specific module.

Related Objects

HXC_TIME_RECIPIENTS is referenced by numerous dependent tables through the TIME_RECIPIENT_ID foreign key. The most significant documented relationships are:

• HXC_APPROVAL_COMPS — approval components associated with each recipient.
• HXC_APPROVAL_PERIOD_COMPS — period-level approval components.
• HXC_DATA_APP_RULE_USAGES — data application rule usage records.
• HXC_RETRIEVAL_PROCESSES — retrieval process definitions tied to recipients.
• HXC_RETRIEVAL_RULE_COMPS — retrieval rule components.
• HXC_APP_PERIOD_SUMMARY and HXC_APP_PERIOD_SUMMARY_AR — period summary tables (including the archive variant) referencing recipients.

These relationships confirm the table's role as a hub: configuration flows for approval, retrieval, and summarization all resolve back to a single recipient definition, making HXC_TIME_RECIPIENTS the anchor for cross-component Time and Labor reporting and diagnostics.