Search Results pn_payment_frequency_type




Overview

APPS.PN_VAR_BKPTS_HEAD_V is a reporting and inquiry view in Oracle E-Business Suite Property Manager (PN), the ETRM module responsible for managing real estate leases, variable rent, and breakpoints. The view exposes the breakpoint header definition for variable rent schedules together with the reporting frequency of the underlying variable rent record. It is defined over PN_VAR_BKPTS_HEAD, PN_VAR_RENT_DATES_ALL, and FND_LOOKUPS, producing a denormalized result set that joins each breakpoint header to its parent variable rent date record and resolves the reporting frequency code to a user-facing meaning. Because it is owned by APPS and defined as a view (not a table), it is read-only and intended for reporting, concurrent-program queries, Oracle Forms LOVs, and integration extracts rather than for transactional DML. The view is available in both EBS 12.1.1 and 12.2.2; the documented metadata reflects the 12.2.2 ETRM definition.

Underlying Base Objects

The documented base objects and their roles are:

  • PN_VAR_BKPTS_HEAD (synonym) — The primary breakpoint header table, aliased bkhead in the view text. It supplies the breakpoint header identifier, break type, base rent attributes, natural break rate, breakpoint type, descriptive flexfield columns, and the ORG_ID operating unit column.
  • PN_VAR_RENT_DATES_ALL (synonym) — The variable rent dates table, aliased dat. It is joined to the breakpoint header on VAR_RENT_ID and contributes REPTG_FREQ_CODE, which is projected as frequency_code.
  • FND_LOOKUPS (view) — The standard Oracle Application Object Library lookup view, aliased fnd1. It is joined with outer-join syntax on lookup_type = 'PN_PAYMENT_FREQUENCY_TYPE' and lookup_code = dat.reptg_freq_code to resolve the meaning of the reporting frequency, projected as frequency.
  • FND_GLOBAL (package) — Not referenced in the visible SELECT text but documented as a base object; FND_GLOBAL supplies session context (user, responsibility, org) used by multi-org and security predicates applied to the view.

Key Columns

Common Use Cases and Queries

The view is typically used to report breakpoint definitions alongside their variable rent reporting frequency, for reconciliation of variable rent schedules, and for building LOVs or extracts that require the lookup meaning rather than the raw code.

  • Listing all breakpoint headers for a line item: SELECT bkpt_header_id, line_item_id, period_id, break_type, breakpoint_type, base_rent FROM apps.pn_var_bkpts_head_v WHERE line_item_id = :line_item_id;
  • Resolving breakpoints by frequency meaning: SELECT bkpt_header_id, var_rent_id, frequency_code, frequency FROM apps.pn_var_bkpts_head_v WHERE frequency = 'Monthly';
  • Org-scoped extract: SELECT bkpt_header_id, org_id, bkhd_start_date, bkhd_end_date FROM apps.pn_var_bkpts_head_v WHERE org_id = :org_id;

Because the join to FND_LOOKUPS is an outer join, records whose reporting frequency code has no matching lookup value are still returned with a null frequency; queries filtering on translated meanings should account for this.