Search Results create_us_int_person_address

Overview

The APPS.GHR_PERSON_ADDRESS_API package body is a public Oracle E-Business Suite API responsible for the creation and maintenance of person address records within the Human Resources (HR) datamodel. In Oracle EBS 12.1.1 and 12.2.2, person addresses are stored against the PER_ADDRESSES table and are validated against reference data such as address styles, country codes, and state or province lists. This package encapsulates that validation and DML logic behind a stable procedural interface, allowing developers and integrators to insert or update address rows without writing direct SQL against the base table.

The package exposes a United States-specific interface that understands the structure of a US address style — address lines, city, state, ZIP code, county, and country — along with a generalized international interface for addresses that do not conform to the US format. The header comment identifies the source file as ghaddapi.pkb, version 120.1, indicating both an 11i-era origin and forward compatibility with Release 12. The API is classified as an API in the ETRM repository, meaning it is documented and intended for customer and partner use rather than internal-only consumption.

Key Procedures and Functions

• CREATE_US_PERSON_ADDRESS — Creates a new person address record using the United States address format. It accepts a person identifier, an effective date for the operation, the primary flag, a date range (from and to dates), address type, comments, structured US address components (address lines, city, state, ZIP code, county, country), telephone numbers, and the address attribute category with its flexfield segments. The procedure supports a validation-only mode through the p_validate parameter, allowing callers to test input without committing data.
• CREATE_US_INT_PERSON_ADDRESS — Creates an international address for a person. The international variant accommodates address formats that fall outside the US style, such as the textual "address line" representation used by many non-US countries, while still applying the package's standard validation and date-tracking rules.
• UPDATE_US_PERSON_ADDRESS — Updates an existing United States-format address for a person. It applies the same validation logic as the create procedure but operates against an address already present in PER_ADDRESSES, preserving the effective-dating and primary-flag semantics required by the HR datamodel.
• UPDATE_US_INT_PERSON_ADDRESS — Updates an existing international address record, applying the international address style and the package's standard update behavior.

Tables Accessed

The documented table accessed by this package is PER_ADDRESSES, reached through an APPS synonym. This is the base table that stores all person address rows in Oracle HRMS, including effective dates, primary flags, address style linkage, and the flexfield attribute columns surfaced as p_addr_attribute1 through p_addr_attribute15 in the API signature. All create and update procedures ultimately write to this single table; the API performs the necessary lookups and validation against related reference entities before performing the DML. No other packages are documented as callers of this API, and it is not documented as referencing additional tables directly.

Usage Notes

This package is typically invoked from PL/SQL triggers and customizations attached to HR forms, from concurrent programs that load or migrate person data, and from external integration code that needs to insert addresses into HRMS without bypassing validation. Because the create and update procedures perform the same checks the application applies interactively, calling the API is strongly preferred over direct inserts into PER_ADDRESSES; direct DML risks inconsistent dates, missing style validation, and orphaned primary addresses.

The p_validate parameter should be exercised during development to confirm that inputs pass validation before committing. Callers must supply a valid p_effective_date in every invocation, since effective dating governs which address row is considered current. A search for "create_us_person_address" will most commonly surface this package when developers are building a US-format address creation routine for a person record.