Results for “detail_comment_text”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
HXC_APPROVAL_DETAILS_V is a reporting and integration view owned by the APPS schema within the HXC (Time and Labor Engine) product of Oracle E-Business Suite. It surfaces approval-related detail records associated with time building blocks, consolidating approval status, resource identification, detail measures, comments, and descriptive flexfield attribute values into a single queryable structure. The view occupies an important position in the Time and Labor approval workflow, where submitted timecards and their constituent detail lines must be routed through one or more approval steps before being transferred or costed. Rather than requiring custom reports to join multiple underlying approval and detail tables directly, this view presents a denormalized projection that exposes the approval status of individual time building blocks together with the corresponding detail-level measures and attribute context.
Because approval data in Time and Labor straddles both the approval header structure and the granular timecard detail records, the view is particularly useful for building approval dashboards, audit reports, and downstream integrations that need to know the state of each resource's submitted time. It carries the object version number, which supports optimistic locking patterns commonly used by the OTL (Oracle Time and Labor) middle tier and self-service pages, and it exposes the resource identifier that ties an approval record back to the person or resource that owns the time.
Underlying Base Objects
The documented base objects referenced by HXC_APPROVAL_DETAILS_V span several Time and Labor views and shared HR packages. The Time and Labor specific views are HXC_APPLICATION_PERIODS_V, HXC_MAPPING_ATTRIBUTES_V, HXC_TIMECARDS_V, HXC_TIMECARD_DAYS_V, and HXC_TIMECARD_DETAILS_V. These supply the timecard context, day-level breakdown, detail-level measures, and the flexfield mapping metadata that drives the DECODE logic in the view text. Shared HR objects include PER_PEOPLE_F, the date-tracked people view, and the packages HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. HR_SECURITY is significant because it enforces the security profile hierarchy that restricts which employees a given responsibility may query, while HR_PERSON_NAME and HR_GENERAL provide name formatting and lookup utilities.
The view text joins approval records (aliased HAP, carrying TIME_BUILDING_BLOCK_ID, OBJECT_VERSION_NUMBER, RESOURCE_ID, and APPROVAL_STATUS) against timecard detail records (aliased HTDETAIL, carrying DETAIL_MEASURE, DETAIL_COMMENT_TEXT, and the DETAIL_ATTRIBUTE1 through DETAIL_ATTRIBUTE30 columns). The DECODE expressions resolve the correct flexfield attribute based on mapping metadata held in HXC_MAPPING_ATTRIBUTES_V, ensuring that descriptive flexfield segments are surfaced under their configured context and segment name rather than as a flat positional attribute.
Key Columns
- TIME_BUILDING_BLOCK_ID — Identifier of the time building block to which the approval applies; the primary correlation key back to the timecard structure.
- OBJECT_VERSION_NUMBER — Optimistic locking token used to detect concurrent modification of approval records.
- RESOURCE_ID — The resource (typically a person or assignment) whose time is under approval; joins to PER_PEOPLE_F and is filtered by HR_SECURITY.
- APPROVAL_STATUS — The current disposition of the approval record, such as approved, rejected, or pending.
- DETAIL_MEASURE — The measured quantity on the timecard detail line, generally hours or another configured unit of measure.
- DETAIL_COMMENT_TEXT — Free-text comment attached to the detail line, often used to justify exceptions.
- DETAIL_ATTRIBUTE_CATEGORY and DETAIL_ATTRIBUTE1..30 — Descriptive flexfield context and segment values on the detail line, resolved through the mapping attributes view.
Common Use Cases and Queries
Typical uses include approval status reporting, exception auditing for lines with comments, and extracting detail measures for downstream payroll or project costing integration. A representative query follows:
SELECT resource_id, time_building_block_id, approval_status, detail_measure, detail_comment_text
FROM apps.hxc_approval_details_v
WHERE approval_status = 'APPROVED';
Because the view is defined on date-effective and security-enabled base objects, queries should be run under a responsibility whose HR security profile appropriately restricts the returned RESOURCE_ID values. Developers should also apply bind variables to RESOURCE_ID or TIME_BUILDING_BLOCK_ID to avoid full scans across large timecard volumes.
-
View: HXC_APPROVAL_DETAILS_V 12.1.1
APPS.HXC_APPROVAL_DETAILS_V·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore HXC module →
-
View: HXC_APPROVAL_DETAILS_V 12.2.2
APPS.HXC_APPROVAL_DETAILS_V·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·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 →
-
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 →
-
eTRM - HXC Tables and Views 12.1.1
Transaction Details Archive
-
eTRM - HXC Tables and Views 12.2.2
Used in Generic Upgrade