Search Results create_default_constraints




Overview

APPS.PN_VAR_DEFAULTS_PKG is a PL/SQL package within the Oracle E-Business Suite Property Manager (PN) module, responsible for managing variable rent default structures in commercial real estate lease agreements. Its primary business function is to generate, reset, and delete the default constraint and line records that underlie variable rent calculations, such as those based on sales volume, percentage rent, or other performance-driven thresholds. The package provides programmatic support for the default setup data that drives rent escalation, partial-year proration, and agreement population across the variable rent lifecycle.

Key Procedures and Functions

The package exposes fourteen documented programs that fall into three functional clusters: setup creation, deletion/reset, and calculation/lookup.

Tables Accessed

The package reads and writes a wide set of Property Manager base tables accessed via APPS synonyms. Default configuration tables include PN_VAR_BKHD_DEFAULTS_ALL, PN_VAR_BKDT_DEFAULTS_ALL, PN_VAR_LINE_DEFAULTS_ALL, and PN_VAR_CONSTR_DEFAULTS_ALL, which store the default header, detail, line, and constraint definitions. Breakpoint data resides in PN_VAR_BKPTS_HEAD_ALL and PN_VAR_BKPTS_DET_ALL. Core transactional tables include PN_VAR_RENTS_ALL, PN_VAR_LINES_ALL, PN_VAR_PERIODS_ALL, PN_VAR_RENT_DATES_ALL, PN_VAR_GRP_DATES_ALL, and PN_VAR_CONSTRAINTS_ALL. Financial linkage is provided through PN_PAYMENT_TERMS_ALL, PN_PAYMENT_SCHEDULES, and PN_PAYMENT_ITEMS_ALL, which connect default calculations to payment scheduling.

Usage Notes

PN_VAR_DEFAULTS_PKG is typically invoked from Property Manager forms during variable rent setup, as well as from concurrent programs and custom PL/SQL integrations that need to seed or reset default data. Because CREATE_SETUP_DATA and the related creation procedures target a specific X_VAR_RENT_ID, they are commonly called immediately after a variable rent record is established. The package is referenced by six other packages, indicating that it functions as a shared lower-level utility within the PN module. Developers extending EBS 12.1.1 or 12.2.2 should treat these programs as internal APIs, respecting the documented signatures and avoiding direct DML against the underlying _ALL tables to preserve data integrity.