Search Results pay_event_groups_bk1

Overview

PAY_EVENT_GROUPS_BK1 is a generated PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the API taxonomy as OTHER. It belongs to the Oracle Payroll (PAY) product family and forms part of the Event Groups API stack. The "BK1" suffix identifies this package as a backward-compatibility or stub layer produced by the Oracle HRMS API Hook Pre-processor, as evidenced by the header comment block ("Code generated by the Oracle HRMS API Hook Pre-processor") and the "$Header: pyevgapi.pkb" marker, which traces the source to the Event Groups API (pyevgapi).

Event groups in Oracle Payroll define collections of payroll events, together with their proration behaviour and associated time definitions, used primarily in absence and proration processing. The business purpose of PAY_EVENT_GROUPS_BK1 is to expose a stable, generated entry point for the creation of event group definitions while the substantive business logic resides in the corresponding entity-level APIs. This package therefore acts as a thin veneer over the core event groups API rather than as a self-contained implementation.

Key Procedures and Functions

The package body exposes two documented procedures, both of which are creation entry points:

• CREATE_EVENT_GROUP_A — The primary create routine for an event group. It represents the full-signature variant of the create operation, intended to accept the complete set of event group attributes required to persist a new definition, including effective dating, naming, event group type, proration type, business group ownership, legislation, time definition, and object version information.
• CREATE_EVENT_GROUP_B — A reduced-signature create routine. Its parameter profile omits the event group identifier and object version number present in variant A, indicating that it is intended for use before the surrogate key and versioning metadata have been assigned, or for internal callers that rely on the API to derive those values.

Both procedures are stubs. Their bodies contain only hr_utility.set_location tracing calls marking entry and exit points; no business logic is present in the body as documented. This is characteristic of pre-processor-generated hook packages, where the real implementation is delivered through the hook mechanism and the calling API, not through the generated text itself.

Tables Accessed

The ETRM metadata for PAY_EVENT_GROUPS_BK1 does not document any direct table references via APPS synonyms. This is consistent with the stub nature of the package: because the procedure bodies contain no DML, no table access paths are recorded. Any persistence of event group data is performed by the underlying Event Groups API and its associated database objects (notably the PAY_EVENT_GROUPS entity) at the point where the generated hook is invoked, rather than within this package.

Usage Notes

PAY_EVENT_GROUPS_BK1 should not be called directly by custom code. It is a generated hook package whose procedures are invoked by the HRMS API framework during the execution of the parent Event Groups API. The ETRM metadata records that the package is referenced by one other package, confirming its role as a dependent component rather than a user-facing API surface.

In release 12.1.1 and 12.2.2, the package remains available primarily for backward compatibility with callers that were coded against the pre-processor-generated signatures. Typical invocation occurs indirectly through forms-based maintenance of payroll event groups, through concurrent or batch processes that create event group definitions, or through PL/SQL that calls the higher-level Event Groups API. Developers integrating custom logic should target the supported parent API and treat PAY_EVENT_GROUPS_BK1 as an internal implementation artefact that is regenerated by Oracle and therefore subject to change.