Results for “hxc_time_entry_rule_group_bk_1”

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

Overview

The APPS.HXC_TIME_ENTRY_RULE_GROUP_BK_1 package body is a generated Oracle HRMS API hook package within the Oracle Time and Labor (OTL) module of Oracle E-Business Suite. Its identifier prefix, HXC, corresponds to the Time and Labor schema, and the BK_1 suffix identifies it as a backward-compatibility hook generated by the Oracle HRMS API Hook Pre-processor. As confirmed by the source header ($Header: hxctegapi.pkb 120.0 2005/05/29 05:58:53 generated noship $) and the generation timestamp of 2007/01/03, the package is a programmatically generated stub that exposes hook points corresponding to the business logic of the underlying Time Entry Rule Group API. In EBS 12.1.1 and 12.2.2, such hook packages allow customer extensions and Oracle's own layered logic to intercept or augment the standard API processing without modifying the base API package. The package is owned by APPS and classified as OTHER in the ETRM metadata, reflecting its role as supporting generated code rather than a standalone public API.

Key Procedures and Functions

The package body exposes two documented procedures, both of which are empty hook stubs containing only entry and exit tracing via hr_utility.set_location:

• CREATE_TIME_ENTRY_RULE_GROUP_A — The "before" hook invoked during creation of a time entry rule group. It marks the entry point of the hook sequence at location 10 and the exit at location 20, providing an extension point where custom pre-processing logic may be inserted.
• CREATE_TIME_ENTRY_RULE_GROUP_B — The "after" hook for the same creation operation. Like its counterpart, it contains only tracing calls, marking the post-processing extension point at locations 10 and 20.

Both procedures accept parameters mirroring the parent API — notably a time entry rule group identifier, an object version number, and a name — but the API Hook Pre-processor generates them strictly as empty containers. No business logic, validation, or DML is implemented in the shipped body. This package is referenced by one other package, which supplies the actual invocation context for these hooks.

Tables Accessed

The ETRM metadata documents no tables referenced via APPS synonyms for this package body. This is consistent with its generated stub nature: the procedures perform no SQL operations, and the underlying DML against the time entry rule group entity is executed by the parent API package (typically HXC_TIME_ENTRY_RULE_GROUP_API or its related public wrapper). Any table access associated with creating a time entry rule group occurs in that base API, not in this hook package. Consequently, no direct read or write activity against Time and Labor configuration tables should be attributed to HXC_TIME_ENTRY_RULE_GROUP_BK_1 itself.

Usage Notes

This package is not intended to be called directly by forms, concurrent programs, or custom code. It is invoked internally by the parent Time Entry Rule Group API during the create operation, following the standard Oracle HRMS hook pattern in which the API calls the _A hook before its main processing and the _B hook afterward. Because the shipped procedures are empty, the package has no functional effect unless a customer or Oracle extension populates the hook bodies. Customizations should avoid modifying the generated body directly; instead, extensions should be implemented through supported API hook mechanisms or by wrapping the parent API, so that the generated code remains consistent with Oracle's pre-processor output. The only runtime footprint of the package in its delivered state is the hr_utility.set_location tracing, which writes to the HR utility location stack and can aid debugging of the API call sequence.