Search Results get_query

Overview

APPS.HXC_SEEDDATA_PKG is a seed data utility package within the Oracle E-Business Suite Time and Labor (HXC) module. Its principal business function is to centralize the retrieval logic used by the HXC seed data loader (hxcseed.lct) and the HXCSEEDDATA form during seed data upload, download, and validation operations. Rather than embedding SQL statements separately in each loader or form region, the package exposes a small set of PL/SQL functions and procedures that dynamically construct queries by object type and return the corresponding values and legislation codes. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user and relies on APPS synonyms for access to the underlying HXC tables. The header comment dates the base specification to 2005 (hxcseeddatapkg.pkh 120.1), indicating a long-standing, stable interface that has been retained across the 12.1.1 and 12.2.2 releases.

The package also declares two public types: r_rec, a record representing a single seed data row (object identifier, object type, owner application, value, application name, code level required, HXC required flag, and standard WHO audit columns), and t_rec, a PL/SQL associative array of r_rec indexed by binary integer. These types are used to pass collections of seed data rows between the form or loader and the package.

Key Procedures and Functions

The documented interface comprises four program units:

• GET_QUERY — A function that returns the query text as a VARCHAR2 string. The query returned depends on the object type passed in, allowing callers to obtain the appropriate selection statement for a given category of seed data without hard-coding SQL.
• GET_VALUE — A function that accepts an object identifier and an object type, internally resolves the query via GET_QUERY, and returns the value corresponding to the object identifier. It is explicitly documented as being used by the hxcseed.lct loader in its download section.
• GET_LEGISLATION_CODE — A function that returns the legislation code based on the supplied object identifier and object type. Like GET_VALUE, it is consumed by the download section of the hxcseed.lct loader.
• HXC_SEEDDATA_BY_LEVEL_QUERY — A procedure that populates an OUT NOCOPY collection of type t_rec based on filtering criteria (object type, value, application name, and code level required) and returns a row count via an OUT NOCOPY parameter. This procedure backs the HXC_SEEDDATA_BY_LEVEL block of the HXCSEEDDATA form.

Tables Accessed

The package reads from the following HXC tables through APPS synonyms:

• HXC_ALIAS_DEFINITIONS — earnings and time alias definitions used in seed data resolution.
• HXC_APPROVAL_STYLES — time approval style definitions referenced during seed data queries.
• HXC_PREF_HIERARCHIES — preference hierarchy structures used for seed data levels.
• HXC_TIME_ENTRY_RULES — time entry rule definitions included in seed data sets.
• PLITBLM — an Oracle Forms internal table referenced in the context of the query logic.

Access to these tables supports the dynamic query construction performed by GET_QUERY and the direct retrieval performed by GET_VALUE and HXC_SEEDDATA_BY_LEVEL_QUERY, ensuring that seed data values and legislation codes are derived from the authoritative configuration tables rather than duplicated literals.

Usage Notes

HXC_SEEDDATA_PKG is invoked primarily by the hxcseed.lct seed data loader (download section, through GET_VALUE and GET_LEGISLATION_CODE) and by the HXCSEEDDATA form, whose HXC_SEEDDATA_BY_LEVEL block calls HXC_SEEDDATA_BY_LEVEL_QUERY. The metadata records that one other package references this package, confirming its role as a shared, load-time dependency. Customers and implementers typically encounter the package indirectly during Time and Labor setup and seed data migration rather than invoking it directly from custom code. Because the package is AUTHID CURRENT_USER, any caller must have the necessary privileges on the underlying HXC tables. The GET_QUERY function's dependence on object type means that support for a new seed data category generally requires extending the internal query list rather than altering the calling loader or form. In both 12.1.1 and 12.2.2 the interface remains unchanged, making it a reliable reference point when diagnosing seed data download discrepancies.