Search Results pn_var_trx_pkg




Overview

APPS.PN_VAR_TRX_PKG is a PL/SQL package body in the Oracle E-Business Suite Property Manager (PN) module. It provides the transactional backbone for variable rent processing, supporting the calculation and persistence of variable rent transactions derived from sales, volume, and other performance-based measures. In the ETRM (Enterprise Tenant and Lease Management) context, variable rent arrangements allow landlords and tenants to settle rent based on actual business activity reported during a period rather than a fixed contractual amount. This package encapsulates the logic required to build, populate, and maintain those variable rent transactions across billing periods.

The package is owned by the APPS schema and holds a VALID status. It is not referenced by any other database object, but it depends on a broad set of PN variable rent tables and on PN_VAR_RENT_CALC_PKG, indicating that PN_VAR_TRX_PKG acts as the transaction persistence layer beneath the rent calculation engine. It is classified as a non-public API (OTHER) and is primarily intended for internal use within the variable rent subsystem.

Key Procedures and Functions

The package exposes twenty-nine documented procedures and functions that manage the lifecycle of variable rent transactions.

Tables Accessed

The package interacts with the core variable rent transaction and configuration tables through APPS synonyms:

Usage Notes

PN_VAR_TRX_PKG is invoked internally by the variable rent processing flow rather than directly by end users. It is typically called after PN_VAR_RENT_CALC_PKG has computed the underlying rent amounts, with PN_VAR_TRX_PKG responsible for persisting those results as transaction records. Its EXISTS and DELETE procedures support safe re-execution of generation runs, allowing recalculation without duplicating data.

In Oracle EBS 12.1.1 and 12.2.2, the package is reached through concurrent programs and Property Manager forms that drive variable rent sales and volume processing. Because it is documented as not referenced by any other database object but is itself dependent on numerous PN tables, customizations should treat it as an internal implementation package: direct calls are not part of the supported public API, and any extension should be confined to the documented transaction tables. Developers troubleshooting variable rent transaction generation should inspect this package first, as it governs the header/detail insert, grouping, and sales/volume projection logic for the entire variable rent settlement cycle.