Results for “negative_rent”

50+ results




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

Overview

PN_VAR_TEMPLATES_ALL is a Property Manager (PN) table in Oracle E-Business Suite that stores template definitions containing default values for variable rent agreements. Variable rent agreements are used in lease and property management scenarios where rent is calculated from periodic sales, usage, or other variable performance measures rather than a fixed schedule. The template record acts as a reusable blueprint: it carries default reporting and invoicing parameters, term associations, and behavioral flags that are copied or referenced when variable rent lines are created for a lease.

The table is owned by the PN schema and is documented as VALID in ETRM 12.2.2, with a physical schema of 46 columns. Its primary key is PN_VAR_TEMPLATES_PK on AGREEMENT_TEMPLATE_ID, and a unique index PN_VAR_TEMPLATES_U1 also exists on AGREEMENT_TEMPLATE_ID. In Data Vault terms, the heuristic classification is hub-leaning: AGREEMENT_TEMPLATE_ID functions as a durable business key, while the descriptive columns (purpose, frequencies, proration rules, and so on) behave like satellite attributes. Modelers may therefore treat this object as a hub with an associated satellite rather than as a transactional fact or link.

Key Information Stored

The surrogate and unique key is AGREEMENT_TEMPLATE_ID, which uniquely identifies each variable rent template. AGREEMENT_TEMPLATE holds the user-visible template name or identifier. TYPE_CODE and PURPOSE_CODE classify the template and its intended use. TERM_TEMPLATE_ID is a foreign key to PN_TERM_TEMPLATES_ALL, linking the variable rent template to the term template that governs its validity period.

Financial and behavioral defaults include CUMULATIVE_VOL, INVOICE_ON, NEGATIVE_RENT, and ABATEMENT_AMOUNT, which control cumulative volume treatment, invoicing triggers, negative rent handling, and abatement offsets. PRORATION_RULE defines how partial-period amounts are prorated.

Reporting and invoicing cadence is controlled by a cluster of scheduling columns: VRG_REPTG_FREQ_CODE, REPTG_FREQ_CODE, REPTG_DAY_OF_MONTH, REPTG_DAYS_AFTER, INVG_FREQ_CODE, INVG_SPREAD_CODE, INVG_DAY_OF_MONTH, and INVG_DAYS_AFTER. Calendar and period handling rely on USE_GL_CALENDAR, YEAR_START_DATE, GL_PERIOD_SET_NAME, PERIOD_TYPE, and PERIOD_FREQ_CODE. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the ORG_ID multi-tenant discriminator are also present, along with fifteen ATTRIBUTE flex columns and COMMENTS.

Common Use Cases and Queries

A frequent requirement is to list all active variable rent templates with their reporting and invoicing frequency for configuration review:

  • SELECT agreement_template_id, agreement_template, type_code, purpose_code, reptg_freq_code, invg_freq_code FROM pn_var_templates_all WHERE org_id = :org_id ORDER BY agreement_template;
  • Join to term templates to confirm validity: SELECT v.agreement_template, t.* FROM pn_var_templates_all v, pn_term_templates_all t WHERE v.term_template_id = t.term_template_id;
  • Identify templates using the GL calendar for period-based reporting: SELECT agreement_template_id, gl_period_set_name, period_type FROM pn_var_templates_all WHERE use_gl_calendar = 'Y';
  • Find templates referenced by variable rent lines to trace usage: SELECT l.*, v.agreement_template FROM pn_var_lines_all l, pn_var_templates_all v WHERE l.agreement_template_id = v.agreement_template_id;

These queries support lease setup validation, reporting-frequency audits, and impact analysis before changing a shared template.

Related Objects

PN_VAR_TEMPLATES_ALL sits at the center of a family of Property Manager variable rent objects that reference it through AGREEMENT_TEMPLATE_ID:

Together these form the variable rent configuration and transaction model, with PN_VAR_TEMPLATES_ALL serving as the master definition from which line, constraint, and default records inherit their parameters.