Search Results pn_variable_term_pkg




Overview
Explore in AI Chat

Overview

PN_VARIABLE_TERM_PKG is an Oracle Property Manager (PN) package owned by the APPS schema. It serves the variable-term and payment-term processing requirements of lease and rent management within Oracle E-Business Suite 12.1.1 and 12.2.2. In release 12.2.2 the object is documented as VALID with an API classification of OTHER, reflecting that it is primarily an internal processing engine rather than a published public interface. The package provides the procedural logic that generates, schedules, evaluates, and reverses payment terms associated with leases and variable rent agreements. Its responsibilities include creating single and batch payment terms, computing variable rent amounts on a continuous basis and for defined variable groups, resolving accounting and lease periods, retrieving lease line and invoice date context, deriving schedule status, and producing reversal terms. Because these operations intersect with lease financial schedules and distribution generation, PN_VARIABLE_TERM_PKG forms part of the core calculation layer used by Property Manager for variable rent leases.

Key Procedures and Functions

  • CREATE_PAYMENT_TERMS — Generates payment terms, establishing the term records and associated scheduling data required for a lease or variable rent arrangement.
  • CREATE_PAYMENT_TERM_BATCH — Performs payment term creation in batch, allowing multiple terms to be produced in a single processing run rather than one term at a time.
  • CREATE_REVERSAL_TERMS — Creates reversal terms, supporting correction or back-out of previously generated payment term schedules.
  • GET_SCHEDULE_STATUS — Returns the status of a payment schedule, allowing callers to determine the processing state of schedule records.
  • FIND_VOLUME_CONTINUOUS — Calculates or locates variable rent volume on a continuous basis, supporting variable rent determination across a date range.
  • FIND_VOLUME_CONTINUOUS_FOR — Variant of the volume calculation scoped for a specific context, used when variable rent volume must be resolved for a designated group or period.
  • GET_PERIOD — Resolves the applicable period used by the term generation and variable rent logic.
  • GET_LINE — Retrieves lease line information required during term and schedule construction.
  • GET_INV_DATE — Determines the invoice date applicable to term or schedule processing.

Tables Accessed

The package operates directly against variable rent and lease data. Its dependency list identifies PN_VAR_RENTS_ALL as a referenced object, and the documented synonym set extends to PN_DISTRIBUTIONS and PN_DISTRIBUTIONS_ALL, PN_LEASES and PN_LEASES_ALL, PN_LEASE_DETAILS and PN_LEASE_DETAILS_ALL, PN_LOCATIONS_ALL, PN_PAYMENT_SCHEDULES_ALL, PN_PAYMENT_TERMS and PN_PAYMENT_TERMS_ALL, PN_TERM_TEMPLATES_ALL, PN_VAR_GRP_DATES_ALL, PN_VAR_LINES_ALL, and PN_VAR_PERIODS. In practical terms, the payment term procedures write to PN_PAYMENT_TERMS and related schedule tables, the volume and line procedures read variable rent lines and group dates, and the period and invoice date functions draw on the lease and location context needed to determine the correct accounting period and billing date. Distribution tables are touched where generated terms flow into accounting distributions for the lease.

Usage Notes

PN_VARIABLE_TERM_PKG is intended for internal invocation. The ETRM metadata records that it is referenced by zero other packages, indicating that it is not part of an established package-to-package call chain in the documented release. It is therefore normally reached from Property Manager forms, concurrent programs, or generated scheduling logic rather than from custom integration code. Sites implementing custom variable rent automation should treat the package as a private implementation detail; the documented procedure names may be called with care, but the absence of published parameter signatures and the OTHER API classification mean Oracle does not guarantee interface stability. All access occurs through APPS synonyms, and any custom code referencing these procedures should be validated after applying Property Manager patches or upgrading between 12.1.1 and 12.2.2.