Search Results get_line_expenses

Overview

APPS.PN_REC_CALC_PKG is the recovery calculation engine within the Oracle Property Manager (PN) module of Oracle E-Business Suite, delivered identically in releases 12.1.1 and 12.2.2. Recovery agreements allow a landlord or property manager to bill tenants for a contractually agreed share of operating expenses, taxes, and other recoverable costs. This package encapsulates the business logic that determines what is recoverable, how much of it applies to a given tenant, and when the resulting charges should be billed. The package is classified as OTHER in the ETRM metadata, indicating that it is an internal engine rather than a formally published open interface, and is referenced by one other package in the application. The header comments confirm its central public entry point, CALCULATE_REC_AMOUNT_BATCH, originated in 2003 and has been maintained through later 11i and R12 patch levels, including fixes for date-format handling and lazy upgrade of term templates used by E-Tax. All logic resolves through APPS synonyms, so the package operates exclusively against the PN schema objects owned by the application.

Key Procedures and Functions

The package exposes 25 documented procedures and functions, organized into several functional clusters.

• Batch and single calculation: CALCULATE_REC_AMOUNT_BATCH performs recovery calculation for a set of recovery agreements or agreement lines over a calculation period, accepting identifying keys such as recovery agreement, lease, location, customer, customer site, agreement line, calculation period, and period start/end and as-of dates, with errbuf and retcode standard concurrent program OUT parameters. CALCULATE_REC_AMOUNT provides the equivalent processing for an individual agreement.
• Measurement and expense sources: GET_RECOVERABLE_AREA, TEN_RECOVERABLE_AREA, and GET_TOT_PROP_AREA derive the recoverable and total property areas used to prorate tenant shares. GET_LINE_EXPENSES, GET_BUDGET_EXPENSES, GET_CONTR_ACTUAL_RECOVERY, and GET_BILLED_RECOVERY gather the expense, budget, contractual actual recovery, and previously billed recovery amounts against which the current period calculation is performed.
• Constraint and abatement retrieval: GET_LINE_CONSTRAINTS and GET_LINE_ABATEMENTS fetch the caps, floors, exclusions, and abatements that modify a recovery line's outcome.
• Period line maintenance: FIND_IF_PERIOD_LINE_EXISTS, INSERT_PERIOD_LINES_ROW, UPDATE_PERIOD_LINES_ROW, and DELETE_PERIOD_LINES_ROW maintain the calculation detail rows for a period.
• Billing and payment terms: FIND_IF_PERIOD_BILLREC_EXISTS, INSERT_PERIOD_BILLREC_ROW, UPDATE_PERIOD_BILLREC_ROW, and DELETE_PERIOD_BILLREC_ROW manage the billing/recovery records produced by a calculation, while CREATE_PAYMENT_TERMS and FIND_IF_REC_PAYTERM_EXISTS establish and verify the payment terms attached to recovery billing.

Tables Accessed

The package reads and writes the core Property Manager recovery tables through APPS synonyms. Configuration and agreement data come from PN_REC_AGREEMENTS_ALL, PN_REC_AGR_LINES_ALL, PN_REC_AGR_LINCONST_ALL, and PN_REC_AGR_LINABAT_ALL. Period definition and output are held in PN_REC_CALC_PERIODS_ALL, PN_REC_PERIOD_LINES_ALL, and PN_REC_PERIOD_BILL_ALL. Expense and distribution details are sourced from PN_REC_ARCL_DTL_ALL, PN_REC_ARCL_DTLLN_ALL, PN_REC_EXPCL_DTLLN_ALL, PN_DISTRIBUTIONS, and PN_DISTRIBUTIONS_ALL. Property and lease context come from PN_LEASES and PN_LEASES_ALL. Payment terms are stored in and retrieved from PN_PAYMENT_TERMS_ALL.

Usage Notes

PN_REC_CALC_PKG is normally invoked indirectly. The Property Manager recovery calculation concurrent program calls CALCULATE_REC_AMOUNT_BATCH, and the recovery calculation and payment terms forms call the single-record procedures and the CREATE_PAYMENT_TERMS and FIND_IF_REC_PAYTERM_EXISTS routines. The errbuf and retcode parameters confirm concurrent program invocation. Custom code should call only the documented public procedures, supply dates in the expected character format, and avoid direct DML against the underlying PN tables so that the package's validation, abatement, and constraint logic remains intact.