Search Results check_location_overlap

Overview

APPS.PNT_LOCATIONS_PKG is the core PL/SQL package body responsible for managing location records within the Oracle E-Business Suite Property Manager module. In both release 12.1.1 and 12.2.2, this package encapsulates the business logic that governs the creation, validation, update, and querying of space-related location definitions held in the PN_LOCATIONS family of tables. A location in this context represents a physical space unit — a floor, office, cubicle, or other assignable area — that can be occupied by employees or customers and associated with tenancies, space assignments, and variable rent arrangements.

The package operates as an internal engine rather than a directly exposed public API, and the ETRM metadata classifies it as OTHER. It provides reusable procedures and functions that support the Property Manager forms, concurrent processes, and dependent packages such as PNT_ADDR_PKG, PNT_VAR_RENT_PKG, and PN_RECOVERY_EXTRACT_PKG. The body depends on standard EBS infrastructure including FND_API, FND_FILE, FND_GLOBAL, FND_MESSAGE, APP_EXCEPTION, PNP_DEBUG_PKG, and PNP_UTIL_FUNC, indicating that it participates in the standard error-handling, messaging, and debugging framework used throughout the applications schema.

Key Procedures and Functions

The package exposes 24 documented procedures and functions. Rather than operating as a single entry point, it offers granular building blocks that address distinct aspects of location maintenance:

• CHECK_LOCATION_OVERLAP and CHECK_LOCATION_GAPS — validate the spatial configuration of locations, identifying conflicting or missing spans along a defined measurement axis.
• SET_ROWID, INSERT_ROW, UPDATE_ROW, and LOCK_ROW — implement the standard EBS row-handling pattern, giving callers optimistic locking and controlled insert or update behavior against the location tables.
• CORRECT_UPDATE_ROW — applies corrective adjustments to an existing location row, typically when data integrity issues are detected.
• UPDATE_CHILD_FOR_DATES and CASCADE_CHILD_LOCN — propagate date or structural changes from a parent location to its dependent child records.
• CHECK_FOR_POPUP — determines whether a user interaction (such as a warning dialog or confirmation) is required before a change proceeds.
• UPDATE_STATUS and UPDATE_ASSIGNMENTS — manage the lifecycle status of a location and the associated space assignment records.
• VALIDATE_GROSS_AREA — enforces that gross area values are within accepted tolerances before committing.
• GET_LOCATION_SPAN and GET_LOCATION_ID — retrieval helpers that return span measurements or the identifier for a given location.
• CHECK_LOCN_ASSGN, PARENT_NOT_OCCPBLE_ASGNBLE, and CHECK_UNIQUE_LOCATION_CODE — enforce the business rules that prevent invalid assignments, prohibit assignment of non-occupiable parents, and guarantee uniqueness of location codes.
• INSERT_LOCN_ROW and UPDATE_LOCN_ROW — consolidated entry points that combine validation and DML logic for new and modified locations.

Tables Accessed

The package reads and writes through APPS synonyms for PN_LOCATIONS_ALL, PN_LOCATIONS, and PN_LOCATIONS_S. The _ALL view provides multi-organization access, while PN_LOCATIONS_S supplies the security-filtered subset appropriate to the current operating unit. Space assignment data is handled through PN_SPACE_ASSIGN_CUST_ALL and PN_SPACE_ASSIGN_EMP_ALL, reflecting the dual customer and employee assignment model. Tenancy relationships are resolved through PN_TENANCIES_ALL, and address associations through PN_ADDRESSES_ALL. DUAL and PLITBLM appear as utility references, the latter used for PL/SQL table-to-string conversion in debugging and messaging.

Usage Notes

PNT_LOCATIONS_PKG is invoked indirectly rather than called directly by end users or typical custom code. The Property Manager location maintenance forms rely on these procedures for row-level validation and commit processing, and the package is referenced by five additional database objects, including PNT_ADDR_PKG, PNT_VAR_RENT_PKG, and PN_RECOVERY_EXTRACT_PKG. Concurrent programs that extract or migrate location data may also call the insert and update routines. Because the package is not marked as a public API, customizations should prefer calling the documented insert, update, and validation procedures through the supported forms interface. The prominent dependency on FND_API and FND_MESSAGE ensures that errors surface through standard Oracle Application messages, supporting consistent user feedback across releases 12.1.1 and 12.2.2. In environments where customers search for "pn_locations_s," the PN_LOCATIONS_S table is the security-enabled source queried and maintained by this package.