Results for “hxc_template_set_v”

22 results




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

Overview

HXC_TEMPLATE_SET_V is a database view owned by the APPS schema within Oracle E-Business Suite, belonging to the HXC – Time and Labor Engine product. Its purpose is to present a unified list of selectable timecard templates to consuming forms, concurrent processes, and reporting layers. The view consolidates two distinct template sources into a single, consistently shaped result set: public templates defined in the template summary repository, and dynamic templates defined through a lookup type. It is therefore a presentation and validation view rather than a transactional entity, and it exposes no insert, update, or delete semantics of its own.

The view is significant because downstream Time and Labor configuration, including the assignment of template sets to business groups and the selection of templates within self-service timecard pages, depends on a reliable enumeration of valid template names and codes. By centralizing that enumeration, the view ensures consistent behavior across Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view text is a UNION of two SELECT statements, and the documented base objects include FND_PROFILE (PACKAGE), HR_API (PACKAGE), HR_LOOKUPS (VIEW), and HXC_TEMPLATE_SUMMARY (SYNONYM).

  • HXC_TEMPLATE_SUMMARY (HTS) supplies the public template rows. The view filters on TEMPLATE_TYPE = 'PUBLIC'.
  • FND_PROFILE.VALUE is used within a DECODE to control business group scoping. When the profile HR_CROSS_BUSINESS_GROUP is 'N', the query restricts rows to the current business group returned by PER_BUSINESS_GROUP_ID; otherwise it returns all business groups.
  • HR_LOOKUPS (HL) supplies dynamic templates where LOOKUP_TYPE = 'HXC_DYNAMIC_TEMPLATES', excluding the lookup code 'APP|HXT'.
  • HR_API (PACKAGE) is documented as a referenced object, reflecting the standard HR security and business group resolution infrastructure used by the underlying HR views and profile calls.

Key Columns

The view exposes a deliberately narrow projection of two columns, which simplifies consumption by callers that only need a display value and a technical identifier.

  • NAME — For public templates this is TEMPLATE_NAME; for dynamic templates it is the lookup MEANING. It is the user-facing label presented in list of values and selection interfaces.
  • CODE — A composite identifier. Public rows are prefixed with the literal 'PUBLIC' followed by a pipe delimiter and the TEMPLATE_ID truncated to 15 characters. Dynamic rows are prefixed with 'DYNAMIC', a pipe delimiter, and the HR_LOOKUPS LOOKUP_CODE.

The 'typed prefix' convention in CODE allows consumers to distinguish the origin of a template without additional joins, and the 15-character truncation of TEMPLATE_ID is a legacy compatibility measure consistent with older Form-based code paths.

Common Use Cases and Queries

Typical uses include populating template selection lists, validating a template code captured in a configuration table, and reconciling template availability across business groups.

  • Listing all available templates: SELECT name, code FROM hxc_template_set_v ORDER BY name;
  • Restricting to public templates only: SELECT name, code FROM hxc_template_set_v WHERE code LIKE 'PUBLIC|%';
  • Identifying dynamic templates: SELECT name, code FROM hxc_template_set_v WHERE code LIKE 'DYNAMIC|%';
  • Resolving a display name for a stored code: SELECT name FROM hxc_template_set_v WHERE code = :p_code;

Because business group filtering is applied through FND_PROFILE within the view definition, the effective row set depends on the profile settings of the session or responsibility under which the query executes. These characteristics should be accounted for when the view is used in custom reports or integrations.