Search Results populate_new_person

Overview

APPS.PER_PEOPLE11_PKG is a low-level PL/SQL package body within the Oracle E-Business Suite Human Resources (PER) schema. Its role is to provide the physical row-level Data Manipulation Language (DML) operations for the PER_ALL_PEOPLE_F and PER_PEOPLE_S entities. The "11" suffix in the package name indicates that it is a versioned or partitioned variant of the core People package family, typically generated to handle tablespace or size constraints on large installations, or to support the row-based insert and delete logic that the higher-level PER_PEOPLE_API relies upon.

The package is classified as OTHER in the ETRM metadata, meaning it is not a public, supported business API intended for direct customer invocation. Rather, it is an internal implementation package. The user search term "populate_new_person" reflects the common pattern of inserting a new person record through the People API layer, which ultimately routes through this package to perform the actual row insertion into the base tables.

Key Procedures and Functions

The package exposes two documented procedures:

• INSERT_ROW1 — Performs the physical insert of a single row into the person table structure. It accepts a very wide parameter list covering all person attributes, including person_id and the rowid, effective dating columns (effective_start_date, effective_end_date), business group and person type identifiers, name components (last_name, first_name, middle_names, full_name, known_as, suffix, title), biographical and employment attributes (date_of_birth, sex, marital_status, nationality, national_identifier, employee_number, applicant_number), flags such as current_employee_flag and registered_disabled_flag, plus the standard WHO audit columns and request_id, program_application_id, program_id, and program_update_date for concurrent manager tracking.
• DELETE_ROW1 — Performs the physical deletion of a person row, typically used by purge or correction processes that operate on the row level rather than through the date-tracked logical delete of the API layer.

Tables Accessed

The package reads from and writes to two documented tables via APPS synonyms:

• PER_ALL_PEOPLE_F — The primary dated (F = "future/dated") person table holding all person records with effective date ranges. INSERT_ROW1 populates this table, and DELETE_ROW1 removes rows from it.
• PER_PEOPLE_S — The "S" table stores the non-dated or setup/static attributes for a person record. It is maintained in parallel with PER_ALL_PEOPLE_F to hold columns that are not date-tracked.

No other tables are directly referenced by the documented procedures; associated child records (assignments, contacts, etc.) are handled by other packages in the API stack.

Usage Notes

This package is not intended for direct invocation by end users, forms, or custom code. It is called internally by the supported PER_PEOPLE_API (and its dependent packages) when a new person is created, which is the conventional path implied by the "populate_new_person" search. Typical calling contexts include the Enter Person form in Oracle HRMS, the Employee Hire and Applicant Entry flows, and concurrent programs that bulk-import person data through the API.

Because INSERT_ROW1 and DELETE_ROW1 bypass the full business validation, date-track propagation, and security checks performed by the public API, direct calls to PER_PEOPLE11_PKG are unsupported and can produce orphaned or inconsistent person records. Customizations that need to create or remove persons should always use PER_PEOPLE_API rather than this package. In Oracle EBS 12.1.1 and 12.2.2, the package header text (peper11t.pkb) and its versioned name confirm it remains an internal, release-maintained artifact across both 11i and R12 code lines.