Search Results create_person_address
Overview
HR_PERSON_ADDRESS_SWI is a server-side wrapper interface (SWI) package body owned by the APPS schema in Oracle E-Business Suite. Its primary business function is to provide a stable, publicly callable API for creating and maintaining person addresses within the Oracle HRMS (Human Resources Management System) data model. Person addresses represent the physical and mailing locations associated with a person record, and they are used across multiple EBS modules, including HR, Payroll, Benefits, and self-service applications.
The package is classified as OTHER within the ETRM metadata, indicating that it is not a standalone business API but rather a thin wrapper that delegates the substantive processing to the underlying HR address business logic. The header comment hraddswi.pkb 120.1 confirms that this is a versioned, shipped Oracle file at the 12.0/12.1 code level, consistent with the 12.1.1 and 12.2.2 releases referenced.
Key Procedures and Functions
The package exposes two documented procedures:
- CREATE_PERSON_ADDRESS — the procedure most commonly invoked by users searching for "create_person_address." It accepts a comprehensive parameter set covering the person identifier, primary flag, address style, effective date range, address type, comments, and the full address detail fields (address lines 1–3, town or city, regions 1–3, postal code, country, telephone numbers 1–3, and descriptive flexfield attribute columns). Validation and overlap-override parameters are also exposed. The procedure creates a new dated address record for the specified person, honoring effective dating and multi-address-type rules.
- UPDATE_PERSON_ADDRESS — the companion procedure used to modify an existing person address record, applying the same effective-dating and validation model as the create path.
Both procedures follow standard Oracle HRMS API conventions, including a p_validate parameter that permits the caller to run the business logic in validation-only mode without committing data.
Tables Accessed
Because the SWI delegates to the underlying HR address business logic, the physical DML is performed against the base HR address tables — principally PER_ADDRESSES, which stores the dated address rows, and its associated child/descriptive flexfield structures. The package itself exposes APPS synonyms rather than direct table references, which is the standard pattern for Oracle HRMS SWI packages and preserves the abstraction boundary between the public API and the internal data model.
Usage Notes
HR_PERSON_ADDRESS_SWI is typically invoked from:
- Oracle Forms (the Person and Assignment windows and the Addresses block) where address entry is captured during hire or maintenance.
- Self-service and iRecruitment flows that create or amend person addresses programmatically.
- Concurrent programs and interfaces that bulk-load person address data from external systems.
- Custom PL/SQL code seeking a supported, upgrade-safe entry point rather than writing directly to HR address tables.
The metadata notes that the package is referenced by two other packages, confirming its role as a shared utility layer within the HRMS API stack. Callers should supply an p_effective_date to ensure correct date-tracked behavior and should use p_validate = hr_api.g_true_num during testing to avoid premature commits.
-
PACKAGE BODY: APPS.HR_PERSON_ADDRESS_SWI
12.2.2
-
PACKAGE: APPS.HR_PERSON_ADDRESS_SWI
12.1.1
-
PACKAGE: APPS.HR_PERSON_ADDRESS_SWI
12.2.2
-
PACKAGE BODY: APPS.HR_PERSON_ADDRESS_SWI
12.1.1
-
PACKAGE BODY: APPS.HR_KIOSK_ADDRESS_API
12.2.2
-
PACKAGE BODY: APPS.HR_KIOSK_ADDRESS_API
12.1.1
-
PACKAGE BODY: APPS.HR_PERSON_ADDRESS_BK1
12.1.1
-
PACKAGE BODY: APPS.HR_PERSON_ADDRESS_BK1
12.2.2
-
PACKAGE: APPS.PER_CA_PERSON_ADDRESS_API
12.1.1
-
PACKAGE: APPS.PER_CA_PERSON_ADDRESS_API
12.2.2
-
PACKAGE: APPS.HR_PERSON_ADDRESS_API
12.1.1
-
PACKAGE: APPS.HR_PERSON_ADDRESS_API
12.2.2
-
PACKAGE: APPS.HR_KIOSK_ADDRESS_API
12.1.1
-
PACKAGE: APPS.HR_KIOSK_ADDRESS_API
12.2.2
-
PACKAGE: APPS.HR_FR_PERSON_ADDRESS_API
12.1.1
-
PACKAGE: APPS.HR_FR_PERSON_ADDRESS_API
12.2.2
-
PACKAGE: APPS.HR_CN_PERSON_ADDRESS_API
12.1.1
-
PACKAGE: APPS.HR_PROCESS_ADDRESS_SS
12.2.2
-
PACKAGE: APPS.HR_CN_PERSON_ADDRESS_API
12.2.2
-
PACKAGE: APPS.HR_PROCESS_ADDRESS_SS
12.1.1
-
PACKAGE: APPS.PER_ZA_USER_HOOK_PKG
12.2.2
-
PACKAGE: APPS.HR_AE_PERSON_ADDRESS_API
12.2.2
-
PACKAGE: APPS.HR_AE_PERSON_ADDRESS_API
12.1.1
-
PACKAGE: APPS.HR_HK_PERSON_ADDRESS_API
12.2.2
-
PACKAGE: APPS.HR_HK_PERSON_ADDRESS_API
12.1.1
-
PACKAGE: APPS.HR_PL_PERSON_ADDRESS_API
12.1.1
-
PACKAGE: APPS.HR_IN_PERSON_ADDRESS_API
12.2.2
-
PACKAGE: APPS.HR_PL_PERSON_ADDRESS_API
12.2.2
-
PACKAGE: APPS.HR_IN_PERSON_ADDRESS_API
12.1.1
-
PACKAGE: APPS.HR_NZ_PERSON_ADDRESS_API
12.1.1
-
PACKAGE: APPS.HR_NZ_PERSON_ADDRESS_API
12.2.2
-
PACKAGE BODY: APPS.HR_PERSON_ADDRESS_API
12.2.2
-
PACKAGE BODY: APPS.HR_PERSON_ADDRESS_API
12.1.1
-
APPS.HR_PERSON_ADDRESS_BK1 dependencies on HR_API
12.1.1
-
APPS.HR_PERSON_ADDRESS_BK1 dependencies on HR_API
12.2.2
-
APPS.HR_PERSON_ADDRESS_BK1 dependencies on HR_PERSON_ADDRESS_BK1
12.2.2
-
APPS.HR_PERSON_ADDRESS_BK1 dependencies on HR_PERSON_ADDRESS_BK1
12.1.1
-
APPS.HR_PERSON_ADDRESS_BK1 dependencies on HR_UTILITY
12.2.2
-
APPS.HR_PERSON_ADDRESS_BK1 dependencies on HR_UTILITY
12.1.1
-
PACKAGE BODY: APPS.HR_PROCESS_ADDRESS_SS
12.2.2
-
PACKAGE BODY: APPS.HR_PROCESS_ADDRESS_SS
12.1.1
-
APPS.HR_PERSON_ADDRESS_BK1 dependencies on HR_MULTI_MESSAGE
12.2.2
-
APPS.HR_PERSON_ADDRESS_BK1 dependencies on HR_MULTI_MESSAGE
12.1.1
-
APPS.HR_KIOSK_ADDRESS_API dependencies on PER_PEOPLE_F
12.1.1
-
APPS.HR_KIOSK_ADDRESS_API dependencies on PER_ADDRESSES
12.1.1
-
APPS.HR_JPBP_API dependencies on HR_APPLICANT_API
12.1.1
-
APPS.HR_JPBP_API dependencies on HR_APPLICANT_API
12.2.2
-
APPS.HR_KIOSK_ADDRESS_API dependencies on PER_ADDRESSES
12.2.2
-
APPS.HR_KIOSK_ADDRESS_API dependencies on PER_PEOPLE_F
12.2.2
-
APPS.HR_PERSON_ADDRESS_API dependencies on HR_PERSON_ADDRESS_BK1
12.1.1