Search Results hr_process_person_ss




Overview
Explore in AI Chat

Overview

HR_PROCESS_PERSON_SS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It forms part of the Self-Service Human Resources (SSHR) processing layer and is responsible for orchestrating the creation and update of person records through the HR_API infrastructure. The package acts as a server-side façade that accepts person data collected from SSHR web pages, validates that data, and then delegates the actual write operations to the standard HR person API. It is classified under the generic API classification of OTHER, reflecting its role as an internal integration construct rather than a published open interface.

The package is tightly coupled with the HR_API package, from which it draws core person maintenance logic, and with SYS.STANDARD for baseline PL/SQL constructs. It is referenced by seventeen other packages, confirming its position as a shared dependency within the HR, Benefits, and Payroll self-service stacks.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions within the package. Their purposes are as follows:

  • GET_HR_LOOKUP_MEANING — Retrieves the meaning of a value from an HR lookup type, supporting validation and display of code values during person processing.
  • GET_MAX_EFFECTIVE_DATE — Derives the maximum effective date applicable to a person record, used to establish correct date-tracked boundaries.
  • GET_PERSON_DATA_FROM_TT — Extracts person data from a PL/SQL table type populated by the calling SSHR process.
  • UPDATE_PERSON — Executes the update of an existing person record using data supplied by the transaction.
  • VALIDATE_BASIC_DETAILS — Performs elementary validation on the supplied person attributes before any API call is made.
  • IS_REC_CHANGED — Determines whether the incoming record differs from the stored record, allowing unnecessary API calls to be skipped.
  • PROCESS_API — Invokes the underlying HR person API and manages the outcome of that invocation.
  • PROCESS_DUMMY_API — Provides a no-write path used to simulate processing without committing changes.
  • CREATE_PERSON — Creates a new person record from validated SSHR input.
  • PROCESS_APPLICANT — Handles the person processing variant applicable to applicants recruited through iRecruitment.

Tables Accessed

The package reads and writes through APPS synonyms across several HR and related schemas. Person and assignment data is manipulated in PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F, with assignment status driven by PER_ASSIGNMENT_STATUS_TYPES. Address information is stored in PER_ADDRESSES. Descriptive flexfield context handling relies on FND_DESCR_FLEX_CONTEXTS, while organization details are read from HR_ALL_ORGANIZATION_UNITS_TL and HR_ORGANIZATION_INFORMATION.

Transaction auditing and API control use HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS, and HR_API_TRANSACTION_VALUES. Comments are captured in HR_COMMENTS. Applicant and recruitment document handling references IRC_DOCUMENTS and FND_DOCUMENT_CATEGORIES. User context is resolved through FND_USER, and legislative validation draws on PAY_LEGISLATION_RULES.

Usage Notes

HR_PROCESS_PERSON_SS is not a documented public API and should not be called directly by custom code without risk assessment. It is invoked principally from SSHR flows and related self-service packages, including HR_PROCESS_ADDRESS_SS, HR_PROCESS_ASSIGNMENT_SS, HR_PROCESS_EIT_SS, HR_TRANSACTION_SS, HR_NEW_USER_REG_SS, and HR_SUPERVISOR_SS. Benefits and Payroll components such as BEN_CREATE_PTNL_LER_SS, BEN_PROCESS_COBRA_PERSON_SS, and PER_SSHR_CHANGE_PAY also depend upon it. Because of its dependency on HR_API and its position beneath the SSHR UI layer, any extension or diagnostic work should account for the date-tracked tables it touches and the fact that it participates in API transaction logging.