Search Results hr_lei_bus




Overview

HR_LEI_BUS is a business logic package in the APPS schema that supports the Legislative and External Information (LEI) framework within Oracle Human Resources. The LEI framework allows organizations to capture jurisdiction-specific statutory, regulatory, and reporting information that is not accommodated by the standard person, assignment, or organization data model. HR_LEI_BUS acts as the middle-tier business logic layer of this framework, sitting between the database-level tables that persist legislative data and the user-facing forms, APIs, and concurrent processes that consume it.

The package is classified in ETRM as an OTHER API, meaning it is not a public, supported interface in the same sense as an Open Interface or a fully documented PL/SQL API. It is an internal component of the HR legislative data architecture. Its role is to encapsulate validation rules that govern the integrity of legislative information records before they are committed, updated, or removed by the corresponding Data Manipulation Logic. In this capacity it is closely coupled with the HR_LEI_SHD shadow package and the family of HR_LEI_DEL, HR_LEI_INS, and HR_LEI_UPD packages that perform the physical insert, update, and delete operations against the legislative information tables.

Key Procedures and Functions

The ETRM metadata documents three procedures in HR_LEI_BUS, each corresponding to a distinct lifecycle event for legislative information records:

  • INSERT_VALIDATE — Executes the validation logic required before a new legislative or external information record is created. It confirms that the record's attributes are internally consistent and compatible with the configuration of the associated information type and location before the insert is allowed to proceed.
  • UPDATE_VALIDATE — Applies the equivalent validation checks when an existing legislative information record is modified. It ensures that changes do not violate the framework's constraints or produce inconsistent state relative to related records.
  • DELETE_VALIDATE — Evaluates whether an existing legislative information record may be removed. This guards against deletion of records that remain referenced or that are required for statutory continuity.

The procedures are intended to be invoked as guards by the HR_LEI_INS, HR_LEI_UPD, and HR_LEI_DEL packages respectively. The metadata does not publish parameter lists for these procedures, and the ETRM record treats them as internal validation entry points rather than standalone callable APIs.

Tables Accessed

HR_LEI_BUS operates against four core Human Resources tables, accessed through APPS synonyms:

  • HR_LOCATIONS_ALL — The base location definition table. Legislative information is frequently keyed to a specific location or jurisdiction, so validation must confirm that the referenced location exists and is valid for the information type being recorded.
  • HR_LOCATION_EXTRA_INFO — Stores the additional, attribute-flexible information attached to a location. This is the principal target of the LEI insert, update, and delete operations whose data HR_LEI_BUS validates.
  • HR_LOCATION_INFO_TYPES — Defines the configured information types that may be associated with a location. Validation depends on this table to confirm that the requested information type is a legitimate, enabled choice.
  • HR_ORGANIZATION_INFORMATION — Holds organization-level information records. It is used to verify consistency between legislative information attached to a location and the organizational context in which that location operates.

Usage Notes

HR_LEI_BUS is an internal package and is not intended for direct invocation by customer-written code. It is called indirectly whenever legislative information is entered, changed, or removed through the standard HR forms that maintain location and organization extra information. The HR_LEI_INS, HR_LEI_UPD, and HR_LEI_DEL packages, which are themselves referenced by HR_LEI_BUS, are the operational layer that enforces the validate-then-manipulate sequence.

Because the package is tightly coupled to HR_LEI_SHD and the surrounding HR_LEI_* package family, customizations should not modify its logic. Extensions that require additional validation should generally be implemented through supported APIs or form personalization rather than by altering this package. The metadata presented here reflects Oracle E-Business Suite 12.2.2; behavior in 12.1.1 is functionally equivalent for the documented procedures, though the underlying table structures may differ slightly. Oracle's proprietary and confidential designations apply to all associated source.