Results for “application_set_name”

44 results




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

Overview

HXC_APPLICATION_SETS_V is a validation view owned by the APPS schema within the HXC – Time and Labor Engine product family. It exposes a filtered, business-friendly projection of entity groups defined in the Time and Labor repository and presents them under the label "application set." In Oracle EBS 12.1.1 and 12.2.2, the view is registered in ETRM as VALID, meaning its compiled definition is consistent with the referenced base objects in the reporting database.

The view plays a specific role in reporting and integration: it isolates the subset of entity groups whose ENTITY_TYPE equals 'TIME_RECIPIENTS'. Rather than querying HXC_ENTITY_GROUPS directly and applying the entity-type filter manually, consumers can select from HXC_APPLICATION_SETS_V to obtain only those groups relevant to time recipient processing. Practically, the view is a convenience layer that renames ENTITY_GROUP_ID as APPLICATION_SET_ID and NAME as APPLICATION_SET_NAME, allowing downstream reports, interfaces, and lookups to reference "application set" semantics without coupling to the underlying column naming. Because it is a view rather than a table, it stores no data of its own and always reflects the current state of the base entity groups.

Underlying Base Objects

The view is defined over a single documented base object: HXC_ENTITY_GROUPS, accessed through its APPS synonym. The view text joins or, more precisely, projects from this table with a restricting predicate, as shown in the ETRM definition:

  • Source object: HXC_ENTITY_GROUPS HEG (SYNONYM).
  • Filter predicate: WHERE HEG.ENTITY_TYPE = 'TIME_RECIPIENTS'.
  • Alias convention: the base table is aliased HEG, and each selected column is qualified accordingly.

No joins to other tables are present in the documented view text, so the relationship between view and base object is one-to-many in principle (one row per qualifying entity group row) but strictly a row-preserving projection with a filter. Consequently, any insert, update, or delete performed against entity groups of type TIME_RECIPIENTS in HXC_ENTITY_GROUPS is immediately visible through this view. The view itself is not updatable through simple DML unless an INSTEAD OF trigger exists, and none is documented. Referential integrity and auditing characteristics therefore inherit directly from HXC_ENTITY_GROUPS.

Key Columns

  • ROW_ID – The ROWID of the underlying HXC_ENTITY_GROUPS row, useful for row-level identification and troubleshooting duplicate or stale records.
  • APPLICATION_SET_ID – Maps to ENTITY_GROUP_ID. This is the primary identifier consumers search for, and it is the column most commonly used in joins to setup, recipient, and assignment tables.
  • APPLICATION_SET_NAME – Maps to NAME, the user-visible name of the entity group, used in list-of-values and report labels.
  • OBJECT_VERSION_NUMBER – Optimistic locking counter inherited from the base table; changes on each update.
  • CREATED_BY, CREATION_DATE – Standard WHO columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns recording the most recent modification user, timestamp, and login.

Common Use Cases and Queries

Typical scenarios include validating that an application set exists before loading time recipient mappings, populating a list of values in a concurrent program parameter, and reconciling configuration between environments. A basic lookup by identifier or name is shown below.

  • Retrieve a set by ID: SELECT application_set_id, application_set_name FROM hxc_application_sets_v WHERE application_set_id = :p_id;
  • List all sets for a picklist: SELECT application_set_id, application_set_name FROM hxc_application_sets_v ORDER BY application_set_name;
  • Audit recent changes: SELECT application_set_id, application_set_name, last_updated_by, last_update_date FROM hxc_application_sets_v WHERE last_update_date >= :p_since;
  • Join to related setup data on APPLICATION_SET_ID to resolve a recipient or assignment to its owning set.

Because the view filters on ENTITY_TYPE = 'TIME_RECIPIENTS', queries against it inherently exclude other entity group categories, and no additional type predicate is required. For high-volume extraction, joining directly to HXC_ENTITY_GROUPS may allow more selective indexing, but the view remains the canonical, documented access path for application set metadata in HXC.