Results for “parent_object_version”

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

Overview

The view APPS.HXC_RESOURCE_TIMECARD_DETAIL_V is a reporting and integration object within the Oracle E-Business Suite Time and Labor Engine (HXC) product family. It presents timecard detail rows for resources together with their associated building-block mapping attributes, joining timecard detail data to the mapping metadata that describes how those attributes should be interpreted. The view carries a VALID status in the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2.

Users searching on the term "object_version" are typically interested in the concurrency-control columns exposed by this view. Notably, the view surfaces two object version columns — OBJECT_VERSION (aliased from DETAIL_OBJECT_VERSION) and PARENT_OBJECT_VERSION (from DETAIL_PARENT_OBJECT_VERSION). These columns support optimistic locking semantics, allowing integrators and reporting tools to detect whether a timecard detail record has changed since it was last read, which is essential for safe updates in Time and Labor timecard processing.

Underlying Base Objects

The view is defined over two primary HXC views, combined with a DECODE-based transformation. Per the ETRM documentation, the referenced base objects are HXC_TIMECARD_DETAILS_V (VIEW), HXC_MAPPING_ATTRIBUTES_V (VIEW), and HR_GENERAL (PACKAGE). The core SELECT joins HXC_TIMECARD_DETAILS_V (aliased HTDETAIL) to HXC_MAPPING_ATTRIBUTES_V (aliased HMA) on the condition HTDETAIL.DETAIL_BLD_BLK_INFO_TYPE_ID = HMA.BLD_BLK_INFO_TYPE_ID.

The HR_GENERAL package is referenced as a supporting object, typically supplying session or business-group context used indirectly by the underlying timecard views. The join on building-block information type ID links each timecard detail to the mapping attribute that governs which of the thirty detail attribute columns is relevant, and supplies the MAP and FIELD_NAME descriptors for that attribute.

Key Columns

• TIMECARD_ID — The detail timecard identifier (source: DETAIL_TIMECARD_ID), the primary key of the detail record.
• OBJECT_VERSION — The detail record's object version (source: DETAIL_OBJECT_VERSION), used for optimistic locking on the timecard detail row.
• PARENT_TIMECARD_ID — The parent timecard identifier (source: DETAIL_PARENT_TIMECARD_ID), linking the detail to its header/parent timecard.
• PARENT_OBJECT_VERSION — The parent record's object version (source: DETAIL_PARENT_OBJECT_VERSION), enabling optimistic locking at the parent timecard level.
• RESOURCE_ID — The resource (typically person or assignment) to whom the timecard detail belongs.
• SCOPE — Indicates the scope of the detail record.
• ATTRIBUTE_ID — The resolved attribute value, produced by the DECODE over DETAIL_ATTRIBUTE1 through DETAIL_ATTRIBUTE30, selected according to HMA.SEGMENT.
• MAP — Mapping descriptor from HXC_MAPPING_ATTRIBUTES_V (HMA.MAP).
• FIELD_NAME — Field name from HXC_MAPPING_ATTRIBUTES_V (HMA.FIELD_NAME).

Common Use Cases and Queries

A typical use is retrieving the mapped attribute value for a specific timecard detail. The following query selects detail rows for a resource and exposes the object version columns for change detection.

SELECT timecard_id,
       object_version,
       parent_timecard_id,
       parent_object_version,
       resource_id,
       scope,
       attribute_id,
       map,
       field_name
FROM   apps.hxc_resource_timecard_detail_v
WHERE  resource_id = :p_resource_id
ORDER BY timecard_id;

Integration and middleware scenarios frequently filter on OBJECT_VERSION and PARENT_OBJECT_VERSION to validate that a cached detail or parent timecard remains current before posting updates, using these columns as the optimistic-locking token. Reporting scenarios group by MAP and FIELD_NAME to analyze which building-block attributes drive timecard values.

SELECT map, field_name, COUNT(*)
FROM   apps.hxc_resource_timecard_detail_v
GROUP BY map, field_name;

Because the view joins two HXC views and applies a wide DECODE across thirty attribute columns, queries should be restricted by RESOURCE_ID, TIMECARD_ID, or a date/business-group predicate where available to avoid full scans over the underlying timecard detail data.