Results for “time_recipients”

36 results




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

Overview

APPS.HXC_APPLICATION_SETS_V is a reporting and integration view in Oracle E-Business Suite (available in 12.1.1 and 12.2.2) that presents application set definitions used by Oracle Time and Labor (OTL) and related HXC (Time and Labor) functionality. The view is a filtered projection of the HXC_ENTITY_GROUPS table, exposing only those entity groups whose ENTITY_TYPE is equal to the literal value 'TIME_RECIPIENTS'. In this context, an "application set" is a named entity group that identifies a collection of recipients of time information — for example, a grouping of employees, payrolls, or organizational units that receive timecard or time-related notifications and data under Oracle Time and Labor processing rules.

Because the view renames ENTITY_GROUP_ID to APPLICATION_SET_ID and NAME to APPLICATION_SET_NAME, it provides a more business-friendly, semantically consistent interface for developers and reports that need to refer to application sets rather than to the generic entity-group construct. This makes the object well suited for use in concurrent program extracts, BI Publisher data models, OAF pages, and custom PL/SQL that query application sets without embedding the underlying table's entity-type filter.

Underlying Base Objects

The view is defined over a single documented base object, HXC_ENTITY_GROUPS, which is referenced through a synonym in the APPS schema. The view text performs a straightforward selection from that table with an inline filter:

  • HXC_ENTITY_GROUPS (SYNONYM): the physical entity group table that stores entity group headers, including identity, type, version, and audit columns. The view restricts rows to ENTITY_TYPE = 'TIME_RECIPIENTS'.
  • ROWID: the base table ROWID is surfaced as ROW_ID for direct row addressing.

No joins, aggregations, or outer query blocks exist in the view definition. The relationship to the base table is therefore strictly one-to-one and filtered: every row returned by the view corresponds to exactly one TIME_RECIPIENTS row in HXC_ENTITY_GROUPS, and columns not projected by the view remain accessible only through the base table.

Key Columns

  • ROW_ID: the ROWID of the underlying HXC_ENTITY_GROUPS row; useful for high-performance row-level access and for tools that require a unique row identifier.
  • APPLICATION_SET_ID: alias of ENTITY_GROUP_ID, the primary key of the application set (entity group). Used to join to dependent tables that reference application sets, such as membership or recipient-detail tables keyed by entity group.
  • APPLICATION_SET_NAME: alias of NAME, the user-visible name of the application set. This is the value typically displayed in lists of values and reports.
  • OBJECT_VERSION_NUMBER: the optimistic locking version counter maintained by the underlying table; important when the view participates in updating or concurrency-controlled integration.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN: standard EBS WHO columns providing audit and accountability information for each application set.

Common Use Cases and Queries

Typical scenarios include validating that an application set exists before assigning time recipients, driving LOV queries, and extracting application set definitions for interfaces.

  • List all time-recipient application sets with their identifiers and names.
  • Retrieve a specific application set by ID or name for downstream processing.
  • Extract audit information for reconciliation and data-governance reporting.

Sample SQL:

  • SELECT application_set_id, application_set_name FROM apps.hxc_application_sets_v ORDER BY application_set_name;
  • SELECT application_set_id, application_set_name, last_update_date FROM apps.hxc_application_sets_v WHERE application_set_name LIKE :p_name;
  • SELECT application_set_name FROM apps.hxc_application_sets_v WHERE application_set_id = :p_id;

Because the view applies the 'TIME_RECIPIENTS' filter internally, callers do not need to add an ENTITY_TYPE predicate, reducing the risk of inadvertently including entity groups of other types.