Search Results agreement_template_id

Overview

The PN_VAR_TEMPLATES_ALL table is a core data repository within the Oracle E-Business Suite (EBS) Property Manager (PN) module. It serves a critical administrative function by storing master templates that define default values and structures for variable rent agreements. These templates streamline the creation of complex rental contracts where the payment amount is not fixed but varies based on predefined formulas, such as a percentage of sales or changes in an index. By centralizing common agreement parameters, the table enforces standardization, reduces manual data entry errors, and accelerates the leasing process across the enterprise's property portfolio.

Key Information Stored

The table's primary purpose is to hold the unique identifier and descriptive attributes for each variable rent template. The documented primary key column, AGREEMENT_TEMPLATE_ID, uniquely identifies each template record. While the full column list is not detailed in the provided metadata, such a table typically stores columns for the template name, a description, an effective start and end date, and a set of default values for key agreement terms. These defaults likely include parameters for calculation frequency, base rent percentages, escalation clauses, and recovery types. The "_ALL" suffix in the table name is a standard EBS convention indicating the table is partitioned by a multi-organization access control (MOAC) security identifier, such as ORG_ID, enabling it to store data for multiple operating units.

Common Use Cases and Queries

The primary use case is the rapid generation of new variable rent agreements. When a property manager creates an agreement, they can select a template from this table to pre-populate its terms. For reporting and administration, common queries involve listing available templates or auditing their usage. A basic SQL pattern to retrieve all active templates for a specific operating unit would be:

• SELECT agreement_template_id, template_name, description FROM pn_var_templates_all WHERE sysdate BETWEEN start_date AND NVL(end_date, sysdate) AND org_id = :org_id;

Another critical use case is identifying which specific variable rent agreements were created from a given template, which requires joining to child agreement tables using the AGREEMENT_TEMPLATE_ID as a foreign key.

Related Objects

As the source of default values, PN_VAR_TEMPLATES_ALL has a direct parent-child relationship with tables that store the actual variable rent agreements. The documented primary key (AGREEMENT_TEMPLATE_ID) will be referenced as a foreign key in these agreement tables. The most significant related object is likely the PN_VAR_AGREEMENTS_ALL table, which stores the executed variable rent agreements. The join between these tables would typically be on the AGREEMENT_TEMPLATE_ID column. Other related objects may include views that consolidate template and agreement data for reporting, such as PN_VAR_AGREEMENTS_V, and the PL/SQL APIs in the PN_VAR_RENT_PVT package that likely contain procedures for validating and applying template data during agreement creation.