Search Results hxc_time_category_api




Overview
Explore in AI Chat

Overview

HXC_TIME_CATEGORY_API is a public PL/SQL API owned by the APPS schema that provides the supported programmatic interface for creating, maintaining, and removing time categories within Oracle E-Business Suite. In Oracle EBS 12.1.1 and 12.2.2, time categories form the backbone of timecard and time-entry processing: they define the classification applied to reported time (for example, regular, overtime, or absence), and they determine how that time is processed by downstream payroll, costing, and project accounting logic. The package encapsulates the validation and referential-integrity rules that govern the HXC_TIME_CATEGORIES schema, ensuring that time categories and their associated mapping components are inserted, changed, and deleted consistently whether the operation originates from an Oracle form, a concurrent program, or custom integration code. Because it is classified as an API in the ETRM metadata, it is the intended entry point for external or extension code, rather than direct DML against the underlying tables.

Key Procedures and Functions

  • CREATE_TIME_CATEGORY — Creates a new time category record, applying the API's validation rules and defaulting logic before persisting the definition to the base table.
  • UPDATE_TIME_CATEGORY — Modifies an existing time category, enforcing consistency between the category definition and any dependent configuration.
  • DELETE_TIME_CATEGORY — Removes a time category, including the associated cleanup of related component and mapping data.
  • SET_DYNAMIC_SQL_STRING — Builds or assigns the dynamic SQL text the package uses internally to process category components, supporting the flexible, metadata-driven behavior of the time category framework.
  • DELETE_OLD_COMPS — Purges obsolete or superseded component rows when a category definition changes, preventing orphaned configuration.
  • GET_COMPONENT_TYPE_NAME — Returns the descriptive name associated with a component type, used to translate internal type identifiers into readable values.

These six documented entry points together cover the full lifecycle of a time category, from creation through update and deletion, with supporting utilities for component handling.

Tables Accessed

The package operates primarily against HXC_TIME_CATEGORIES, the base table holding category definitions, and HXC_TIME_CATEGORY_COMPS, which stores the component rows that make up a category. HXC_MAPPING_COMPONENTS holds the mapping configuration that links categories to downstream processing, and is read and maintained as part of category definition changes. PLITBLM is a PL/SQL index-by table type used internally by the package, not a physical application table; it supports the array-based processing used by the component and dynamic SQL routines.

Usage Notes

HXC_TIME_CATEGORY_API is referenced by seven other packages in the EBS schema, including HXC_TCC_INS, HXC_TCC_UPD, HXC_TCC_DEL, HXC_HTC_UPD, HXC_ABSENCE_TYPE_ALIAS, HXC_PROJ_MANAGER_APPROVAL_PKG, and HXC_TIME_CATEGORY_HOOK. This dependency pattern indicates that the package is invoked both by the standard time category maintenance forms and by the absence-management, timecard-processing, and project approval flows that consume category definitions. Custom code and integration routines should call these procedures rather than performing direct inserts or updates on HXC_TIME_CATEGORIES, so that the same validation and component cleanup logic applied by the seeded forms is preserved. The presence of HXC_TIME_CATEGORY_HOOK among the referencing objects confirms that the package participates in the standard hook mechanism used to extend time category behavior in Oracle Time and Labor.