Results for “bkpt_update_flag”

50+ results




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

Overview

PN_VAR_LINES_ALL is a Property Manager (PN) transaction table in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It stores the individual line items that belong to each variable rent period. In the Property Manager rent model, a variable rent captures rent calculated from actual sales, volumes, or other variable performance measures rather than a fixed contractual amount. Each such rent is decomposed into periods, and each period is further decomposed into lines; PN_VAR_LINES_ALL holds that lowest-level line detail, including the sales type, item category, and the template, default, and rent associations from which the line was generated.

The table is owned by the PN schema and contains 34 documented columns in the 12.2.2 physical schema. Its primary key, PN_VAR_LINES_PK, is defined on LINE_ITEM_ID, and a unique index PN_VAR_LINES_U1 also covers LINE_ITEM_ID, which identifies the surrogate key column as the table's business-key candidate from a documented-constraint perspective. From a Data Vault modeling standpoint, the FK topology suggests a hub-leaning classification: the table carries its own durable identity (LINE_ITEM_ID) and serves as the referenced parent for several dependent variable-rent child tables, while also holding descriptive and foreign-key attributes typical of a hub with attached reference context.

Key Information Stored

The most operationally significant columns documented for this table are:

  • LINE_ITEM_ID — Surrogate primary key and the unique business-key candidate; referenced by child tables throughout the variable rent model.
  • LINE_ITEM_NUM — User-facing line number used to sequence lines in reports and inquiries.
  • PERIOD_ID — Foreign key to PN_VAR_PERIODS_ALL, tying the line to a specific period of a variable rent.
  • VAR_RENT_ID — Foreign key to PN_VAR_RENTS_ALL, identifying the parent variable rent header.
  • LINE_TEMPLATE_ID — Reference to the line template that defines the line's structure or calculation basis.
  • AGREEMENT_TEMPLATE_ID — Reference to the agreement-level template that governs the variable rent arrangement.
  • LINE_DEFAULT_ID — Reference to the line default record supplying defaulted values for the line.
  • SALES_TYPE_CODE — Classifies the sales or volume basis used to evaluate the line.
  • ITEM_CATEGORY_CODE — Restricts or identifies the item category applicable to the line.
  • COMMENTS — Free-form descriptive text entered by the user.
  • ORG_ID — Operating unit identifier supporting multi-org access and reporting.
  • BKPT_UPDATE_FLAG — Breakpoint update indicator controlling downstream breakpoint processing.
  • SALES_VOL_UPDATE_FLAG — Sales and volume update indicator controlling refresh of variable measure data.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATION_DATE / CREATED_BY — Standard EBS audit columns identifying who created or last modified the line.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Flexfield descriptive columns available for extensible, client-specific data.

Common Use Cases and Queries

The table is most commonly accessed when reporting variable rent line detail, reconciling line items for a given period, or tracing a line to its associated breakpoints, deductions, volume history, and rent summaries. Typical query patterns join the table to its parent period and rent headers, for example:

  • Retrieving all lines for a period: SELECT * FROM PN_VAR_LINES_ALL WHERE PERIOD_ID = :period_id ORDER BY LINE_ITEM_NUM;
  • Listing lines for a variable rent: SELECT l.* FROM PN_VAR_LINES_ALL l WHERE l.VAR_RENT_ID = :var_rent_id;
  • Reporting lines with sales type and item category: SELECT LINE_ITEM_ID, LINE_ITEM_NUM, SALES_TYPE_CODE, ITEM_CATEGORY_CODE FROM PN_VAR_LINES_ALL WHERE ORG_ID = :org_id;
  • Identifying lines updated for breakpoint or volume processing: SELECT * FROM PN_VAR_LINES_ALL WHERE BKPT_UPDATE_FLAG = 'Y' OR SALES_VOL_UPDATE_FLAG = 'Y';

Because ORG_ID is stored on the row, all reporting queries should constrain by operating unit when run outside standard multi-org views.

Related Objects

The table participates in a closely integrated variable rent schema. Its most significant relationships are the following, with actual join columns:

Together these objects form the complete variable rent processing chain, from rent header through period, line, breakpoint, deduction, and volume history detail to summarized rent output.