Search Results hxc_retrieval_range_resources




Overview
Explore in AI Chat

Overview

HXC_RETRIEVAL_RANGE_RESOURCES is a table owned by the HXC schema, the database component of the Oracle Time and Labor Engine (HXC) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold the resources associated with each retrieval range defined in the Time and Labor architecture. In practical terms, it acts as an intersection or assignment table that binds a configured retrieval range to one or more resource identifiers, allowing the retrieval engine to determine which resources are visible or processed when the range criteria are evaluated.

The table is minimal by design, consisting of only two documented columns and a composite primary key. It has no independent identity of its own outside the RETRIEVAL_RANGE_ID association, which places it firmly in a dependent or child role relative to HXC_RETRIEVAL_RANGES. Under the heuristic Data Vault classification mined from its foreign key structure, the object is described as satellite-leaning: it carries descriptive associations attached to a parent range rather than acting as a hub (no single natural business key of its own) or a true link between multiple independent hubs. This classification should be treated as a modeling suggestion rather than a normative Oracle statement, since Oracle's own documentation presents the object simply as a table, not as a Data Vault artifact.

Key Information Stored

The documented column set is deliberately narrow, containing just two columns, both of which participate in the primary key:

  • RETRIEVAL_RANGE_ID — Identifies the parent retrieval range. This is also the table's foreign key column, referencing HXC_RETRIEVAL_RANGES.RETRIEVAL_RANGE_ID. It is the primary business-key candidate on the range side of the relationship.
  • RESOURCE_ID — Identifies the individual resource assigned to that retrieval range. Together with RETRIEVAL_RANGE_ID it forms the composite business key of the record.

The composite primary key is defined as HXC_RETRIEVAL_RANGE_RESOURCE_P over (RETRIEVAL_RANGE_ID, RESOURCE_ID). Because the table has no additional documented columns, there is no separate surrogate single-column primary key distinct from these two identifiers; the surrogate is effectively the combination of the two business keys. This means each (range, resource) pairing can exist only once, which enforces the integrity of the assignment set. No additional unique indexes, descriptive attributes, or audit columns are documented for this object, so consumers should treat the pair itself as the authoritative identifier.

Common Use Cases and Queries

The principal use case is determining which resources belong to a given retrieval range, and conversely which retrieval ranges reference a particular resource. This supports time-entry retrieval scoping, reporting on retrieval configuration, and validation of the assignment mapping when ranges are copied, modified, or migrated between environments.

A representative join retrieves the resource set for a specific range:

  • SELECT rr.resource_id FROM hxc_retrieval_range_resources rr WHERE rr.retrieval_range_id = :range_id;
  • SELECT r.retrieval_range_id, r.resource_id FROM hxc_retrieval_ranges r, hxc_retrieval_range_resources rr WHERE r.retrieval_range_id = rr.retrieval_range_id;
  • SELECT rr.resource_id, COUNT(*) FROM hxc_retrieval_range_resources rr GROUP BY rr.resource_id HAVING COUNT(*) > 1; to identify resources reused across multiple ranges.

Typical reporting scenarios include auditing retrieval-range coverage, reconciling resource assignments after a patch or upgrade, and troubleshooting cases where a resource does not appear in time-retrieval results because its range association is missing. Because the table is small, queries against it are inexpensive and are usually combined with the parent range table for descriptive context.

Related Objects

The dominant relationship is with the parent range table, and any reconciliation or reporting query should join on that column:

  • HXC_RETRIEVAL_RANGES — the parent object. Join HXC_RETRIEVAL_RANGE_RESOURCES.RETRIEVAL_RANGE_ID = HXC_RETRIEVAL_RANGES.RETRIEVAL_RANGE_ID. This is the only documented foreign key relationship for the table.
  • HXC_RETRIEVAL_RANGE_RESOURCE_P — the composite primary key constraint, used by the optimizer for uniqueness enforcement and index access.
  • RESOURCE_ID resolution — the RESOURCE_ID values logically resolve to resource definitions maintained elsewhere in the Time and Labor and HRMS schemas (for example the HXC resource entities and PER_ALL_PEOPLE_F for person-based resources), although this specific linkage is not documented as a formal foreign key on this table.

No additional HXC tables, views, or public APIs are documented in the ETRM metadata as directly referencing HXC_RETRIEVAL_RANGE_RESOURCES beyond the parent range relationship. Integrations should therefore rely on the documented foreign key to HXC_RETRIEVAL_RANGES and treat any resource-side resolution as an application-level association rather than a declared database constraint.