Results for “pn_var_bkpts_head_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_VAR_BKPTS_HEAD_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, defined within the PN – Property Manager product. Its documented purpose is to serve as a form view used to input breakpoint header information, meaning it functions as the data source layer behind an Oracle Forms-based maintenance screen rather than as an independent reporting entity. The view presents a single row per breakpoint header record, joined against period and line context, and exposes both the descriptive attributes of a breakpoint definition and the standard Oracle who-columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus the ORG_ID operating unit discriminator. In 12.1.1 and 12.2.2 the view is delivered as VALID in a standard installation. Because it consolidates breakpoint header data with its parent period and line, it is frequently reached by report and integration developers who need to resolve the BASE_RENT and breakpoint characteristics for a variable rent (percentage rent or natural breakpoint) calculation without navigating multiple underlying tables.

Underlying Base Objects

The documented view text defines PN_VAR_BKPTS_HEAD_V as a three-table join. The driving table is PN_VAR_BKPTS_HEAD (referenced through a synonym), which holds the breakpoint header rows and supplies every column apart from the period and line keys returned by the join. PN_VAR_PERIODS_ALL supplies the PERIOD_ID side of the join, and PN_VAR_LINES_ALL supplies the LINE_ITEM_ID side. The join condition is PER.PERIOD_ID = BKHEAD.PERIOD_ID AND LINES.LINE_ITEM_ID = BKHEAD.LINE_ITEM_ID, so a breakpoint header is only returned when a matching period and line record both exist. Note that the select list aliases the driving table as BKHEAD and emits ROWID AS ROW_ID, giving the view the row identifier that Oracle Forms requires for updatable blocks. Documented dependent objects associated with the view include FND_GLOBAL (package), FND_LOOKUPS (view), PN_VAR_BKPTS_HEAD (synonym) and PN_VAR_RENT_DATES_ALL (synonym); the FND_LOOKUPS and FND_GLOBAL references typically support flexfield or lookup validation displayed alongside the header in the form, while PN_VAR_RENT_DATES_ALL relates to the rent date intervals that a breakpoint header ultimately drives.

Key Columns

• BKPT_HEADER_ID – Primary key of the breakpoint header row in PN_VAR_BKPTS_HEAD.
• LINE_ITEM_ID and PERIOD_ID – Foreign keys linking the header to its variable rent line and period.
• BASE_RENT – The base rent amount used as the threshold or reference figure for the breakpoint calculation; this is the column most often sought when users search on "base_rent".
• BASE_RENT_TYPE – Classifies how base rent is interpreted (for example fixed or per-unit-of-area), driving the arithmetic applied to the breakpoint.
• BREAK_TYPE and BREAKPOINT_TYPE – Distinguish natural versus artificial breakpoints and the associated calculation method.
• NATURAL_BREAK_RATE – The rate at which base rent is recovered before overage participation begins.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield segments for client-specific breakpoint attributes.
• ORG_ID – Operating unit identifier, enabling multi-org secured access.
• ROW_ID – ROWID of the underlying header row, used by Oracle Forms for block updates.

Common Use Cases and Queries

Typical scenarios include auditing base rent values across a portfolio, verifying breakpoint setup before running percentage rent, and building ad hoc extracts for lease administration reconciliation. Because the view is designed for form input, it is not secured by a MOAC policy in the same manner as many reporting views; queries should therefore filter explicitly on ORG_ID.

A representative query retrieves breakpoint headers for a given line and period:

• SELECT bkpt_header_id, line_item_id, period_id, base_rent, base_rent_type, natural_break_rate, org_id FROM apps.pn_var_bkpts_head_v WHERE line_item_id = :p_line_item_id AND org_id = :p_org_id;
• SELECT base_rent_type, base_rent, break_type, breakpoint_type FROM apps.pn_var_bkpts_head_v WHERE natural_break_rate IS NOT NULL AND org_id = :p_org_id ORDER BY base_rent DESC;
• SELECT bkpt_header_id, base_rent, attribute1, attribute_category FROM apps.pn_var_bkpts_head_v WHERE period_id = :p_period_id AND attribute_category IS NOT NULL;

Given the join to PN_VAR_PERIODS_ALL and PN_VAR_LINES_ALL, the view returns only headers with a valid parent period and line; orphaned header rows must be investigated directly in PN_VAR_BKPTS_HEAD rather than through the view.