Search Results p_date_to

Overview

APPS.PER_PL_ADDRESS is a PL/SQL package in the Oracle E-Business Suite Human Resources (PER) product family. Its name and procedure signatures indicate that it encapsulates the business logic required to create, validate, and maintain person addresses associated with a specific legislative or localization context (the "PL" component of the name). In Oracle EBS 12.1.1 and 12.2.2, person addresses are date-tracked records stored in PER_ADDRESSES, keyed by address type, effective dates, and person. The package provides a controlled API layer over that data so that calling programs do not write directly to the underlying table. It is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than the definer, a common convention for EBS APIs that rely on APPS synonyms and row-level security. The package is classified as OTHER in the ETRM data dictionary, indicating it is not a public, supported-interface API in the same sense as the major HR person APIs, but it remains referenced by three other packages within the application, making it a shared internal dependency for address processing. The requested search term, p_date_to, appears consistently across the package's procedure signatures, reflecting the effective-dating model that governs all person address records in EBS.

Key Procedures and Functions

The package exposes five documented procedures, all of which accept date-effective parameters including p_date_to.

• CHECK_ADDRESS_UNIQUE — Validates that a proposed address record does not overlap or duplicate an existing record for the same person, address type, and date range. It accepts an override flag (p_pradd_ovlapval_override) permitting callers to bypass the overlap validation when business rules allow.
• CHECK_PL_ADDRESS — Performs address validation for the localization context, in addition to uniqueness checking. It receives the address lines along with the effective dates, person, and address type, and applies the same override switch.
• CREATE_PL_ADDRESS — Inserts a new person address record. It accepts a style parameter, address type, effective dates, person identifier, and address line values, subject to the overlap validation override.
• UPDATE_PL_ADDRESS — Modifies an existing address record identified by p_address_id, updating type, effective dates, and address line values.
• UPDATE_PL_ADDRESS_STYLE — Updates the address record together with its style attribute, allowing the formatting or style assignment for an address to be changed alongside its substantive content.

Tables Accessed

The only table documented as accessed through APPS synonyms is PER_ADDRESSES. This is the core HR table storing person address records, including address type, effective start and end dates (the columns behind p_date_from and p_date_to), address lines, and the owning person identifier. All five procedures operate against this table: the check routines query it to detect overlaps, while the create and update routines insert or modify rows within it.

Usage Notes

Because PER_PL_ADDRESS is classified as OTHER and is referenced by three other packages, it is best understood as an internal implementation package invoked by higher-level HR APIs and localization routines rather than by external integrations. It is typically called from Oracle Forms address maintenance blocks, from other PL/SQL packages performing person or assignment processing, and from custom code that needs to create or amend person addresses while respecting effective-date overlap rules. Developers invoking it directly should supply valid p_date_from and p_date_to values, since effective dating is central to the uniqueness logic, and should use the override parameter only when a documented business exception justifies bypassing overlap validation. Direct DML against PER_ADDRESSES should be avoided in favour of these procedures to preserve date-track integrity.