Results for “create_var_rent_periods”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_VAR_RENT_PKG is an Oracle Property Manager (ETRM) PL/SQL package owned by the APPS schema. It encapsulates the business logic that governs variable rent processing for leases: the generation, maintenance, and removal of variable rent periods, group dates, billing checkpoints, and associated invoices. The package implements the calendar-driven side of variable rent accounting, in which actual or forecasted sales, usage, or other variable measures are converted into periodic rent obligations, prorated across GL and lease period boundaries, and reconciled against reporting and invoicing schedules.

The package header declares two composite record types used throughout the API. The grp_date_info_rec record mirrors the reporting calendar columns of PN_VAR_GRP_DATES, carrying group dates, reporting due dates, invoice start and end dates, invoice schedule dates, and forecasted expense codes. The proration_factor_rec record holds the proration factors and GL day counts required to split amounts between the start and end of both GL periods and lease group dates. A package-level status constant set to 'REVERSED' is also declared for use in reversal logic.

Key Procedures and Functions

The documented API surfaces seventy-six procedures and functions, divisible by function:

• Period maintenance: INSERT_PERIODS_ROW and DELETE_PERIODS_ROW operate on individual rows of PN_VAR_PERIODS; CREATE_VAR_RENT_PERIODS and CREATE_VAR_RENT_PERIODS_NOCAL generate variable rent periods for a lease (the NOCAL variant bypasses calendar recalculation or logging); UPDATE_VAR_RENT_PERIODS amends existing periods; DELETE_VAR_RENT_PERIODS removes them.
• Report and group date maintenance: CREATE_REPORT_DATES, INSERT_REPORT_DATE_ROW, DELETE_REPORT_DATE_ROW, INSERT_GRP_DATE_ROW, and DELETE_GRP_DATE_ROW manage the reporting calendar structures held in PN_VAR_GRP_DATES and PN_VAR_RENT_DATES_ALL.
• Billing checkpoint handling: DELETE_VAR_BKPTS_HEAD and DELETE_VAR_BKPTS_DET remove checkpoint header and detail records. The checkpoint routines are the objects most closely associated with the search term "delete_var_bkpts_head".
• Dependent data cleanup: DELETE_VAR_RENT_CONSTR, DELETE_VAR_RENT_LINES, DELETE_VAR_VOL_HIST, DELETE_VAR_RENT_DEDUCT, and DELETE_VAR_RENT_INVOICES purge constraints, rent lines, volume history, deductions, and generated invoices tied to a variable rent arrangement.
• Existence checks: FIND_IF_PERIOD_EXISTS and FIND_IF_INVOICE_EXISTS perform validation queries used before inserts or deletes.

INSERT_PERIODS_ROW demonstrates the standard EBS row-handling contract, accepting a ROWID and surrogate key as IN OUT NOCOPY parameters alongside the period dates, proration factor, partial-period flag, and a full descriptive flexfield attribute set.

Tables Accessed

All tables are reached through APPS synonyms. The core variable rent tables are PN_VAR_RENTS_ALL, PN_VAR_PERIODS, PN_VAR_GRP_DATES, and PN_VAR_RENT_DATES_ALL. Lease context is supplied by PN_LEASES_ALL, PN_LEASE_DETAILS_ALL, PN_LEASE_DETAILS_HISTORY, PN_LOCATIONS_ALL, and PN_TENANCIES_ALL. Financial detail flows through PN_PAYMENT_ITEMS, PN_PAYMENT_ITEMS_ALL, PN_PAYMENT_SCHEDULES_ALL, PN_PAYMENT_TERMS, and PN_PAYMENT_TERMS_ALL. GL_PERIODS is consulted to align period generation and proration with the accounting calendar. These reads and writes support the full lifecycle from rent setup through invoice generation and subsequent cleanup.

Usage Notes

PN_VAR_RENT_PKG is referenced by fifty-four other packages, indicating that it functions as a shared service layer rather than an entry-point UI API. It is typically invoked from Property Manager forms and concurrent programs that process variable rent (for example, report date creation and variable rent period generation), and from other PL/SQL units performing cascading deletes when a variable rent arrangement, lease, or reporting calendar changes. Custom code should call these procedures only within the transaction boundaries expected by the calling EBS process, and should treat DELETE_VAR_BKPTS_HEAD and its detail counterpart as destructive operations requiring prior validation via FIND_IF_PERIOD_EXISTS or FIND_IF_INVOICE_EXISTS. Because the package writes to payables-facing payment schedules, changes should be synchronized with the standard Property Manager and Payables accounting flows.