Search Results per_people11_pkg




Overview
Explore in AI Chat

Overview

PER_PEOPLE11_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It belongs to the Oracle Human Resources (PER) product family and is best understood as a low-level Data Manipulation Language (DML) utility package rather than a public, business-facing API. Whereas the flagship HR interfaces such as HR_PERSON_API and HR_EMPLOYEE_API encapsulate full business validation, date-tracked logic, and workflow integration, PER_PEOPLE11_PKG provides a narrow, bare-metal layer for inserting and deleting rows directly against the person tables. The "11" suffix indicates it is one of a series of internal, screen-specific helper packages historically generated to support Oracle Forms in the People module. In the context of Oracle EBS 12.1.1 and 12.2.2 it is classified under API classification OTHER, meaning it is not a supported public API and is intended strictly for internal application consumption.

Its role is therefore transactional plumbing: it exists so that Forms and other internal components can persist person-level records without re-invoking the heavier validation stack. Because it bypasses many business rules, it is considered an internal object and is not recommended for direct use by customer extensions.

Key Procedures and Functions

The package exposes two documented procedures:

  • INSERT_ROW1 — Performs a direct insert of a row into the person data model. Its purpose is to create the underlying person record at the physical table level. As a row-level DML helper, it is expected to be invoked after surrounding application logic has already prepared the column values and derived keys.
  • DELETE_ROW1 — Performs a direct delete of an existing person row. Its purpose is to remove the targeted record at the physical table level, mirroring the insert helper.

Both procedures are named with the "1" suffix, which is characteristic of Oracle Forms generated or auto-created DML units. No validated parameter lists are published in the ETRM metadata; the documented evidence confirms only the procedure names and their DML-oriented intent. Engineers should not assume a public, stable signature, since internal procedures of this type frequently rely on package-level globals or Forms item bindings.

Tables Accessed

The package references two documented base tables through APPS synonyms:

  • PER_ALL_PEOPLE_F — The core, date-tracked (effective-dated) person table holding all person records across employee, applicant, and contact capacities. The INSERT_ROW1 and DELETE_ROW1 operations target this table to create and remove person rows.
  • PER_PEOPLE_S — A supporting sub-entity table associated with person records. It is likely populated or cleared in coordination with the PER_ALL_PEOPLE_F operations.

Because PER_ALL_PEOPLE_F is date-tracked, direct manipulation through this package carries the same effective-dating risks as any raw table operation.

Usage Notes

PER_PEOPLE11_PKG has no documented inbound references from other packages. The ETRM dependency data shows it referencing only SYS.STANDARD and being referenced by itself, which confirms it is a leaf-level, internal utility with no downstream package consumers. It is therefore almost certainly invoked from Oracle Forms (the People form) or from tightly coupled internal code rather than from concurrent programs or published integration points.

For extension work on 12.1.1 or 12.2.2, this package should be regarded as internal and unsupported. Customizations that require person creation or deletion should use HR_PERSON_API or the appropriate HR business APIs, which enforce validation, date tracking, key generation, and audit behavior this helper does not. Direct calls to INSERT_ROW1 or DELETE_ROW1 risk inconsistent person data and are discouraged.