Search Results get_loc_info

Overview

PN_TENANCIES_PKG is the core PL/SQL package in the Oracle Property Manager (PN) module of Oracle E-Business Suite, owned by the APPS schema and validated as VALID in both 12.1.1 and 12.2.2. Its business function is to manage tenancy records — the assignment of space within a property to a tenant, an employee, or a customer — and to govern the allocation of occupiable area across those tenancies. The package centralizes row-level operations on the PN_TENANCIES_ALL entity, enforces uniqueness and overlap rules for primary locations, performs auto space assignment calculations, and exposes helper functions that compute allocated and available area. Because it is classified as "OTHER" rather than a public API, it should be regarded as an internal implementation package that supports the Property Manager forms, concurrent processes, and dependent packages rather than a formally published integration interface.

Key Procedures and Functions

The package exposes 16 documented procedures and functions, which fall into three functional groups.

• DML row handlers: INSERT_ROW, LOCK_ROW, UPDATE_ROW, and DELETE_ROW provide the standard insert, concurrency locking, update, and delete operations against tenancy records. These are the primitives used by the surrounding forms and by the TENANCY block logic.
• Validation routines: CHECK_UNIQUE_PRIMARY_LOCATION ensures that only one primary location exists per tenancy; CHECK_FOR_OVELAP_OF_TENANCY verifies that a proposed tenancy does not overlap an existing one for the same space; and CHECK_TENANCY_DATES validates that the effective start and end dates are internally consistent and fall within allowable ranges.
• Auto space assignment and area calculations: CREATE_AUTO_SPACE_ASSIGN, UPDATE_AUTO_SPACE_ASSIGN, and DELETE_AUTO_SPACE_ASSIGN manage automated allocation of space to customers and employees; UPDATE_DUP_SPACE_ASSIGN handles duplicate assignment corrections; AUTO_ALLOCATED_AREA and AUTO_ALLOCATED_AREA_PCT return the allocated area and its percentage, while AVAILAIBLE_SPACE and GET_ALLOCATED_AREA return available and allocated area respectively; and GET_LOC_INFO retrieves location attribute data needed by the allocation logic.

Tables Accessed

The package reads and writes the primary tenancy tables PN_TENANCIES_ALL, PN_TENANCIES_S (the translated/security variant), PN_TENANCIES_HISTORY, and PN_TENANCIES_HISTORY_S, which hold current and historical tenancy records. Space assignment detail is stored in PN_SPACE_ASSIGN_CUST, PN_SPACE_ASSIGN_CUST_ALL, and PN_SPACE_ASSIGN_EMP_ALL. Location master data is drawn from PN_LOCATIONS_ALL and PN_LOCATIONS. Lease information relevant to tenancy validation comes from PN_LEASES_ALL. Recovery and expiration detail lines are referenced through PN_REC_ARCL_DTLLN_ALL, PN_REC_ARCL_DTL_ALL, PN_REC_EXPCL_DTLLN_ALL, and PN_REC_EXPCL_DTL_ALL. DUAL is used for single-row utility queries. All access is performed through APPS synonyms.

Usage Notes

PN_TENANCIES_PKG is invoked primarily from the Property Manager tenancies and space assignment forms, from the TENANCY and SPACE ASSIGNMENT blocks, and by the dependent package PN_RECOVERY_TENANCY_UPG_PKG. The PN_TENANCIES_V view and the PN_SCHEDULES_ITEMS table-based logic also reference the package, making it central to tenancy-driven space accounting. Because the package is not a published API and its procedures are tightly coupled to the form blocks and to the PN_TENANCIES_ALL row structure, custom code should call it only when operating in the same context. Where an integration requires tenancy creation or update, the supported route is to drive the standard forms or the module's published interfaces rather than invoking these procedures directly. In upgrade scenarios from 12.1.1 to 12.2.2, the package remains VALID and is reused by the recovery/upgrade package, so no recompilation-specific remediation is normally required beyond standard AD administration.