Search Results set_transferred_code




Overview
Explore in AI Chat

Overview

PN_APPROVE_VARENT_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified in the ETRM repository as an OTHER-type API rather than a standard public interface. It belongs to the Property Manager (PN) product family and supports the processing of variable rent agreements, in which lease payments fluctuate based on periodic measurement of actual usage — volume, sales, or similar drivers — rather than being fixed for the lease term. The package's central responsibility is to finalize (approve) the variable rent payment term batches generated during periodic variable rent processing, and to propagate the resulting status to the underlying lease and payment term records so that distributions can be created and invoiced correctly.

The object is reported with a status of VALID in the ETRM metadata. Its dependency footprint is confined to the SYS schema and the STANDARD package, meaning it does not depend on other application packages; the documented metadata indicates it is referenced by zero other packages, which is consistent with a package positioned at or near the top of the application call stack.

Key Procedures and Functions

The ETRM documentation records two program units within this package:

  • APPROVE_PAYMENT_TERM_BATCH — The principal entry point. Its purpose is to approve one or more payment term batches produced by the variable rent calculation process. Approval transitions the batch and its associated variable rent records into an accepted state, after which the system may generate distributions and invoice the approved amounts. It operates against the PN_PAYMENT_TERMS and PN_PAYMENT_TERMS_ALL tables and the related variable rent tables.
  • SET_TRANSFERRED_CODE — A supporting routine that applies the appropriate transferred status code to the qualifying records. It marks records that have been carried forward from variable rent processing into the payment term structure, preserving the audit trail between the calculated variable rent and the resulting approved payment obligation.

No parameter lists are asserted here; the documented metadata does not expose them, and they should be confirmed from the package source in the target environment before any custom invocation.

Tables Accessed

The package touches a broad set of Property Manager tables, primarily through APPS synonyms. The core tables are PN_PAYMENT_TERMS and PN_PAYMENT_TERMS_ALL, which hold the payment term definitions and their translated or versioned rows, and PN_DISTRIBUTIONS_ALL, which stores the payment distributions generated from approved terms. Variable-rent-specific tables include PN_VAR_RENTS and PN_VAR_RENTS_ALL, PN_VAR_RENT_INV_ALL, PN_VAR_DEDUCTIONS_ALL, PN_VAR_GRP_DATES_ALL, PN_VAR_PERIODS_ALL, and PN_VAR_VOL_HIST_ALL, which collectively represent variable rent definitions, invoices, deductions, grouping dates, accounting periods, and volume history. Lease context is supplied by PN_LEASES, PN_LEASES_ALL, PN_LEASE_DETAILS_ALL, and PN_LOCATIONS_ALL, while the inferred package name indicates logic relating to variable rent entries. Writes are concentrated on the payment term, distribution, and variable rent tables; lease and location tables are read to validate and derive context.

Usage Notes

This package is best understood as an internal processing library rather than a documented public API. It is typically invoked indirectly — from Property Manager forms or concurrent programs that run variable rent approval and payment term generation — rather than called directly by customers. Because it is not referenced by other packages, custom code that calls it must be treated as a direct dependency on internal EBS functionality, which Oracle may change in patches or upgrades. Developers integrating with it should validate parameter signatures against the actual package specification in 12.1.1 or 12.2.2, avoid hardcoding internal status codes, and test thoroughly after any applied patch. Execution should generally be performed with the standard APPS initialization, respecting MOAC and security context where the calling concurrent program sets it.