Results for “hxc_application_set_comps_v”

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

Overview

APPS.HXC_APPLICATION_SET_COMPS_V is a reporting and integration view in the Oracle E-Business Suite Time and Labor Engine (HXC) product family, valid in both 12.1.1 and 12.2.2. It presents the association between application sets (internally modeled as entity groups) and the time recipients that are members of those sets. In ETRM terminology, an "application set" defines a named collection of time recipients used to scope timecard, approval, and transfer-related processing. The view flattens the underlying entity-group membership table by joining it to the time recipient master, exposing a resolved recipient name (TIME_RECIPIENT_NAME) alongside the surrogate identifier (TIME_RECIPIENT_ID).

Because the view is maintained by Oracle and marked VALID in the APPS schema, it is a supported read-only access point for reporting layers, concurrent programs, and inbound/outbound integrations that need to enumerate the recipients belonging to an application set without writing joins against the base HXC tables themselves. This makes it particularly useful where a query is driven by a user-supplied search term such as time_recipient_name, since the name is surfaced directly rather than requiring a lookup.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through public synonyms owned by APPS:

• HXC_TIME_RECIPIENTS (aliased TR) — the time recipient master table, furnishing the recipient name and identifier.
• HXC_ENTITY_GROUP_COMPS (aliased EGC) — the entity group component table, furnishing the membership rows that link an application set (entity group) to its member entities.

The join is an inner join constrained by EGC.ENTITY_TYPE = 'TIME_RECIPIENTS' and TR.TIME_RECIPIENT_ID = EGC.ENTITY_ID. The entity-type filter is significant: HXC_ENTITY_GROUP_COMPS is a generic membership table that can hold multiple entity types, and this view restricts its output to time recipient members only. Consequently, only application sets that contain time recipients will produce rows.

Key Columns

• ROW_ID — the ROWID of the underlying HXC_ENTITY_GROUP_COMPS row, exposed for uniqueness and update targeting.
• APPLICATION_SET_COMP_ID — the component identifier of the membership record; maps to HXC_ENTITY_GROUP_COMPS.ENTITY_GROUP_COMP_ID.
• APPLICATION_SET_ID — the parent application set (entity group) identifier; maps to ENTITY_GROUP_ID.
• TIME_RECIPIENT_ID — the recipient identifier; maps to EGC.ENTITY_ID and TR.TIME_RECIPIENT_ID.
• TIME_RECIPIENT_NAME — the descriptive recipient name drawn from HXC_TIME_RECIPIENTS.NAME. This is the column most frequently targeted by name-based searches.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns carried through from the membership record for auditing and optimistic locking.

Common Use Cases and Queries

The primary scenario is resolving which recipients belong to a given application set, or conversely which sets include a given recipient. A name-based lookup, matching the time_recipient_name search term, is typical:

• List all recipients in a specific application set.
• Find all application sets containing a recipient whose name matches a pattern.
• Feed approval or transfer integration processes with the resolved recipient list.

Representative SQL:

• SELECT application_set_id, time_recipient_id, time_recipient_name FROM apps.hxc_application_set_comps_v WHERE application_set_id = :set_id ORDER BY time_recipient_name;
• SELECT application_set_id, time_recipient_name FROM apps.hxc_application_set_comps_v WHERE UPPER(time_recipient_name) LIKE UPPER('%' || :name || '%');