Search Results create_my_person_address

Overview

The APPS.HR_PERSON_ADDRESS_API package body is a public PL/SQL API in Oracle E-Business Suite that provides the supported programmatic interface for creating and maintaining person addresses held within the HR foundation. Person addresses represent the physical, mailing, and location-based addresses associated with a person record in PER_ALL_PEOPLE_F, and they are the source of address data consumed across Oracle HRMS, Payroll, and downstream applications. Rather than allowing direct inserts and updates against the underlying address tables, Oracle EBS directs all address maintenance through this API so that address validation, date-tracked effective dating, descriptive flexfield handling, address style resolution, and legislative data group business rules are applied consistently.

The package body is documented with a status of VALID in the ETRM extract for both 12.1.1 and 12.2.2. It is classified as an API and is referenced at runtime by 28 other database objects, confirming its role as a foundational building block for person address maintenance rather than an application-specific utility.

Key Procedures and Functions

The documented API exposes 53 procedures and functions. The core entry point is CREATE_PERSON_ADDRESS, which accepts address attributes for a person and creates a new effective-dated address record. Around this core, the package provides a series of country-specific creation routines that apply the address style and legislative validation appropriate to each supported territory. Documented examples include CREATE_GB_PERSON_ADDRESS for the United Kingdom, CREATE_US_PERSON_ADDRESS for the United States, CREATE_AU_PERSON_ADDRESS and CREATE_AU_LOC_PERSON_ADDRESS for Australia, CREATE_AT_PERSON_ADDRESS, CREATE_BE_PERSON_ADDRESS, CREATE_DK_PERSON_ADDRESS, CREATE_DE_PERSON_ADDRESS, CREATE_IT_PERSON_ADDRESS, CREATE_MX_PERSON_ADDRESS and CREATE_MX_LOC_PERSON_ADDRESS, CREATE_MY_PERSON_ADDRESS, CREATE_PT_PERSON_ADDRESS, CREATE_FI_PERSON_ADDRESS, CREATE_GR_PERSON_ADDRESS, CREATE_HK_PERSON_ADDRESS, CREATE_IE_PERSON_ADDRESS, CREATE_LU_PERSON_ADDRESS, and CREATE_NL_PERSON_ADDRESS.

Each variant exists because address formats, validation rules, and required segments differ by country. Callers select the appropriate routine based on the person's address style or location, allowing the API to populate the address elements and descriptive flexfield structures expected for that territory. Parameter lists are not enumerated here; consumers should consult the package specification in the target instance for exact signatures.

Tables Accessed

The package body operates against PER_ADDRESSES, the base table that stores person address records, and PER_ALL_PEOPLE_F, the date-tracked person table used to associate and validate the address against a person. In the documented dependency graph, these are exposed to the package through APPS synonyms. The body also references supporting objects including PER_ADD_INS, PER_ADD_SHD, and PER_ADD_UPD, which are the insert, shadow, and update structures used by the address business logic during the create and date-track processing, along with HR_PERSON_ADDRESS_BK1, HR_PERSON_ADDRESS_BK2, and HR_PERSON_ADDRESS_BK3 for the underlying row-level operations. Utility routines in HR_API and HR_UTILITY supply validation, error stacking, and common HRMS API behaviour such as STANDARD for messaging.

Usage Notes

This API is invoked whenever person address data must be created or changed programmatically. In standard EBS usage it is called by the Person and Assignment forms and by address maintenance flows so that effective dating and validation are preserved. It is also the recommended interface for custom PL/SQL, interfaces, and conversions that load or update addresses, and it is referenced by 28 other packaged objects, indicating reuse across HRMS business logic and dependent APIs. Because the API enforces the same rules as the delivered forms, direct DML against PER_ADDRESSES should be avoided in favour of these routines. Consumers should invoke the country-specific variant matching the legislative context of the address and supply the required date-tracked person context to ensure the address is correctly associated with the target person record.