Search Results parent_not_occpble_asgnble

Overview

PNT_LOCATIONS_PKG is a PL/SQL package owned by the APPS schema that supports the Oracle E-Business Suite Property Manager module (PN / PNT). It provides the core business logic for validating, inserting, updating, and managing location records—rooms, floors, buildings, and other physical spaces—within the property management data model. The package acts as a programmatic layer over the PN_LOCATIONS tables and is responsible for enforcing rules that govern how locations are structured, occupied, and assigned to customers or employees.

Because properties can contain nested or hierarchical locations, the package includes routines to detect overlapping or missing (gap) location boundaries, validate areas, and prevent invalid parent-child assignment combinations. It also handles multi-lingual (MLS) row maintenance through the standard EBS row-handling API pattern used by the Property Manager forms.

The package is classified as OTHER rather than as a public API. It is an internal utility package, but because it is referenced by five other packages, its correct behavior is essential to dependent functionality.

Key Procedures and Functions

The ETRM metadata documents 24 procedures and functions. The primary groups are:

• Validation: CHECK_LOCATION_OVERLAP and CHECK_LOCATION_GAPS verify that location spans do not overlap or leave gaps. VALIDATE_GROSS_AREA checks gross area values. CHECK_UNIQUE_LOCATION_CODE ensures location codes are unique. CHECK_FOR_POPUP controls whether a pop-up prompt is raised. CHECK_LOCN_ASSGN and PARENT_NOT_OCCPBLE_ASGNBLE enforce assignment rules, including preventing a non-occupiable parent from being assigned.
• Row Handling: SET_ROWID, CORRECT_UPDATE_ROW, INSERT_ROW, UPDATE_ROW, LOCK_ROW, INSERT_LOCN_ROW, UPDATE_LOCN_ROW, and UPDATE_CHILD_FOR_DATES implement the standard EBS row-level DML and locking pattern, including date-effective child row maintenance.
• Status and Assignment: UPDATE_STATUS changes a location's status, and UPDATE_ASSIGNMENTS manages related assignment records. CASCADE_CHILD_LOCN propagates changes to child locations.
• Retrieval: GET_LOCATION_SPAN returns the span of a location, and GET_LOCATION_ID returns a location identifier.

Parameter signatures are not documented in the ETRM metadata, so callers should inspect the package body or use the "show dependent code" link in EBS before invoking these routines directly.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• PN_LOCATIONS_ALL, PN_LOCATIONS, PN_LOCATIONS_S: the base, non-MLS, and MLS (translation) location tables that store location definitions and attributes.
• PN_ADDRESSES_ALL: location addresses, used together with locations for physical space definition.
• PN_SPACE_ASSIGN_CUST_ALL and PN_SPACE_ASSIGN_EMP_ALL: customer and employee space assignment tables, updated by the assignment and cascade routines.
• PN_TENANCIES_ALL: tenancy records linked to location occupancy.
• DUAL and PLITBLM: utility tables used for single-row selection and EBS message/token handling.

Usage Notes

PNT_LOCATIONS_PKG is invoked primarily from the Property Manager forms, which call its validation and row-handling routines during location entry and maintenance. It is also called programmatically by the five dependent packages—PN_CAD_IMPORT, PN_SPACE_ASSIGN_CUST_PKG, PN_SPACE_ASSIGN_EMP_PKG, PN_TENANCIES_PKG, and PNT_LOCATIONS_PKG itself—during space assignment, tenancy processing, and CAD import. Custom code should treat the package as internal (OTHER classification) and avoid bypassing its validation logic, since direct DML on the underlying location tables can violate overlap, gap, and assignment constraints. All identifiers and dependencies cited above are consistent across Oracle EBS 12.1.1 and 12.2.2.