Results for “detail_attribute30”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
HXC_TIMECARD_DETAILS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined under the HXC (Time and Labor Engine) product. It exposes the lowest level of timecard data maintained by the Time and Labor Engine: individual "detail" time building blocks, each representing a discrete time entry such as a punch, an hours line, an overtime segment, or a premium entry recorded against a person. Retail timecard entry, time collection device imports, timekeeper adjustments, and rules processing all resolve to detail-level building blocks, which this view surfaces in a denormalized, join-ready form.
In Oracle EBS 12.1.1 and 12.2.2 the view is provided as a reporting and integration interface. It shields consumers from the complexity of the underlying attribute-usage model, where one time building block can carry many time attributes through a usage table. Developers and analysts use it for BEE/BIP reports, custom OAF pages, interfaces to payroll or project costing, and reconciliation of time entry against payroll results. The view is documented as VALID in the APPS schema under the ETRM metadata for 12.2.2.
Underlying Base Objects
The view is defined over three base objects, plus a package used for a date predicate:
- HXC_TIME_BUILDING_BLOCKS (synonym to the base table, aliased HTB) — the master record of each time building block, supplying identifier, version, time span, resource, scope, measure, unit of measure, parent linkage, and comments.
- HXC_TIME_ATTRIBUTE_USAGES (HTAU) — the intersection that associates a building block (and a specific object version) with the time attributes that apply to it.
- HXC_TIME_ATTRIBUTES (HTA) — the attribute definitions and their flexfield-style ATTRIBUTE1..ATTRIBUTE30 values.
- HR_GENERAL (package) — referenced through HR_GENERAL.END_OF_TIME in the DATE_TO predicate.
Joins are made on TIME_BUILDING_BLOCK_ID and OBJECT_VERSION_NUMBER between the blocks and usages tables, and on TIME_ATTRIBUTE_ID between usages and attributes. Filters restrict rows to RESOURCE_TYPE = 'PERSON', DATE_TO = HR_GENERAL.END_OF_TIME (current, non-dated rows), and SCOPE = 'DETAIL', so the view returns only current detail-level person timecard entries, not summaries or aggregates.
Key Columns
- DETAIL_TIMECARD_ID / DETAIL_OBJECT_VERSION — surrogate identifier and version of the detail building block; the version participates in the join to attribute usages.
- DETAIL_START_TIME / DETAIL_STOP_TIME — the start and stop of the detail time interval.
- DETAIL_RESOURCE_ID — the person (resource) to whom the entry belongs.
- DETAIL_PARENT_TIMECARD_ID / DETAIL_PARENT_OBJECT_VERSION — the parent building block, linking the detail to its enclosing timecard structure.
- DETAIL_SCOPE / DETAIL_MEASURE / DETAIL_UNIT_OF_MEASURE — scope (always DETAIL here), the measured quantity (for example hours or units), and its unit of measure.
- DETAIL_BLD_BLK_INFO_TYPE_ID — the information type of the attribute, indicating the nature of the detail captured.
- DETAIL_COMMENT_TEXT — free-text comments attached to the detail entry.
- DETAIL_ATTRIBUTE_CATEGORY and DETAIL_ATTRIBUTE1..DETAIL_ATTRIBUTE30 — descriptive flexfield segments carrying the extended detail attributes.
Common Use Cases and Queries
Typical scenarios include extracting individual punches or hours lines for a person and date range, joining detail entries to payroll time results, validating timecard imports, and feeding downstream costing or labor distribution processes.
Detail entries for one person within a period:
SELECT detail_timecard_id, detail_start_time, detail_stop_time, detail_measure, detail_unit_of_measure FROM apps.hxc_timecard_details_v WHERE detail_resource_id = :p_person_id AND detail_start_time >= :p_start AND detail_stop_time <= :p_end ORDER BY detail_start_time;
Retrieving the flexfield attributes of a detail entry:
SELECT detail_timecard_id, detail_attribute_category, detail_attribute1, detail_attribute2 FROM apps.hxc_timecard_details_v WHERE detail_timecard_id = :p_id;
Rolling detail hours up to the parent timecard:
SELECT detail_parent_timecard_id, detail_unit_of_measure, SUM(detail_measure) total_measure FROM apps.hxc_timecard_details_v WHERE detail_resource_id = :p_person_id GROUP BY detail_parent_timecard_id, detail_unit_of_measure;
Because the view filters to current person detail rows, it is best suited to operational reporting rather than historical dated queries; historical retrieval requires the underlying dated tables directly.
-
View: HXC_TIMECARD_DETAILS_V 12.1.1
APPS.HXC_TIMECARD_DETAILS_V·↳ HR_GENERAL·↳ HXC_TIME_ATTRIBUTES·↳ HXC_TIME_ATTRIBUTE_USAGES·Explore HXC module →
-
View: HXC_TIMECARD_DETAILS_V 12.2.2
APPS.HXC_TIMECARD_DETAILS_V·↳ HR_GENERAL·↳ HXC_TIME_ATTRIBUTES·↳ HXC_TIME_ATTRIBUTE_USAGES·Explore HXC module →
-
eTRM - HXC Tables and Views 12.1.1
Transaction Details Archive
-
eTRM - HXC Tables and Views 12.2.2
Used in Generic Upgrade