Search Results rent_increase_detail

Overview

APPS.PNRX_C_RENT_INCREASE_DETAIL is a PL/SQL package body belonging to the Oracle Property Manager (PNRX) module of Oracle E-Business Suite. The package is registered under the APPS schema with an API classification of "OTHER," indicating that it is not a public application programming interface intended for external integration, but rather an internal processing artifact used to support Property Manager rent-increase report functionality. Its guiding purpose is to retrieve and present details of rent increases that apply to leases within a given range and time window, most notably as the executable behind a concurrent program that produces the Rent Increase Detail report.

The header comment dated 2007/10/03 and the file name convention PNRXCRDB.pls confirm that the object is a legacy scripted concurrent program unit, retained unchanged through the 12.1.1 and 12.2.2 releases for backward compatibility. It operates entirely within the APPS schema and relies on the standard Oracle EBS concurrent manager calling convention.

Key Procedures and Functions

The package body exposes a single documented procedure:

• RENT_INCREASE_DETAIL — the report driver. It follows the standard concurrent program signature, accepting an OUT NOCOPY error buffer and return code along with a long series of positional IN VARCHAR2 arguments. Arguments 1 through 4 are explicitly annotated in the source as lease_number_low, lease_number_high, from_date, and to_date, forming the core run-time selection criteria: a lease number range and an effective-date window. The remaining parameters (arguments 5 through 45) are unnamed and each is declared with a DEFAULT NULL, a pattern typical of generic report submissions where the concurrent program definition supplies more parameter slots than the logic strictly requires. The procedure evaluates the supplied lease and date limits, gathers the qualifying rent-increase records, formats the output, and returns it through the error buffer channel to the concurrent manager.

The metadata documents no additional procedures or functions, and the package is not referenced by any other package, confirming its role as a terminal, self-contained report unit.

Tables Accessed

The ETRM metadata records no table references for this package through APPS synonyms. In practice, a Property Manager rent-increase report of this nature reads lease and rent-increase base tables within the PNRX schema, such as the lease header, lease detail, and rent-increase schedule tables that hold periodic escalation amounts and effective dates. Because the extraction was captured without resolved synonym dependencies, the precise table list cannot be confirmed from the supplied metadata; reliance on the PNRX lease and rent-increase entities nonetheless follows directly from the documented lease number and date range parameters.

Usage Notes

The procedure is designed to be invoked exclusively by the Oracle EBS Concurrent Manager as a report-based concurrent program. It is not wired to any form or public API, and no other packages depend on it. Typical invocation occurs when a user submits the Rent Increase Detail report from the Property Manager responsibility, supplying a low and high lease number and a date range; the concurrent manager passes these as arguments 1 through 4 into the procedure and captures the formatted output. Administrators should treat the package as internal, avoid direct custom calls to RENT_INCREASE_DETAIL, and instead consume the report output. Because the procedure relies on the OUT NOCOPY error buffer for status, any wrapper developed for diagnostics must replicate the concurrent program registration and argument mapping exactly.