Search Results check_per_address_upd

Overview

APPS.PER_IN_ADD_LEG_HOOK is an Oracle E-Business Suite database package that implements country-specific address validation logic for India ("IN") within the Oracle Human Resources (PER) module. Its name reflects its role: it is a legislative "hook" package (ADD_LEG for address legislative) that the core HR address validation framework invokes to enforce local statutory rules on address data. The package is declared with AUTHID CURRENT_USER and carries a dated header comment (peinlhad.pkh 120.1, 2006/05/08), consistent with an Oracle-shipped, seeded object rather than a customer extension. Its principal business purpose is to validate and cross-check Indian address information, notably the relationship between state information and PIN (postal) codes, at the point of insert or update of personal and location addresses. The package defines a record type r_pin_code (state_code and pin_code) and an associated PL/SQL table type t_pin_code, plus a package-level collection tab_pin_code, which the hook procedures use to drive validation against lookup and address data. Because it operates as a hook, it is designed to be called by the standard HR address validation API rather than by end users directly, and the validation is conditional on the style/context passed in (p_style), allowing the framework to selectively apply Indian-specific checks.

Key Procedures and Functions

The ETRM documentation lists four procedures, split across personal addresses and location addresses, and across insert versus update operations:

• CHECK_PER_ADDRESS_INS — The driver procedure for validating the address of a person when a personal address is inserted. It is the insert-time hook for PER_ADDRESSES rows and receives style, address identifier, and address information (including state and postal code) for validation.
• CHECK_LOC_ADDRESS_INS — The driver procedure for validating a location address when a location address is inserted. It is the insert-time hook for HR_LOCATIONS_ALL addresses, receiving style, location state information, and postal code.
• CHECK_PER_ADDRESS_UPD — The counterpart hook invoked when a personal address is updated, applying the same Indian address validation rules on modification of PER_ADDRESSES data.
• CHECK_LOC_ADDRESS_UPD — The counterpart hook invoked when a location address is updated, applying Indian validation rules on modification of HR_LOCATIONS_ALL address data.

No parameter lists for CHECK_PER_ADDRESS_UPD or CHECK_LOC_ADDRESS_UPD are provided in the documented excerpt; only the insert procedures expose partial signatures. Based on the metadata, all four procedures share the same purpose: enforcing India-specific validation of state/PIN code consistency for the relevant address context.

Tables Accessed

The package references the following tables through APPS synonyms:

• HR_LOCATIONS_ALL — The base table of location address records. It is read/written in the context of validating location addresses via the location insert/update hooks.
• PER_ADDRESSES — Stores personal (person-level) address rows. Accessed for validating personal addresses through the personal insert/update hooks.
• DUAL — Used for single-row scalar operations and lookups that do not require a persistent table, typical of PL/SQL validation helpers.
• PLITBLM — The Oracle HR application's generic index-by PL/SQL table structure used to hold and pass multi-row validation data (here matching the t_pin_code collection defined in the package) in and out of validation logic.

Because HR_LOCATIONS_ALL and PER_ADDRESSES are the canonical HR address entities, the package validates address changes at their source, ensuring invalid state/PIN combinations are rejected before they are committed. The use of HR_LOCATIONS_ALL and PLITBLM also points to lookup-style validation against Indian state and PIN code reference data held within the HR lookup framework (hr_lookups, as implied by the record type based on hr_lookups.lookup_code and hr_lookups.meaning).

Usage Notes

PER_IN_ADD_LEG_HOOK is not intended for direct invocation by end users or typical customizations. It is automatically invoked by the standard HR address validation infrastructure whenever Indian personal or location addresses are inserted or updated. In Oracle EBS, such legislative hook packages are called from within the HR address API layer, and the p_style parameter determines whether the Indian validation rules apply. The package is further documented as referenced by four other packages within APPS, underscoring its position as a dependent component of the HR address validation chain rather than a standalone API. In EBS 12.1.1 and 12.2.2, this logic operates identically at the database tier; the E-Business Suite architecture does not alter the PL/SQL package behavior between these releases. Customers who need to extend or troubleshoot Indian address validation should treat this package as read-only Oracle-owned code and extend behavior through supported country-specific hook mechanisms rather than modifying the seeded package directly. Forms such as the Person and Location address maintenance screens trigger these hooks indirectly through the underlying HR APIs; concurrent programs that load or update addresses through the HR interfaces likewise route through the same validation path.