Search Results p_first_name

Overview

APPS.HR_CONTACT_BK1 is a PL/SQL package body belonging to the Oracle HRMS (Human Resources Management System) schema within Oracle E-Business Suite release 12.1.1 and 12.2.2. The package is generated by the Oracle HRMS API Hook Pre-processor, as indicated by the header comment in the source. Packages with the _BK1 suffix in the HRMS data model are historically the "before" or "pre-process" hook packages associated with a corresponding user hook or business rule layer, enabling customers and implementers to inject custom logic that executes prior to the main business logic of the corresponding contact or person API.

Functionally, HR_CONTACT_BK1 exposes wrapper entry points around person and contact creation logic, most notably the creation of a person record within a business group. It is classified as an OTHER API object within the ETRM documentation for 12.2.2. The parameter signature of the CREATE_PERSON_A procedure includes P_FIRST_NAME, which is the search term of interest, along with other person-attribute parameters such as P_LAST_NAME, P_MIDDLE_NAMES, P_SEX, P_DATE_OF_BIRTH, and a wide array of descriptive flexfield attribute columns (P_ATTRIBUTE1 through P_ATTRIBUTE30).

Key Procedures and Functions

• CREATE_PERSON_A — The primary documented procedure in this package body. It accepts a broad set of person-creation parameters, including P_FIRST_NAME, P_LAST_NAME, P_MIDDLE_NAMES, P_KNOWN_AS, P_START_DATE, P_BUSINESS_GROUP_ID, and the Attribute1 through Attribute30 descriptive flexfield columns. It also accommodates PER_INFORMATION_CATEGORY and the related PER_INFORMATIONn descriptive flexfield values. The procedure represents the main entry point for pre-processing hooks during person creation.
• CREATE_PERSON_B — A second documented procedure, named with the "_B" convention that in Oracle HRMS hook packages typically designates the "before" or alternate pre-processing variant of the same operation. It mirrors the CREATE_PERSON_A purpose of handling person creation input prior to the core API execution.

Per the documented metadata, the package body contains two procedures in total. Parameter lists are not invented here; the naming convention and the exposed P_FIRST_NAME parameter confirm that person name attributes are central to the procedure contract.

Tables Accessed

The ETRM metadata for this package does not list any explicitly referenced tables accessed via APPS synonyms. The absence of documented table references is consistent with the nature of a generated hook package, which is designed to intercept parameters and route them to the underlying HRMS person API rather than to manipulate base tables directly. The actual INSERT and UPDATE operations against the PER_ALL_PEOPLE_F and related HR tables are performed by the main API (for example, HR_PERSON_API or HR_EMPLOYEE_API) that this hook package precedes.

Usage Notes

HR_CONTACT_BK1 is typically invoked indirectly by the Oracle HRMS person and contact APIs rather than being called directly by end users. It is referenced by one other package according to the documented metadata, which reflects the layered API architecture in which the main contact or person API calls the pre-process hook package. Custom logic placed in this package executes before the standard person creation logic, making it appropriate for validation, defaulting, or derivation of P_FIRST_NAME and related name attributes. Because the package is generated and carries the "$Header" identifier referencing peconapi.pkb, it should be treated carefully during upgrades; customizations are generally preserved through the supported hook mechanism rather than by editing the generated body directly. In the context of Oracle EBS 12.1.1 and 12.2.2, this package supports contact and person creation workflows, including those initiated from forms, concurrent programs, and custom integrations that rely on the HRMS person API.