Search Results in_pin_codes
Overview
The APPS.HR_IN_PERSON_ADDRESS_API package is a public Oracle E-Business Suite PL/SQL API that provides programmatic maintenance of person address records for India-specific Human Resources implementations. Its display name in the ETRM repository, "Person Address for India," reflects its role as the India localization counterpart to the global HR_PERSON_ADDRESS_API. The package encapsulates the business rules governing address creation and maintenance, including validation of the person, effective dating through DateTrack, and enforcement of the single-primary-address constraint. It is classified as an API within the PER product and is licensed for use with Oracle Human Resources. The API is designed to be called by forms, concurrent processes, and custom extensions that must insert or amend address data without directly manipulating the underlying tables, thereby preserving data integrity and DateTrack semantics.
Key Procedures and Functions
The package exposes two documented procedures:
- CREATE_IN_PERSON_ADDRESS — Creates a new address for a person. It functions as an alternative to the generic
CREATE_PERSON_ADDRESSAPI. Validation is controlled by thep_validateflag: when true, only validation is performed and the database remains unchanged; when false and all checks pass, the address row is inserted. Thep_effective_dateparameter determines when the DateTrack operation takes effect. A valid person identified byp_person_idmust exist on the address start datep_date_from. When the address being created is the first for the person, it must be the primary address; because only one primary address may exist at any time, any subsequent address must not be primary. Thep_pradd_ovlapval_overrideparameter supplies a primary address override flag to govern overlap validation. TheADDRESS_TYPEattribute may only be populated once QuickCodes have been defined for the corresponding lookup type. - UPDATE_IN_PERSON_ADDRESS — Amends an existing person address, applying the same DateTrack and validation conventions as the create procedure.
Tables Accessed
The package reads and writes PER_ADDRESSES (accessed through the APPS synonym), the core datetracked table that stores person address records. All inserts and updates performed by the API are applied to this table. The API additionally depends on lookup definitions for the ADDRESS_TYPE lookup type, which must exist before the address type attribute can be used.
Usage Notes
This package is typically invoked from the Person Address maintenance forms within Oracle HRMS, from concurrent programs that load or migrate address data, and from custom PL/SQL integrations. Two other packages reference it, confirming its role as a shared building block. Callers must supply a person that is valid on the address start date and should pass p_validate as true during preliminary checks before committing changes. Because the API is India-specific, it should be selected in preference to the generic person address API when processing Indian address structures. On failure, no address is created or modified and an error is raised, so callers should include exception handling consistent with standard EBS API error conventions.
-
Lookup Type: IN_PIN_CODES
12.1.1
product: PER - Human Resources , meaning: IN_PIN_CODES , description: Pin Code And State Relationship ,
-
Lookup Type: IN_PIN_CODES
12.2.2
product: PER - Human Resources , meaning: IN_PIN_CODES , description: Pin Code And State Relationship ,
-
APPS.PER_IN_ADD_LEG_HOOK SQL Statements
12.2.2
-
APPS.PER_IN_ADD_LEG_HOOK SQL Statements
12.1.1
-
PACKAGE: APPS.HR_IN_PERSON_ADDRESS_API
12.2.2
-
PACKAGE: APPS.HR_IN_PERSON_ADDRESS_API
12.1.1
-
PACKAGE: APPS.HR_IN_LOCATION_API
12.2.2
-
PACKAGE: APPS.HR_IN_LOCATION_API
12.1.1
-
PACKAGE BODY: APPS.PER_IN_ADD_LEG_HOOK
12.1.1
-
PACKAGE BODY: APPS.PER_IN_ADD_LEG_HOOK
12.2.2
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 FND Design Data
12.2.2
-
APPS.PER_IN_ADD_LEG_HOOK dependencies on HR_LOOKUPS
12.2.2
-
APPS.PER_IN_ADD_LEG_HOOK dependencies on HR_LOOKUPS
12.1.1