Search Results pe_pei_bus




Overview
Explore in AI Chat

Overview

PE_PEI_BUS is a validated PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its name follows the Oracle HRMS naming convention for business-layer packages: "PE" identifies the People/Enterprise module, "PEI" denotes Person Extra Information, and the "_BUS" suffix indicates that the package encapsulates business rules rather than performing direct table access. In practice, PE_PEI_BUS provides the central validation and control logic for Person Extra Information records stored against the PER_PEOPLE_EXTRA_INFO table. This table holds flexible, attribute-style data attached to a person record — for example, legislative, statutory, or descriptive values that are not part of the core PER_ALL_PEOPLE_F structure but are still subject to HRMS validation rules.

The package therefore sits between the user interface or calling program and the underlying DML. It does not exist to insert, update, or delete rows on its own behalf; instead it determines whether a proposed change is legal before the associated insert, update, or delete handler performs the physical operation. In the ETRM registry it is classified as API classification OTHER, meaning it is not a public, supported business API in the same sense as an eponymous _API package, but it is an internal component that must be understood when tracing how Person Extra Information is maintained.

Key Procedures and Functions

Seven documented program units make up the interface of PE_PEI_BUS. All names and purposes below are drawn from the ETRM 12.2.2 metadata.

  • INSERT_VALIDATE — Validates a proposed new Person Extra Information row before insertion, enforcing the business rules that apply when a record is created.
  • UPDATE_VALIDATE — Validates a proposed modification to an existing row, applying the restrictions that govern which attributes may change.
  • DELETE_VALIDATE — Determines whether an existing Person Extra Information row may be removed, protecting records that must be retained.
  • RETURN_LEGISLATION_CODE — Returns the legislation code in effect for the record, which drives the legislative-specific rules applied by the validation routines.
  • CHK_NON_UPDATEABLE_ARGS — Confirms that arguments which must not change after creation have not been altered during an update.
  • CHK_PERSON_ID — Verifies that the person identifier supplied is valid and refers to an appropriate person record.
  • CHK_INFORMATION_TYPE — Validates the information type associated with the extra information record, ensuring it is a legitimate, permitted type.

The two validation packages PE_PEI_INS and PE_PEI_UPD, together with PE_PEI_DEL, are the primary internal callers, invoking the corresponding _VALIDATE routine before performing DML.

Tables Accessed

The dependency listing shows that PE_PEI_BUS references the APPS synonym for PER_PEOPLE_EXTRA_INFO, the table that stores the extra information rows themselves, and PE_PEI_SHD, the shadow/audit table used by the associated date-tracked or history-enabled maintenance logic. The ETRM 12.2.2 metadata further records access to PER_ALL_PEOPLE_F, the core person record, and PER_PEOPLE_INFO_TYPES, the setup table that defines the permitted information types. PER_ALL_PEOPLE_F is consulted to confirm person identity and legislative context, while PER_PEOPLE_INFO_TYPES supplies the valid values against which CHK_INFORMATION_TYPE tests a proposed type.

Usage Notes

PE_PEI_BUS is not intended for direct invocation by end users or custom extensions. It is an internal validation layer invoked by the Person Extra Information maintenance packages — PE_PEI_INS, PE_PEI_UPD, PE_PEI_DEL — which are themselves called from the Oracle HRMS person maintenance forms and from any concurrent or batch process that maintains person extra information. It is also referenced by HR_PERSON_EXTRA_INFO_BK2 and BK3, which are backward-compatibility or upgrade stub packages, confirming its role in the upgrade path for older customizations. Developers extending Person Extra Information should call the supported DML entry points rather than PE_PEI_BUS directly, and should treat the package as subject to change across patch levels. Its behaviour is heavily influenced by the legislation code returned by RETURN_LEGISLATION_CODE, so any code that manipulates person extra information must respect the same legislative restrictions the package enforces.