Search Results hxc_hrp_bus




Overview
Explore in AI Chat

Overview

HXC_HRP_BUS is the business-layer PL/SQL package body for the HR Recurring Periods module within Oracle E-Business Suite, owned by the APPS schema. In Oracle EBS 12.1.1 and 12.2.2, the HXC product family covers time and labor processing, and the HRP designation identifies the recurring period configuration logic that governs how Oracle Time and Labor (OTL) structures repeating time periods for timecard entry, reporting, and payroll aggregation. The package encapsulates the business rules that validate, create, update, and remove recurring period definitions, while exposing subordinate validation and utility logic through a companion shadow package, HXC_HRP_SHD. It also layers security-group context handling and legislative/legal-entity context retrieval on top of the underlying data model, ensuring that recurring period configuration is properly isolated across business groups and operating units. The object is recorded as VALID in the ETRM repository for 12.2.2, confirming it is an active, supported component of the application. Its API classification is OTHER, indicating it is an internal business API rather than a formally published public interface, though it is referenced by three other packages within the APPS schema.

Key Procedures and Functions

ETRM documents six procedures and functions in HXC_HRP_BUS. Their names describe their responsibilities, and no parameter signatures are published.

  • SET_SECURITY_GROUP_ID — Establishes the security group context under which subsequent operations in the session execute, enabling business-group-level data isolation consistent with the Oracle EBS security model.
  • RETURN_LEGISLATION_CODE — Returns the legislation code applicable to the current session or business group, which drives legislative validation behavior in the recurring period logic.
  • INSERT_VALIDATE — Performs the validation steps required before inserting a new recurring period record, confirming mandatory values, date ranges, and reference integrity.
  • UPDATE_VALIDATE — Validates modifications to existing recurring period records prior to update, protecting against invalid state changes or overlapping or conflicting configurations.
  • CHK_DELETE — Determines whether a recurring period record may be deleted, checking for downstream dependencies or referential constraints.
  • DELETE_VALIDATE — Executes the final validation gate before a delete is committed, complementing CHK_DELETE with pre-deletion business rule enforcement.

Tables Accessed

The package operates directly on two documented tables, accessed through APPS synonyms:

  • HXC_RECURRING_PERIODS — The primary entity table holding recurring period definitions. INSERT_VALIDATE, UPDATE_VALIDATE, DELETE_VALIDATE, and CHK_DELETE all center on this table, governing the creation, modification, and removal of period records.
  • PER_TIME_PERIOD_TYPES — Provides the time period type reference data that classifies recurring periods, used to validate that a chosen period type is valid and applicable to the operating context.

The package also references PER_BUSINESS_GROUPS, HXC_PREFERENCE_EVALUATION, HXC_HRP_SHD, HXC_HRP_BUS, HR_API, HR_UTILITY, FND_MESSAGE, and DUAL through its dependency list. FND_MESSAGE supplies user-facing error text for validation failures, HR_API and HR_UTILITY provide HR infrastructure calls, and HXC_PREFERENCE_EVALUATION supports evaluation of time and labor preferences that may refine recurring period behavior.

Usage Notes

HXC_HRP_BUS is a server-side business package typically invoked indirectly rather than called directly by end users. It is most commonly reached through the Oracle Time and Labor configuration forms that maintain recurring period setup, where form-level triggers delegate insert, update, and delete operations to the INSERT_VALIDATE, UPDATE_VALIDATE, DELETE_VALIDATE, and CHK_DELETE entry points. Because the ETRM metadata states the package is not referenced by any database object, there are no recorded database-level dependents such as triggers or views; instead, the three referencing packages are PL/SQL callers within the APPS schema. Custom extensions and concurrent programs that need to create or maintain recurring periods programmatically should invoke these documented procedures so that security group context, legislation checks, and preference evaluation remain consistent with delivered functionality. Direct DML against HXC_RECURRING_PERIODS is discouraged, since validation logic, message handling, and shadow-table synchronization in HXC_HRP_SHD would be bypassed. When troubleshooting, confirm that SET_SECURITY_GROUP_ID has been called before invoking validation procedures, as business-group context directly affects which records are visible and valid.