Results for “hxt_batch_reference_v”

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

Overview

The HXT_BATCH_REFERENCE_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Time and Labor module (HXT). It presents a filtered, de-duplicated list of batch references that qualify as retroactive time batches pending or undergoing validation in the Time and Labor batch process. The view exists to expose a clean, abstracted set of batch identifiers and the business group context to which each belongs, without requiring downstream consumers to navigate the internal batch state machine or the detailed hours-worked structures directly.

Its role is primarily diagnostic and reconciliation-oriented. Administrators, support analysts, and custom concurrent programs use it to identify batches that carry a valid, non-null batch reference and that are in a validation state and that contain retroactive detail rows. Because the view distills these conditions into a two-column projection, it serves as a convenient driver for reports, data fixes, and integration points that must reconcile batch references against downstream processing.

Underlying Base Objects

The view is defined over three documented base objects, joined in a single SELECT with a DISTINCT clause:

• HXT_BATCH_STATES (SYNONYM) — the Time and Labor batch state table, providing the current status of each batch. The view filters to statuses VV and VW, representing the relevant validation states in the batch lifecycle.
• HXT_DET_HOURS_WORKED (VIEW) — the detailed hours-worked view, used here only through an EXISTS predicate. The correlation requires that at least one detail row references the batch as its RETRO_BATCH_ID, ensuring the batch is genuinely tied to retroactive time entries.
• PAY_BATCH_HEADERS (SYNONYM) — the Payroll batch header table, supplying the human-readable BATCH_REFERENCE and the BUSINESS_GROUP_ID. The join condition is BATCH_REFERENCE IS NOT NULL, which excludes unnamed batches from the result set.

Because HXT_BATCH_STATES is a synonym that commonly resolves to a synonym chain in the APPS schema, and PAY_BATCH_HEADERS is likewise exposed as a synonym, the view remains a stable public interface even if underlying physical objects are reorganized by patching.

Key Columns

• BATCH_REFERENCE — the descriptive identifier assigned to a payroll batch header. This is the value users typically search for and cite in support tickets or reconciliation spreadsheets. Only non-null references are returned.
• BUSINESS_GROUP_ID — the identifier of the business group (HR security group) that owns the batch. It scopes results to a legal-employer or operating-unit context and is essential for multi-organization filtering in HRMS-secured environments.

The two-column shape is deliberate: the view does not expose batch IDs, states, or detail quantities, so consumers must join back to the base objects if they require deeper attributes. This keeps the projection efficient and the DISTINCT cheap to compute.

Common Use Cases and Queries

Typical scenarios include reconciling retroactive batches prior to payroll transfer, auditing why a batch reference is missing from a report, and populating a parameter list for a custom validation program. The following queries illustrate routine access patterns.

• List all qualifying batch references for a business group:

  SELECT BATCH_REFERENCE FROM APPS.HXT_BATCH_REFERENCE_V WHERE BUSINESS_GROUP_ID = :p_bg_id ORDER BY BATCH_REFERENCE;

• Confirm whether a specific user-supplied reference exists and is retroactive:

  SELECT COUNT(*) FROM APPS.HXT_BATCH_REFERENCE_V WHERE BATCH_REFERENCE = :p_ref;

• Drive a custom concurrent program or LOV by selecting both columns:

  SELECT BATCH_REFERENCE, BUSINESS_GROUP_ID FROM APPS.HXT_BATCH_REFERENCE_V;

Because the view is a read-only, DISTINCT projection, it is safe for ad-hoc querying but should not be treated as an update target. Its correctness depends entirely on the ETRM batch state and retro detail data being current, so results should be interpreted after batch validation cycles complete.