Search Results create_in_person_address

Overview

The APPS.HR_IN_PERSON_ADDRESS_API package body is a PL/SQL application programming interface supplied by Oracle E-Business Suite to manage person addresses for employees and other person records governed by the Indian (IN) legislation. Its principal purpose is to provide a controlled, validated entry point for creating and maintaining address data held against a person, thereby insulating callers from the underlying PER_ADDRESSES table and ensuring that mandatory business rules — including legislative eligibility of the person and the validity of the primary key passed by the caller — are enforced before any row is inserted or updated.

The package is part of the Oracle HRMS (Human Resources Management System) family of "IN" localization APIs, as evidenced by the naming convention and by the hard-coded validation of legislation code IN. It is classified in ETRM as an API, meaning it is intended for programmatic invocation rather than direct table manipulation. The package is referenced by two other database objects and exposes two documented procedures, CREATE_IN_PERSON_ADDRESS and UPDATE_IN_PERSON_ADDRESS, forming a paired interface for the full lifecycle of an address record.

Internally, the package body declares a package-level variable used for message and error handling, reflecting the standard Oracle HR error-reporting idiom based on HR_UTILITY. The source header indicates a last modification date of 25-May-2004, confirming its availability across the 12.1.1 and 12.2.2 release lines.

Key Procedures and Functions

• CREATE_IN_PERSON_ADDRESS — Inserts a new address record for a specified person into the underlying address table. Invocation validates the person and their legislative context before the insert is performed, so that only persons belonging to a business group whose legislation code is IN may receive an address of this type. The procedure is the documented entry point corresponding to the search term create_in_person_address.
• UPDATE_IN_PERSON_ADDRESS — Modifies an existing person address record previously created by the package, subject to the same legislative and person validation. It preserves the audit and effective-dating conventions expected of HRMS datetracked entities.

The package body additionally implements a private helper, check_person, which is not a documented API procedure but performs the pre-condition checks used by the two public procedures. It queries the person record to determine the associated legislation code using an effective-date join against PER_PEOPLE_F and PER_BUSINESS_GROUPS. If the person cannot be found for the supplied effective date, it sets message HR_7220_INVALID_PRIMARY_KEY and raises an error. If the person's legislation code does not match the supplied legislation code, it sets message HR_7961_PER_BUS_GRP_INVALID with the token LEG_CODE set to IN and raises an error. These validations guarantee that address creation for Indian legislation is never applied to a person outside that legislative context.

Tables Accessed

• PER_ADDRESSES — the principal table read and written by the package. It stores the person address rows that the CREATE and UPDATE procedures insert and modify. Address attributes, effective dates, and the association to the person are held here.
• PER_PEOPLE_F — accessed indirectly by the check_person helper to resolve the business group of the person and to honour effective dating. This ensures validation is performed against the person as of the requested effective date rather than against the current record unconditionally.
• PER_BUSINESS_GROUPS — accessed indirectly to translate the person's business group into a legislation code, which is then compared with the required IN legislation.

All table access is performed through APPS synonyms, consistent with the documented ETRM metadata that lists only PER_ADDRESSES as the referenced base table for the public interface.

Usage Notes

The package is typically invoked from Oracle Forms-based HRMS address maintenance screens, from concurrent programs that load or migrate person address data, and from custom PL/SQL or integration code that must create or amend Indian person addresses without bypassing HRMS validation. Because the procedures rely on HR_UTILITY to set messages and raise errors, callers should wrap invocation in an exception handler that presents the resulting message to the user or logs it appropriately; unhandled errors will surface with the standard 801 application message identifiers HR_7220_INVALID_PRIMARY_KEY or HR_7961_PER_BUS_GRP_INVALID. Callers must supply a valid person identifier, a matching legislation code, and an effective date for which the person record exists, and should respect the datetracked effective-dating conventions of the HRMS schema. Direct DML against PER_ADDRESSES is strongly discouraged in favour of this API, since the package encapsulates the required legislative and primary-key validations.