Search Results chk_correspondence_language

Overview

APPS.PER_PER_BUS1 is the business-rule validation package body that supports the People (PER) entity in Oracle EBS Human Resources. It belongs to the standard Oracle HRMS "BUS" (business) layer, a generated companion to the PER_PER_API PL/SQL interface that encapsulates all declarative and procedural validation logic applied before a person record is inserted or updated in the PER tables. In the 12.1.1 and 12.2.2 releases, the package body carries the header marker peperrhi.pkb and is owned by APPS, with an API classification of OTHER.

Its role is defensive: each CHK_* routine evaluates one attribute or combination of attributes and raises an application error when the incoming value violates a seeded HRMS rule. The package also exposes DF_UPDATE_VALIDATE, which compares the old and new values held in the PER_PER_SHD shadow record (attribute_category through attribute30) to determine whether descriptive-flexfield segments have actually changed.

Key Procedures and Functions

The documented package exposes eighteen procedures and functions. Representative members include:

• DF_UPDATE_VALIDATE — compares the shadow old record against the incoming record for attribute_category and attribute1–attribute30, detecting real DFF changes before update processing.
• CHK_UNSUPPORTED_ATTRIBUTES — rejects attempts to populate attributes not supported by the current business group configuration.
• CHK_CORRESPONDENCE_LANGUAGE — validates the correspondence language against FND_LANGUAGES.
• CHK_COORD_BEN_MED_CVG_DATES — checks consistency of coordinated benefits medical coverage dates.
• CHK_COORD_BEN_MED_DETAILS — validates coordinated benefits medical plan detail combinations.
• CHK_OTHER_COVERAGES — validates the "other coverages" benefits indicator.
• CHK_FTE_CAPACITY — enforces the full-time-equivalent capacity value for the assignment.
• CHK_BACKGROUND_CHECK_STATUS — validates the background check status value for the person record; this is the routine most commonly surfaced when users query the "chk_background_check_status" business rule in ETRM.
• CHK_BLOOD_TYPE — validates the blood type against the seeded lookup.
• CHK_STUDENT_STATUS — validates the student status value.
• CHK_WORK_SCHEDULE — validates the work schedule referenced by the person.
• CHK_REHIRE_RECOMMENDATION — validates the rehire recommendation indicator.
• CHK_BENEFIT_GROUP_ID — verifies the benefit group identifier exists in BEN_BENFTS_GRP.
• CHK_DATE_DEATH_AND_RCPT_CERT — cross-checks date of death against receipt of death certificate.
• CHK_BIRTH_ADOPTION_DATE — validates the birth or adoption date.
• CHK_RD_FLAG — validates the "receipt of death" flag.
• CHK_DATE_OF_DEATH — validates the date of death.
• CHK_USES_TOBACCO — validates the tobacco-use indicator used for benefits rating.

Tables Accessed

The package body references several tables through APPS synonyms. PER_ALL_PEOPLE_F is the primary source, supplying the person attributes (blood type, student status, tobacco use, date of death, background check status) that the CHK_* routines validate. BEN_BENFTS_GRP is queried by CHK_BENEFIT_GROUP_ID to confirm that the benefit group passed in exists and is valid for the business group. FND_LANGUAGES underpins CHK_CORRESPONDENCE_LANGUAGE, ensuring the language code supplied by the form or interface is an active, installed language. PER_CONTACT_RELATIONSHIPS is used where contact and relationship-derived attributes must be checked before the person is saved. The package does not write to these tables directly; it operates on records passed by the calling API and raises errors when validation fails.

Usage Notes

PER_PER_BUS1 is not normally called directly by end users. It is invoked by the PER_PER_API business API layer, which in turn is called by the People form (PERWSHRG), the Hire and Maintain Person flows, and by concurrent programs or custom PL/SQL that use the supported HRMS APIs. One other package references PER_PER_BUS1 according to the ETRM metadata, reflecting its position as a shared validation gateway for the person entity. Developers extending HR should route person validations through PER_PER_API rather than calling PER_PER_BUS1 procedures directly, because the bus package depends on the shadow record (PER_PER_SHD) being populated by the API wrapper. When a user searches ETRM for "chk_background_check_status", the result points to this package as the definitive location of the background check status validation rule in the 12.1.1 and 12.2.2 code lines.