Results for “parent_building_block_ovn”

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

Overview

HXC.HXC_AR_TC_IDS_TEMP is a transient working table within the Oracle E-Business Suite Time and Labor Engine (product code HXC). Per the ETRM metadata, its documented purpose is "For Multi-threaded A&R" — that is, to support concurrent, multi-threaded execution of the Time and Labor Approval and Rules (A&R) processing that evaluates timecard building blocks against approval styles and rule definitions. Because A&R processing can be parallelized across worker threads, this table temporarily stages the identifiers of building blocks being processed simultaneously, preventing contention on the primary transactional timecard tables.

The object is classified as VALID and owned by the HXC schema, with 25 documented columns. Its primary key is HXC_AR_TC_IDS_TEMP_PK, defined over (TIME_BUILDING_BLOCK_ID, OBJECT_VERSION_NUMBER). A foreign key relationship exists to HXC_APPROVAL_STYLES via APPROVAL_STYLE_ID.

From a heuristic Data Vault modeling perspective, the FK structure is classified as standalone. This suggests the table is best modeled as a staging or work table rather than a durable hub, link, or satellite. Its transient nature aligns with that classification: it holds short-lived, thread-scoped identifier sets rather than persistent business entities.

Key Information Stored

The table stores a limited set of columns relevant to parallel A&R processing. The most significant include:

• TIME_BUILDING_BLOCK_ID — the identifier of the time building block being processed; part of the composite primary key.
• OBJECT_VERSION_NUMBER — optimistic locking/versioning column; the second component of the composite primary key.
• TYPE, MEASURE, UNIT_OF_MEASURE — describe the building block's nature and quantified measurement.
• START_TIME, STOP_TIME — the temporal span of the building block being evaluated.
• PARENT_BUILDING_BLOCK_ID, PARENT_BUILDING_BLOCK_OVN — parent linkage and parent version for hierarchical time definitions.
• SCOPE — the processing scope applicable to the row.
• APPROVAL_STATUS, APPROVAL_STYLE_ID — the approval outcome and the referenced approval style (FK to HXC_APPROVAL_STYLES).
• RESOURCE_ID, RESOURCE_TYPE — the resource (person or asset) associated with the block.
• DATE_FROM, DATE_TO — effective dating for the row.
• DATA_SET_ID, APPLICATION_SET_ID — set-based (multi-org / reference data set) partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

The surrogate primary key is HXC_AR_TC_IDS_TEMP_PK; no separate business-key unique index is documented beyond that PK.

Common Use Cases and Queries

Because this is a temporary multi-threading aid, direct querying is uncommon in production reporting. Typical usage includes:

• Diagnosing concurrent A&R failures by inspecting which building blocks were staged for a given run.
• Joining to HXC_APPROVAL_STYLES to verify approval style resolution during a batch cycle.
• Data cleanup / purge scripts that truncate or delete stale rows after a processing run completes.

A representative query:

SELECT t.time_building_block_id, t.approval_status, a.approval_style_name
FROM   hxc.hxc_ar_tc_ids_temp t, hxc.hxc_approval_styles a
WHERE  t.approval_style_id = a.approval_style_id
AND    t.date_from <= SYSDATE;

Reporting use cases are limited; the table is best treated as a diagnostic and housekeeping object rather than a reporting source.

Related Objects

• HXC_APPROVAL_STYLES — referenced via APPROVAL_STYLE_ID (documented FK).
• HXC_TIME_BUILDING_BLOCKS — source of TIME_BUILDING_BLOCK_ID values staged here.
• HXC_TIME_ATTRIBUTE_RANGES and HXC_TIME_BUILDING_BLOCK_USAGES — related to building block definitions used during A&R.
• HXC_AR_TC_IDS (persistent counterpart) — parallels this temp table's processed identifier set.
• HXC_RULES and HXC_APPROVAL_PERIODS — provide the rule and period context for A&R evaluation.
• HXC_TIME_ATTRIBUTES — supplies attribute values considered during approval.

Together these objects form the A&R processing ecosystem in which HXC_AR_TC_IDS_TEMP serves as a transient coordination artifact.