Results for “hxt_batch_sum_amounts_v”

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

Overview

The HXT_BATCH_SUM_AMOUNTS_V view is a reporting and integration object in the Oracle E-Business Suite Time and Labor module (HXT). It presents summarized, batch-level earnings data that has been calculated and cost-allocated for individual assignments. The view joins timecard, element type, cost allocation, and location information into a single denormalized result set, which makes it suitable for downstream reporting, payroll feeds, and custom integrations that require earnings amounts grouped by batch, assignment, and element.

The view is owned by the APPS schema and is marked VALID. Its defining characteristic is that it exposes hours, amount, rate, and full cost allocation segment detail together with the earnings reason, which is a value drawn from the ELE_ENTRY_REASON lookup. This reason column is the field most users search for when attempting to identify why a particular batch or earnings line carries a specific classification.

Underlying Base Objects

The documented base objects referenced by the view include:

• HXT_TIMECARDS_F (synonym) — provides the BATCH_ID that groups earnings records.
• HXT_DET_HOURS_WORKED_F (synonym) — the primary detail source for hours worked, amounts, rates, and the foreign keys to reason, rate code, cost center, and location.
• PER_ASSIGNMENTS_F (view) — supplies ASSIGNMENT_NUMBER for the working assignment.
• PAY_ELEMENT_TYPES_F (synonym) and PAY_ELEMENT_TYPES_F_TL — provide the element type definition and translated element name.
• HR_LOOKUPS (view) — filtered to LOOKUP_TYPE = 'ELE_ENTRY_REASON' to resolve the numeric reason code into a readable MEANING.
• PAY_COST_ALLOCATION_KEYFLEX (synonym) — supplies the concatenated and individual cost allocation segments.
• FND_FLEX_VALUES (synonym) — resolves the rate code flex value.
• HR_LOCATIONS_ALL_TL (synonym) and HR_LOCATIONS_NO_JOIN (view) — provide location code with language-based translation.

Supporting packages such as HR_API, HR_GENERAL, and HR_SECURITY are referenced in the metadata, typically invoked through the base objects rather than directly in the view text.

Key Columns

• BATCH_ID — the Time and Labor batch the summarized amounts belong to.
• ASSIGNMENT_ID / ASSIGNMENT_NUMBER — identifies the assignment for which hours and amounts were calculated.
• ELEMENT_NAME / ELEMENT_TYPE_ID — the payroll element and its identifier.
• REASON — the decoded ELE_ENTRY_REASON lookup meaning, sourced from HR_LOOKUPS against FCL_EARN_REASON_CODE.
• HOURS, AMOUNT, HOURLY_RATE, RATE_MULTIPLE — the calculated earnings quantities and rates.
• CONCATENATED_SEGMENTS and SEGMENT1–SEGMENT30 — the full cost allocation key flexfield breakdown.
• RATE_CODE — the flex value representing the rate code.
• LOCATION_CODE, CITY_NAME, COUNTY_NAME, STATE_NAME, ZIP_CODE — location and jurisdiction attributes.
• FCL_TAX_RULE_CODE, SEPARATE_CHECK_FLAG — payroll tax and check handling attributes.
• DATE_WORKED — the work date used for date-effective joins.

Common Use Cases and Queries

The view supports reconciliation of batch earnings, cost allocation validation, and lookup of the earnings reason behind a given batch line. A typical query filtering by reason:

• SELECT batch_id, assignment_number, element_name, reason, hours, amount FROM hxt_batch_sum_amounts_v WHERE reason = 'OVERTIME';
• SELECT batch_id, SUM(amount) FROM hxt_batch_sum_amounts_v GROUP BY batch_id;
• SELECT assignment_number, concatenated_segments, amount FROM hxt_batch_sum_amounts_v WHERE batch_id = :batch_id;

Because the definition restricts rows to the current effective date range and to records where AMOUNT is not null, results always reflect active, costed earnings suitable for financial and integration consumption.