Results for “retrieval_process_id”

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

Overview

HXC_RETRIEVAL_RULES is a table in the HXC schema (Time and Labor Engine) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of retrieval rules, which govern how time-related data is retrieved, filtered, and assembled for processing by the Time and Labor Engine. Retrieval rules sit beneath retrieval processes as configurable components, forming the logic that determines which time data is pulled into a given process.

Based on the foreign key topology provided in the ETRM metadata, this table is classified as satellite-leaning in a Data Vault modeling sense. It should be treated as a satellite that carries descriptive attributes and depends on a parent business entity (HXC_RETRIEVAL_PROCESSES). Its descriptive columns and its downstream dependency from HXC_RETRIEVAL_RULE_COMPS support this classification as a modeling suggestion.

Key Information Stored

HXC_RETRIEVAL_RULES contains 10 documented columns. The most important include:

• RETRIEVAL_RULE_ID – The surrogate primary key, defined by the HXC_RETRIEVAL_RULES_PK constraint. It uniquely identifies each retrieval rule.
• RETRIEVAL_PROCESS_ID – A foreign key to HXC_RETRIEVAL_PROCESSES, establishing the parent retrieval process to which the rule belongs.
• NAME – The descriptive name of the retrieval rule. Along with ZD_EDITION_NAME it forms the unique business key candidate HXC_RETRIEVAL_RULES_UK1.
• ZD_EDITION_NAME – The edition name supporting the edition-based redefinition (EBR) model used in EBS 12.2. It participates in both the primary key (HXC_RETRIEVAL_RULES_PK) and the business key (HXC_RETRIEVAL_RULES_UK1).
• OBJECT_VERSION_NUMBER – The optimistic locking column used to manage concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – The standard Oracle EBS audit columns tracking who created and last modified each row.

The surrogate primary key (RETRIEVAL_RULE_ID) should be distinguished from the business-key candidate (NAME, ZD_EDITION_NAME), which represents the logical, user-facing identifier of the rule.

Common Use Cases and Queries

Typical usage centers on interrogating and reporting on retrieval rule configuration. A common query joins rules to their parent process to list all rules by process name:

• Joining HXC_RETRIEVAL_RULES to HXC_RETRIEVAL_PROCESSES on RETRIEVAL_PROCESS_ID to report rule-to-process mappings.
• Looking up a rule by its business key (NAME and ZD_EDITION_NAME) for configuration review.
• Enumerating the components of a rule by joining to HXC_RETRIEVAL_RULE_COMPS on RETRIEVAL_RULE_ID.
• Auditing rule changes using LAST_UPDATED_BY and LAST_UPDATE_DATE.
• Edition-aware queries filtering on ZD_EDITION_NAME to isolate rules for a specific edition in a 12.2 environment.

Related Objects

• HXC_RETRIEVAL_PROCESSES – Parent table referenced via HXC_RETRIEVAL_RULES.RETRIEVAL_PROCESS_ID.
• HXC_RETRIEVAL_RULE_COMPS – Child table referencing HXC_RETRIEVAL_RULES.RETRIEVAL_RULE_ID, holding the individual rule components.
• HXC_RETRIEVAL_RULES_PK – Primary key constraint on RETRIEVAL_RULE_ID and ZD_EDITION_NAME.
• HXC_RETRIEVAL_RULES_UK1 – Unique business-key index on NAME and ZD_EDITION_NAME.