Search Results pnp_util_func




Overview
Explore in AI Chat

Overview

PNP_UTIL_FUNC is a utility package body in the APPS schema that supports Oracle Property Manager (PNP), the EBS module used to administer real estate leases, properties, locations, space assignments, and related payment obligations. The package encapsulates a broad set of reusable calculations and lookups that are required by Property Manager forms, concurrent programs, and dependent PL/SQL packages. Its status is VALID in both the 12.1.1 and 12.2.2 releases, and the ETRM metadata classifies its API type as OTHER, reflecting that it is an internal helper package rather than a formally published public API.

The package is not referenced by any database object, but it is referenced by approximately 51 other packages. This asymmetrical dependency profile confirms that PNP_UTIL_FUNC functions as a shared service layer: consumers such as PN_SPACE_ASSIGN_CUST_PKG and PN_SPACE_ASSIGN_EMP_PKG call into it for validation, date derivation, and occupancy computations. It also depends internally on PNP_DEBUG_PKG and PN_MO_CACHE_UTILS, indicating that it participates in debug tracing and cache management within the Property Manager codebase.

Key Procedures and Functions

The documented interface exposes 122 procedures and functions. The following are representative of the principal functional groupings.

Tables Accessed

The package reads and writes Property Manager base tables through APPS synonyms. Lease and tenancy data is drawn from PN_LEASES_ALL, PN_LEASE_CHANGES_ALL, and PN_TENANCIES_ALL. Financial schedules and terms are sourced from PN_PAYMENT_ITEMS_ALL, PN_PAYMENT_SCHEDULES_ALL, PN_PAYMENT_TERMS_ALL, PN_TERM_TEMPLATES_ALL, PN_VAR_ABATEMENTS_ALL, PN_VAR_RENTS_ALL, and PN_VAR_RENT_INV_ALL. Property and space structures are represented by PN_PROPERTIES_ALL, PN_LOCATIONS, PN_LOCATIONS_ALL, PN_LOCATIONS_S, PN_LOCATION_PARKS, PN_SPACE_ASSIGN_CUST_ALL, and PN_SPACE_ASSIGN_EMP_ALL. Addresses are resolved through PN_ADDRESSES_ALL, and currency context through PN_CURRENCIES.

Cross-module lookups depend on Oracle Payables (AP_TERMS, AP_DISTRIBUTION_SETS, AP_DISTRIBUTION_SETS_ALL), Receivables (RA_CUST_TRX_TYPES, RA_RULES, RA_SALESREPS, RA_TERMS), Projects (PA_PROJECTS_ALL, PA_TASKS, PA_ORGANIZATIONS_EXPEND_V, PA_TASKS_EXPEND_V), General Ledger (GL_PERIODS, GL_PERIOD_STATUSES, GL_SETS_OF_BOOKS, GL_CURRENCY_API), and Human Resources (PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, PER_JOBS, PER_PERSON_TYPES_TL, PER_PHONES, HR_ORGANIZATION_UNITS, HR_LOOKUPS). FND_API, FND_FLEX_APIS, FND_MESSAGE, FND_GLOBAL, FND_LOOKUPS, and FND_TERRITORIES_VL supply application framework services. Dynamic SQL is executed via DBMS_SQL against DUAL and STANDARD.

Usage Notes

PNP_UTIL_FUNC is typically invoked indirectly. Property Manager forms call the dependent space assignment and lease packages, which in turn call PNP_UTIL_FUNC for validation and computation. Concurrent programs that generate lease abstracts, occupancy reports, or billing schedules rely on the same inner functions. Because the package is referenced by 51 other packages but is itself unreferenced, customizations should treat it as an internal implementation detail; direct invocation is possible from custom PL/SQL but is not supported by Oracle. Developers extending Property Manager should prefer the higher-level callers and should be aware that the package performs cross-module lookups into AP, AR, GL, PA, and HR, so performance is sensitive to the setup of those modules.