Search Results generate_constraints

Overview

PN_VAREN_PVT is an Oracle Property Manager (PN) private API package that manages the variable rent component of lease agreements. Variable rent provisions allow lease contracts to charge rent based on measurable business activity — percentage rent, cumulative sales breakpoints, or excess abatements — rather than a fixed schedule. The package is classified as PVT (private), meaning its interface is not committed for external or cross-module invocation and is intended for consumption by other PL/SQL units within the PN application. The header declares AUTHID CURRENT_USER and pins an API version constant (g_api_version_number) of 1.0, alongside module-level constants for success, warning, and error return codes and cached FND globals (g_user_id, g_login_id, g_org_id, g_sysdate). Its scope is the full variable rent lifecycle: creation of the variable rent definition, generation of billing periods and breakpoint structures, generation of constraint records, and the corresponding undo operations.

Key Procedures and Functions

Nine documented entry points are exposed. CREATE_VAR_RENT establishes a new variable rent definition on a lease, deriving defaults from the lookup types declared in the package header. UPDATE_VAR_RENT modifies an existing variable rent definition. GENERATE_PERIODS builds the variable rent period rows derived from the lease term and the applicable proration and calculation method rules. UNDO_PERIODS reverses a prior period generation. GENERATE_BREAKPOINTS constructs the breakpoint header and detail records that define percentage rent tiers. UNDO_BREAKPOINTS removes previously generated breakpoint structures; this is the procedure most directly associated with the search term undo_breakpoints. GENERATE_CONSTRAINTS creates the variable rent constraint records that limit or condition variable rent charges, and UNDO_CONSTRAINTS reverses that generation. CREATE_BKPT_CONST_ALLOW_ABAT supports the combined creation of breakpoint, constraint, and allowable abatement data. Because this is a private package, undo procedures are typically paired one-to-one with their generate counterparts and are invoked as a set rather than individually.

Tables Accessed

Core persistence is in PN_VAR_RENTS_ALL, which stores the variable rent definitions, keyed against PN_LEASES_ALL, PN_LEASE_DETAILS_ALL, and PN_LOCATIONS_ALL. Breakpoint data resides in PN_VAR_BKPTS_HEAD_ALL and PN_VAR_BKPTS_DET_ALL. Constraints are held in PN_VAR_CONSTRAINTS_ALL. Abatement and defaulting information is read from PN_VAR_ABATEMENTS_ALL, PN_VAR_ABAT_DEFAULTS_ALL, PN_VAR_BKDT_DEFAULTS_ALL, PN_VAR_BKHD_DEFAULTS_ALL, and PN_VAR_CONSTR_DEFAULTS_ALL. Term template behavior is sourced from PN_TERM_TEMPLATES_ALL, and system-level behavior from PN_SYSTEM_SETUP_OPTIONS. FND_USER supplies the who-column audit values. All access is performed through APPS synonyms.

Usage Notes

PN_VAREN_PVT is invoked by the Property Manager variable rent and breakpoint maintenance forms and by concurrent programs that (re)generate or remove variable rent structures across one or more leases. It is referenced by one other package, consistent with its private classification. Direct calls from custom code are not recommended; the supported integration surface is the corresponding public API or the standard UI and concurrent request paths. When troubleshooting undo_breakpoints behavior, note that undo operations assume the current state of PN_VAR_BKPTS_HEAD_ALL, PN_VAR_BKPTS_DET_ALL, and dependent period records — partial or externally modified data can cause the undo to fail or produce inconsistent results, so regeneration and undo should be performed as a coordinated pair.