Search Results per_apl_bus




Overview
Explore in AI Chat

Overview

APPS.PER_APL_BUS is a validation business (BUS) layer package body in the Oracle E-Business Suite Human Resources (Oracle HRMS) product family. The "APL" mnemonic corresponds to the Applications entity, which in Oracle HRMS represents an application submitted by a person for a position, requisition, or recruitment vacancy. The package therefore provides the server-side business rules and row-level validation logic for records held in the PER_APPLICATIONS table, which stores applicant and application data in the iRecruitment and Oracle Recruiting (Advanced Sourcing) functional areas.

Consistent with Oracle EBS application architecture, PER_APL_BUS forms the middle tier of a three-part implementation. A shadow (SHD) package, PER_APL_SHD, performs the actual DML against the base table; PER_APL_BUS wraps that shadow layer with validation, error handling, and business-governance logic; and PER_APL_API exposes the callable public interface. This separation allows Oracle to change validation rules without altering the underlying table structure, and it enforces a uniform set of checks whether a record is created through a form, a concurrent program, or a web service.

Key Procedures and Functions

The ETRM documentation identifies eight callable procedures and functions for this package. Their documented purposes are as follows:

  • INSERT_VALIDATE — Validates a candidate application row before insertion into PER_APPLICATIONS, ensuring mandatory and business-rule conditions are satisfied.
  • UPDATE_VALIDATE — Validates changes to an existing application record, including date and status transitions, before the record is updated.
  • DELETE_VALIDATE — Determines whether an application row may be removed, protecting records that are referenced by downstream recruitment or assignment data.
  • CHK_PROJECTED_HIRE_DATE — Verifies the projected hire date supplied for an application falls within acceptable bounds relative to the business group and person type.
  • CHK_DATE_RECEIVED_PERSON_ID — Checks the date the application was received in conjunction with the person identifier, ensuring the combination is valid.
  • CHK_DATE_END — Validates the end date of an application, typically enforcing that it does not precede the start or received date.
  • CHK_TERMINATION_REASON — Validates the termination reason captured when an application is closed or withdrawn.
  • RETURN_LEGISLATION_CODE — A function that returns the legislation code applicable to the application, driving localized validation and date-format rules.

Tables Accessed

The package reads from three principal tables, accessed through APPS synonyms. PER_APPLICATIONS is the primary subject table containing the application records being validated. PER_ALL_PEOPLE_F, the date-tracked people table, is queried to resolve the applicant's or employee's person identifier and to confirm the associated person record is effective on the relevant date. PER_PERSON_TYPES supplies the person type definitions used by CHK_PROJECTED_HIRE_DATE and related checks to determine valid hiring behavior. The package also draws on HR_API, HR_UTILITY, HR_DFLEX_UTILITY, HR_MULTI_MESSAGE, and APP_EXCEPTION for shared error messaging, flexfield validation, and exception construction. Because the DML itself is delegated to PER_APL_SHD, the BUS layer is principally a read and validation layer.

Usage Notes

PER_APL_BUS is not intended to be called directly by end users or custom code. It is invoked internally by the higher-level PER_APL_API package, which is the supported entry point for creating, updating, and deleting applications. The ETRM dependency record states that the package is referenced by three other database objects and that it is not referenced by any object outside that set, confirming its role as an internal implementation unit. Typical invocation paths include the iRecruitment and Applicant Entry forms, concurrent programs that load or reconcile applicant data, and Oracle-provided integration flows that submit applications through the API. Customizations that require modified recruitment validation should ideally extend the API layer rather than alter this package, because patches and upgrades to Oracle HRMS will overwrite changes made to PER_APL_BUS directly.