Results for “gl_calendar”

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

Overview

PN_VAR_RENT_PKG is the variable rent engine of the Oracle Property Manager (PN) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Variable rent describes lease and tenancy charges that are not fixed for the term of the agreement but are calculated periodically from reported sales, occupancy, or other measurable activity — the classic percentage-rent and overage-rent arrangements found in retail leases. The package body maintains the period-by-period rental schedule that Property Manager uses to bill tenants for these computed amounts.

The package owns the full life cycle of variable rent data. It derives accounting and reporting periods from the GL calendar, expands a variable rent definition into individual period rows, and deletes or regenerates those rows when lease terms, rent dates, or sales figures change. Because variable rent schedules feed invoice generation, the package also provides existence checks and cascading cleanup routines so that aborted or amended agreements do not leave orphaned invoices, breakpoints, deductions, or volume history records behind. The header notes that the generated period data is consumed by the view PN_PAYMENT_SCHEDULES_V, which places this package squarely in the payment schedule and billing path.

Key Procedures and Functions

• INSERT_PERIODS_ROW / DELETE_PERIODS_ROW — Atomic maintenance of individual rows in PN_VAR_PERIODS, including descriptive flexfield attribute columns and proration factor. A multi-org change and the migration from PN_VAR_PERIODS to the _ALL table are recorded in the header history.
• CREATE_VAR_RENT_PERIODS / CREATE_VAR_RENT_PERIODS_NOCAL — The core drivers that explode variable rent definitions into period rows. The NOCAL variant bypasses GL calendar derivation, supporting non-calendar or user-supplied period boundaries.
• DELETE_VAR_RENT_PERIODS / UPDATE_VAR_RENT_PERIODS — Bulk removal and amendment of variable rent schedules when terms change.
• CREATE_REPORT_DATES, INSERT_REPORT_DATE_ROW, DELETE_REPORT_DATE_ROW, INSERT_GRP_DATE_ROW, DELETE_GRP_DATE_ROW — Maintenance of reporting and grouping date structures used to align variable rent measurement periods with tenant reporting cycles.
• DELETE_VAR_RENT_CONSTR, DELETE_VAR_RENT_LINES, DELETE_VAR_VOL_HIST, DELETE_VAR_RENT_DEDUCT, DELETE_VAR_BKPTS_HEAD, DELETE_VAR_BKPTS_DET, DELETE_VAR_RENT_INVOICES — Cascading cleanup of tenant constraints, rent lines, volume history, deductions, breakpoint header and detail records, and any invoices already raised for the variable rent.
• FIND_IF_PERIOD_EXISTS / FIND_IF_INVOICE_EXISTS — Validation functions used before creation or deletion to prevent duplicate periods and to protect invoiced data.

Tables Accessed

The package reads lease and tenancy context from PN_LEASES_ALL, PN_LEASE_DETAILS_ALL, PN_LEASE_DETAILS_HISTORY, PN_LOCATIONS_ALL, and PN_TENANCIES_ALL. The GL calendar is accessed through GL_PERIODS, which is the object returned when users search for gl_calendar in this context: CREATE_VAR_RENT_PERIODS relies on GL period definitions to align lease periods to accounting periods. Variable rent configuration lives in PN_VAR_RENTS_ALL and PN_VAR_RENT_DATES_ALL, with generated schedules written to PN_VAR_PERIODS and reporting/grouping dates in PN_VAR_GRP_DATES. Billing integration uses PN_PAYMENT_ITEMS, PN_PAYMENT_ITEMS_ALL, PN_PAYMENT_SCHEDULES_ALL, PN_PAYMENT_TERMS, and PN_PAYMENT_TERMS_ALL.

Usage Notes

PN_VAR_RENT_PKG is an internal implementation package rather than a public API; it is classified as OTHER. It is invoked primarily from the Property Manager variable rent windows during rent definition, schedule regeneration, and termination processing. Regeneration is also triggered when lease dates or sales reports are modified. With 54 dependent packages, it is referenced widely across Property Manager billing, invoice, and reporting logic, so customizations should call the existing procedures rather than issuing DML against PN_VAR_PERIODS directly. The header reference to PN_COMMON.debug() indicates the package participates in the standard EBS debug logging convention.