Search Results rollforward_terms

Overview

PN_MTM_ROLLFORWARD_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Property Manager (PN) module within the Enterprise Asset Management / Real Estate family. Its core business function is the mass roll-forward of lease and tenancy records from one accounting or operational period to the next. Roll-forward processing is central to lease administration: when a lease term, escalation, variable rent obligation, or tenancy assignment must be carried into a new period, the system must reproduce the prior structure, recalculate effective dates and amounts, and insert the successor records into the base tables without manual re-entry. This package encapsulates that logic for indexed leases, tenancies, variable rents, and lease terms.

The package is classified as OTHER in the documented API metadata, meaning it is an internal utility package rather than a publicly published open interface. It is present and VALID in ETRM 12.2.2, and the same object exists under the APPS schema in 12.1.1. The documentation exposes the package specification and body with no standalone SQL statement definitions, which is consistent with a procedural batch package that orchestrates DML across several Property Manager base tables.

Key Procedures and Functions

• ROLLFORWARD_LEASES — Drives the roll-forward of lease records into a subsequent period, generating successor lease rows derived from the source lease definition.
• ROLLFORWARD_TENANCIES — Performs the equivalent roll-forward for tenancy records, carrying space assignment and occupancy relationships forward.
• ROLLFORWARD_VAR_RENT — Rolls forward variable rent definitions and their associated calculation basis, ensuring percentage-rent or sales-based rent obligations continue into the new period.
• ROLLFORWARD_TERMS — Reproduces lease terms and their effective-dated attributes for the target period.
• CREATE_AMENDMENT — Creates an amendment record associated with a rolled-forward or modified lease, capturing the change as a discrete amendable event rather than an in-place update.
• PRINT_OUTPUT — Produces the processing output or report text generated by a roll-forward run, supporting review and audit of the records created.

No parameter lists are published in the documented metadata, so callers should resolve signatures from the package specification in the database before invoking these units directly.

Tables Accessed

The package operates across the principal Property Manager base tables, referenced through APPS synonyms:

• PN_LEASES_ALL, PN_LEASE_DETAILS_ALL, PN_INDEX_LEASES_ALL — source and target lease headers, detail lines, and index-based lease provisions subject to roll-forward.
• PN_TENANCIES_ALL, PN_SPACE_ASSIGN_CUST_ALL — tenancy records and customer space assignments carried into the new period.
• PN_VAR_RENTS_ALL — variable rent definitions and their basis data.
• PN_PAYMENT_TERMS_ALL — payment term references applied to the reproduced lease and tenancy rows.
• PN_PROPERTIES_ALL, PN_LOCATIONS_ALL — property and location context used to resolve the correct space and address references.
• DBMS_SQL, DUAL — dynamic SQL support and singleton row constructs used internally for statement construction and control logic.

Usage Notes

PN_MTM_ROLLFORWARD_PKG is not referenced by any other documented package, indicating it sits at the top of its call stack and is invoked either from Property Manager forms or from a concurrent program that schedules period-end processing. Customizations should treat it as an internal package: because the procedures write directly to the base tables rather than through a validated interface, any direct invocation must replicate the application's context, concurrency, and validation expectations. Where the application provides a concurrent program for lease or tenancy roll-forward, that program is the preferred entry point, and PRINT_OUTPUT should be used to capture the run results for reconciliation.