Results for “retrieval_rule_comp_id”

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

Overview

The HXC.HXC_RETRIEVAL_RULE_COMPS table stores Retrieval Rule Components within the Oracle E-Business Suite Time and Labor Engine (HXC) module. It defines the individual building blocks that make up a Retrieval Rule, associating each rule with a specific Time Recipient. Retrieval Rules govern how time and labor data is gathered, filtered, and directed toward recipients during timecard processing, and the component rows are the granular configuration records that link a parent rule to the recipient that should receive or process the retrieved data. The table is classified as VALID in the HXC schema and is available in both 12.1.1 and 12.2.2 releases, with the 12.2.2 documented physical schema exposing 11 columns.

From a Data Vault modeling perspective, the metadata's heuristic classification of this object is link. This is a suggestion rather than a prescribed design: the table primarily resolves a relationship between two business entities — a Retrieval Rule (RETRIEVAL_RULE_ID) and a Time Recipient (TIME_RECIPIENT_ID) — with descriptive attributes carried alongside. Analysts building a Data Vault layer should consider treating it as a link table between the rule and recipient hubs, with the status and Who-columns modeled as satellite attributes.

Key Information Stored

The table's surrogate primary key is RETRIEVAL_RULE_COMP_ID, enforced by the HXC_RETRIEVAL_RULE_COMPS_PK constraint. Notably, the documented unique index is composite, spanning RETRIEVAL_RULE_COMP_ID and ZD_EDITION_NAME. The ZD_EDITION_NAME column is part of the 12.2.2 editioning model and reflects the edition in which the row is valid, so the true business-key candidate combines the surrogate identifier with the edition name rather than the surrogate alone.

• RETRIEVAL_RULE_ID — foreign key to HXC_RETRIEVAL_RULES; identifies the parent rule to which this component belongs.
• TIME_RECIPIENT_ID — foreign key to HXC_TIME_RECIPIENTS; identifies the recipient associated with the component.
• STATUS — the lifecycle or activation state of the component record.
• OBJECT_VERSION_NUMBER — optimistic locking version used by the application to detect concurrent updates.
• CREATED_BY, CREATION_DATE — standard WHO audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording the last modifying user, timestamp, and login.
• ZD_EDITION_NAME — edition identifier for the 12.2.2 editioning model, also part of the unique index.

Common Use Cases and Queries

Typical usage centers on retrieving the components configured for a given rule, or the rules associated with a given recipient. A consultant troubleshooting time retrieval behavior would join this table to its parent rule and recipient to inspect configuration.

To list active components for a rule:

SELECT rc.retrieval_rule_comp_id,
       rc.retrieval_rule_id,
       rc.time_recipient_id,
       rc.status
FROM   hxc.hxc_retrieval_rule_comps rc
WHERE  rc.retrieval_rule_id = :rule_id;

A common reporting pattern resolves each component to its rule and recipient descriptions:

SELECT r.retrieval_rule_id,
       tr.time_recipient_id
FROM   hxc.hxc_retrieval_rule_comps rc,
       hxc.hxc_retrieval_rules   r,
       hxc.hxc_time_recipients    tr
WHERE  rc.retrieval_rule_id = r.retrieval_rule_id
AND    rc.time_recipient_id = tr.time_recipient_id;

Because RETRIEVAL_RULE_COMP_ID is the surrogate key, lookups by that value return a single component row (subject to edition). Data extraction routines frequently key on LAST_UPDATE_DATE for incremental loads.

Related Objects

• HXC.HXC_RETRIEVAL_RULES — parent rule table; join on RETRIEVAL_RULE_COMPS.RETRIEVAL_RULE_ID = HXC_RETRIEVAL_RULES.RETRIEVAL_RULE_ID.
• HXC.HXC_TIME_RECIPIENTS — recipient definition table; join on RETRIEVAL_RULE_COMPS.TIME_RECIPIENT_ID = HXC_TIME_RECIPIENTS.TIME_RECIPIENT_ID.
• HXC_RETRIEVAL_RULE_COMPS_PK — the primary key constraint and its backing unique index on RETRIEVAL_RULE_COMP_ID and ZD_EDITION_NAME.

In practice, the Time and Labor Engine APIs that manipulate retrieval rules read and write these component rows as part of rule definition maintenance. Any custom extraction, conversion, or reporting layer that models retrieval configuration should treat HXC_RETRIEVAL_RULE_COMPS as the junction between rules and recipients.