Search Results insert_constraints

Overview

APPS.PN_VAREN_PVT is a private (PVT) PL/SQL package body within the Oracle E-Business Suite Property Manager module. It encapsulates the core business logic that governs variable rent processing, including the creation, maintenance, and reversal of variable rent agreements, their associated billing periods, breakpoints, and constraint definitions. Variable rent refers to lease charges that fluctuate based on measurable business activity — for example, percentage rent tied to a tenant's reported sales — and this package provides the programmatic backbone that translates lease terms into scheduled rent obligations.

The package is classified as PVT, meaning it is intended for internal use by other Property Manager components rather than as a public API for external integration. As reflected in the ETRM metadata, it exposes nine documented procedures and references fifteen tables through APPS synonyms, and it is referenced by one additional package. The body carries a header dated 2010/12/15 and reflects development work centered on the variable rent feature set released in the 12.1.x and 12.2.x code lines.

Key Procedures and Functions

• CREATE_VAR_RENT — Establishes a new variable rent record, creating the parent row in PN_VAR_RENTS_ALL and initializing the downstream period, breakpoint, and constraint structures.
• UPDATE_VAR_RENT — Modifies an existing variable rent definition. This is the procedure most directly associated with the search term "update_var_rent" and is the entry point for maintaining rent terms after initial creation.
• GENERATE_PERIODS — Derives and inserts the individual variable rent billing periods derived from the parent rent record's schedule.
• UNDO_PERIODS — Reverses or deletes previously generated periods, typically invoked when a rent record is amended or removed.
• GENERATE_BREAKPOINTS — Builds the breakpoint header and detail records that define the sales thresholds or tiering used to compute variable rent amounts.
• UNDO_BREAKPOINTS — Removes or reverses generated breakpoint records.
• GENERATE_CONSTRAINTS — Populates constraint records that bound or qualify the variable rent calculation, drawing on constraint default templates.
• UNDO_CONSTRAINTS — Reverses generated constraint records.
• CREATE_BKPT_CONST_ALLOW_ABAT — Creates breakpoint, constraint, and abatement allowance records in a coordinated fashion, supporting the abatement functionality associated with variable rent agreements.

The body also contains internal helper logic such as the GET_ATTRIBUTE_STATUS function and the INSERT_CONSTRAINTS procedure, which delegate to PN_VAR_CONSTR_DEFAULTS_PKG.INSERT_ROW and emit diagnostic output through PN_VAREN_UTIL.PVT_DEBUG.

Tables Accessed

• PN_VAR_RENTS_ALL — The primary variable rent entity table; the anchor for all create, update, and undo operations.
• PN_VAR_RENT_DATES_ALL — Stores individual period/date records referenced by the period generation logic.
• PN_LEASES_ALL, PN_LEASE_DETAILS_ALL, PN_LOCATIONS_ALL — Provide lease, detail, and location context for the variable rent agreement.
• PN_VAR_BKPTS_HEAD_ALL, PN_VAR_BKPTS_DET_ALL — Breakpoint header and detail tables populated by GENERATE_BREAKPOINTS.
• PN_VAR_CONSTRAINTS_ALL, PN_VAR_CONSTR_DEFAULTS_ALL — Constraint instances and their default templates, used by GENERATE_CONSTRAINTS and INSERT_CONSTRAINTS.
• PN_VAR_ABATEMENTS_ALL, PN_VAR_ABAT_DEFAULTS_ALL — Abatement records and defaults supporting CREATE_BKPT_CONST_ALLOW_ABAT.
• PN_VAR_BKHD_DEFAULTS_ALL, PN_VAR_BKDT_DEFAULTS_ALL — Default templates for breakpoint headers and details.
• PN_TERM_TEMPLATES_ALL, PN_SYSTEM_SETUP_OPTIONS — Term template definitions and system configuration.
• FND_USER — Supplies the application user identity for who-column auditing.

Usage Notes

PN_VAREN_PVT is invoked indirectly rather than directly by end users. Property Manager rent entry forms and the variable rent concurrent programs call the public wrapper layer, which in turn drives these PVT procedures. Custom extensions should avoid calling the package directly; instead, they should use the supported public API surface, since PVT packages are subject to change between patch levels without notice. The pattern of paired generate/undo procedures indicates that the package is designed to be re-entrant during amendment workflows: existing derived data is cleared before regeneration to maintain consistency. Diagnostic tracing is available through PN_VAREN_UTIL.PVT_DEBUG, which can be enabled when troubleshooting variable rent processing issues in either 12.1.1 or 12.2.2 environments.