Results for “hxc_dynamic_templates”

24 results




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

Overview

APPS.HXC_TEMPLATE_SET_V is a reporting and integration view within the Oracle E-Business Suite Time and Labor (HXC) module. It exposes the set of timecard templates available to a user or responsibility by combining two distinct sources of template definitions: stored (public) templates maintained in the HXC_TEMPLATE_SUMMARY repository, and dynamic template definitions driven by lookup values. The view presents a normalized two-column result set consisting of a display name and an encoded identifier, allowing downstream forms, concurrent programs, and integrations to present a unified list of selectable templates without directly querying the underlying template and lookup tables.

Because the identifier column embeds a type discriminator prefix (PUBLIC or DYNAMIC), the view enables consumers to distinguish the origin of each template while still treating the collection as a single set. This is particularly relevant in self-service time entry configurations where both seeded dynamic templates and customer-defined public templates may be valid choices.

Underlying Base Objects

The view is defined over four documented base objects: HXC_TEMPLATE_SUMMARY (accessed through a synonym), HR_LOOKUPS (a view), the FND_PROFILE package, and the HR_API package. The first branch of the UNION selects from HXC_TEMPLATE_SUMMARY, filtering rows where TEMPLATE_TYPE equals 'PUBLIC'. Critically, this branch applies business group security logic using FND_PROFILE.VALUE('HR_CROSS_BUSINESS_GROUP') and FND_PROFILE.VALUE('PER_BUSINESS_GROUP_ID'): when cross business group access is disabled ('N'), the query restricts rows to the session's current business group; otherwise all business groups are visible.

The second branch draws from HR_LOOKUPS, filtering on LOOKUP_TYPE = 'HXC_DYNAMIC_TEMPLATES' and excluding the seeded entry with LOOKUP_CODE 'APP|HXT'. The reference to HR_API in the metadata reflects the profile and security infrastructure that governs business group access, ensuring the view is consistent with Oracle HRMS multi-tenancy rules.

Key Columns

  • NAME — The user-facing template label. For public templates this is TEMPLATE_NAME from HXC_TEMPLATE_SUMMARY; for dynamic templates it is the lookup MEANING.
  • CODE — A composite identifier. Public templates produce 'PUBLIC|' concatenated with the first 15 characters of the TEMPLATE_ID (via SUBSTR(TO_CHAR(...),1,15)). Dynamic templates produce 'DYNAMIC|' concatenated with the lookup_code. The prefix allows consumers to parse the template type and route processing accordingly.

Common Use Cases and Queries

A frequent requirement is to populate a list of values in a time entry form or to enumerate valid templates for a given responsibility. A basic query returns the full set:

SELECT name, code
FROM   apps.hxc_template_set_v
ORDER BY name;

When only customer-defined public templates are required, the discriminator prefix can be filtered:

SELECT name, code
FROM   apps.hxc_template_set_v
WHERE  code LIKE 'PUBLIC|%';

Dynamic templates can likewise be isolated with code LIKE 'DYNAMIC|%'. Because the query is driven by HR_CROSS_BUSINESS_GROUP and PER_BUSINESS_GROUP_ID profile options, callers should be aware that results are session- and responsibility-dependent; testing under the correct business group context is essential when validating that expected templates appear. The view is typically not used for updates and should be treated as read-only reference data for reporting, integration bridges, and configuration validation.