Search Results get_max_effective_date




Overview
Explore in AI Chat

Overview

APPS.HR_PROCESS_PERSON_SS is a server-side PL/SQL package body in Oracle E-Business Suite 12.1.1 and 12.2.2 that encapsulates the business logic for creating and maintaining person records within Oracle HRMS. The package operates against the PER_ALL_PEOPLE_F entity and its associated date-tracked structures, providing a controlled, API-like layer over the underlying person tables. Its name suffix (SS) indicates a server-side helper package, and the header comment (hrperwrs.pkb, version 120.11.12010000.10) confirms that it forms part of the HR person processing subsystem.

The package supports both employee and applicant processing, as evidenced by the presence of PROCESS_API, PROCESS_DUMMY_API, CREATE_PERSON, PROCESS_APPLICANT, and UPDATE_PERSON. It is registered in ETRM with an API classification of OTHER and is referenced by seventeen other packages, indicating that it is a widely relied-upon component of the HRMS data model rather than an isolated utility.

Key Procedures and Functions

The package exposes eleven documented procedures and functions:

  • GET_MAX_EFFECTIVE_DATE — Returns the maximum effective date applicable to a person record, allowing callers to identify the most recent date-tracked row before performing an insert or update.
  • GET_PERSON_DATA_FROM_TT — Retrieves person data from a PL/SQL table (table type), typically populated by a calling form or concurrent program.
  • GET_HR_LOOKUP_MEANING — Resolves an HR lookup code to its displayed meaning, supporting validation and descriptive display.
  • UPDATE_PERSON — Applies changes to an existing person record.
  • VALIDATE_BASIC_DETAILS — Performs mandatory-field and business-rule validation on core person attributes, raising the package's validation exceptions on failure.
  • IS_REC_CHANGED — Determines whether a record has been modified since it was last read, avoiding unnecessary DML.
  • PROCESS_API — Main entry point that orchestrates person processing through the HRMS API layer.
  • PROCESS_DUMMY_API — A mode that simulates processing without committing changes, used for validation-only scenarios.
  • CREATE_PERSON — Inserts a new person record in PER_ALL_PEOPLE_F.
  • PROCESS_APPLICANT — Handles applicant-specific processing, including conversion of an applicant to an employee.

Tables Accessed

The package reads and writes PER_ALL_PEOPLE_F, PER_ADDRESSES, PER_ALL_ASSIGNMENTS_F, and PER_ASSIGNMENT_STATUS_TYPES as its core person and assignment structures. HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS, and HR_API_TRANSACTION_VALUES capture the API transaction audit trail. HR_COMMENTS, HR_ORGANIZATION_INFORMATION, and HR_ALL_ORGANIZATION_UNITS_TL support comments and organizational context, while FND_DESCR_FLEX_CONTEXTS handles descriptive flexfield context resolution. FND_USER and FND_DOCUMENT_CATEGORIES support user and document categorization lookups, IRC_DOCUMENTS links recruitment records, and PAY_LEGISLATION_RULES applies payroll legislation during validation.

Usage Notes

HR_PROCESS_PERSON_SS is typically invoked from the People form, applicant windows, and hire/applicant concurrent programs rather than being called directly by end users. Because it is referenced by seventeen other packages, changes to its public signatures carry broad impact across HRMS. Custom code should call the documented procedures in sequence, using GET_MAX_EFFECTIVE_DATE and IS_REC_CHANGED before writes, and should respect the package's exception flags, including g_data_error and g_date_prior_to_cur_start_date, which signal date-track violations and validation failures.