Search Results populate_sales

Overview

APPS.PN_VAR_TRX_PKG is the core PL/SQL package within the Oracle E-Business Suite Property Manager (PN) module responsible for generating and maintaining variable rent transaction records. Variable rent is the component of a lease that is calculated from actual sales volume reported by a tenant, rather than a fixed contractual amount. This package encapsulates the business logic that converts reported sales figures into calculated rent obligations across defined accounting periods.

The package serves as the primary programmatic boundary between sales reporting data and the PN_VAR_TRX_HEADERS_ALL / PN_VAR_TRX_DETAILS_ALL transaction tables. It implements multiple calculation methods — cumulative, non-cumulative, year-to-date, and true-up — along with a set of proration rules (NP, STD, FY, LY, FLY, CYP, CYNP) that determine how sales thresholds and rent brackets are applied when a lease period does not align with a reporting calendar. It also manages sales volume lifecycle states (APPROVED, DRAFT, ON_HOLD) and period states (ACTIVE, REVERSED), ensuring that only valid data drives financial transactions.

Key Procedures and Functions

The package exposes 29 documented program units. Among the most significant, given that insert_trx_hdr was the searched symbol, are the transaction maintenance routines:

• INSERT_TRX_HDR — Inserts a new row into the variable rent transaction header table. It accepts a transaction header identifier as an IN OUT NOCOPY parameter so that a newly generated primary key can be returned to the caller, alongside the full set of context attributes required for the transaction: variable rent and period references, line item and group/date identifiers, calculation period boundaries, reset and line item group identifiers, and the monetary values derived from proration and year-to-date processing.
• INSERT_TRX_DTL — Inserts corresponding detail rows linked to a transaction header, tying breakpoint-level information to the transaction record.
• EXISTS_TRX_HDR and EXISTS_TRX_DTL — Validation functions that determine whether a matching transaction already exists, preventing duplicate generation for the same variable rent, period, line item, and date combination.
• POPULATE_TRANSACTIONS and DELETE_TRANSACTIONS — Orchestration routines that drive bulk generation and cleanup of transaction records for a processing run.
• POPULATE_LINE_GRP_ID, POPULATE_RESET_GRP_ID, POPULATE_LY_PRO_VOL, POPULATE_FY_PRO_VOL, POPULATE_BLENDED_GRP_VOL, POPULATE_YTD_PRO_VOL, POPULATE_BLENDED_PERIOD_VOL — Helper routines that resolve grouping identifiers and compute prorated and blended volumes for prior-year, fiscal-year, and year-to-date scenarios.
• GET_CALC_PRD_SALES, GET_CALC_PRD_SALES_FOR, POPULATE_LY_PRO_SALES, POPULATE_FY_PRO_SALES, POPULATE_YTD_SALES, POPULATE_SALES, POPULATE_YTD_SALES_FOR — Sales aggregation routines that retrieve reported sales for the calculated period and derive prorated and cumulative sales figures used in rent determination.

Tables Accessed

The package operates against the PN variable rent schema primarily through APPS synonyms. PN_VAR_TRX_HEADERS_ALL and PN_VAR_TRX_DETAILS_ALL are the principal write targets, with the corresponding _S sequence-backed tables used for identifier generation. Header and detail processing is parameterised by PN_VAR_RENTS_ALL, PN_VAR_LINES_ALL, PN_VAR_PERIODS_ALL, and PN_VAR_GRP_DATES_ALL, which supply the lease, line, period, and grouping-date context. Breakpoint configuration is read from PN_VAR_BKPTS_HEAD_ALL, PN_VAR_BKPTS_DET_ALL, PN_VAR_BKHD_DEFAULTS_ALL, and PN_VAR_BKDT_DEFAULTS_ALL. Sales and volume history is sourced from PN_VAR_VOL_HIST_ALL, and adjustment logic draws on PN_VAR_DEDUCTIONS_ALL. DUAL is used for singleton calculations.

Usage Notes

PN_VAR_TRX_PKG is not intended as a public integration API; it is classified as OTHER and is primarily invoked internally. Typical call paths include the variable rent calculation concurrent programs and the Property Manager variable rent forms, both of which rely on POPULATE_TRANSACTIONS to generate header and detail records for active periods. Because four other packages reference it, customisations should treat it as an internal dependency: it is invoked whenever sales volumes are approved or periods are processed or reversed. Direct calls to INSERT_TRX_HDR from custom code require that grouping identifiers and proration factors already be resolved by the preceding POPULATE_* routines, since the procedure performs insertion only and delegates all derivation logic elsewhere.