Search Results pn_addresses_s




Overview
Explore in AI Chat

Overview

PNT_ADDR_PKG is a stored PL/SQL package body owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides in the Oracle Property Manager (PNT) application and provides the data access layer that application logic uses to manage the address records stored in the Property Manager address tables. Property Manager maintains addresses for leases, lessors, lessees, properties, and related parties; the PNT_ADDR_PKG package encapsulates the insert, update, and locking operations against that address data so that calling modules do not issue direct DML against the underlying tables.

The object is documented with a status of VALID and is classified as an OTHER API. It is not referenced by any database object according to the dependency listing, meaning it acts as a terminal consumer in the dependency chain rather than a shared lower-level utility. It does, however, reference other packages, including APP_EXCEPTION, FND_MESSAGE, and PN_VAR_RENT_PKG, which indicates that it raises user-facing errors through the Oracle Application Object Library message framework and participates in rent-related validation logic.

Key Procedures and Functions

The ETRM documentation records three public procedures in the package body:

  • INSERT_ROW — Creates a new address row in the Property Manager address tables. It is the entry point used when a new address must be recorded for a lease, party, or property record.
  • UPDATE_ROW — Modifies the attributes of an existing address row. Callers use it to correct or change address details while preserving the integrity of the surrounding Property Manager data model.
  • LOCK_ROW — Obtains a row-level lock on an address record, typically as the first step in a read-modify-write sequence so that concurrent sessions cannot update the same address simultaneously.

Parameter lists are not documented in the available metadata and are intentionally omitted here. The procedures follow the standard Oracle EBS API convention in which LOCK_ROW precedes UPDATE_ROW within the same transaction.

Tables Accessed

  • PN_ADDRESSES_ALL — the primary multi-organization address table. The package reads and writes address rows through the APPS synonym, subject to the organization security enforced by the _ALL view.
  • PN_ADDRESSES_S — the corresponding sequence or shadow table used to obtain the next primary key value when new address rows are inserted.
  • DUAL — the standard single-row SYS table, used for trivial lookups and sequence or value retrieval within the package logic.

Usage Notes

PNT_ADDR_PKG is typically invoked from Property Manager forms and from other PNT packages that need to create or maintain address records. Because it is not referenced by any database object, it is not exposed as a general-purpose utility; callers reach it through the Property Manager application layer, including the PN_VAR_RENT_PKG package with which it shares dependencies. Errors raised inside the package are surfaced to the user through FND_MESSAGE and APP_EXCEPTION, so custom code that calls these procedures must be prepared to handle the standard applications exception.

Customizations should invoke LOCK_ROW before UPDATE_ROW within a single transaction, and should rely on the package rather than issuing direct DML against PN_ADDRESSES_ALL, since the package enforces the validation and messaging behavior expected by the rest of the Property Manager module. In both 12.1.1 and 12.2.2 the object name and schema are unchanged.