Results for “agreement_template_id”

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

Overview

PN_VAR_LINE_TEMPLATES_ALL is a Property Manager (PN) transactional table in Oracle EBS 12.1.1 and 12.2.2 that stores line-level setup information for variable rent, segmented by organization. Variable rent arrangements allow property managers to define rent calculations based on sales volume, thresholds, or other variable measures rather than fixed amounts. This table functions as the template-level definition layer within that framework, holding the reusable line specifications that are subsequently applied to actual variable rent agreements and defaulted into downstream processing records.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is identified as a standalone entity. In dimensional modeling terms, it behaves as a configuration or reference entity rather than a transactional fact: it is referenced by dependent default and booking-header tables but does not itself act as a junction linking multiple hubs. The table is org-striped, as indicated by the ORG_ID column and the _ALL suffix, meaning rows are partitioned by operating unit or organization and are subject to Multi-Org access control.

Key Information Stored

The surrogate primary key is LINE_TEMPLATE_ID, enforced by the PN_VAR_LINE_TEMPLATES_PK constraint. A second unique index, PN_VAR_LINES_TMPLATE_U1, also covers LINE_TEMPLATE_ID. Most business content is carried by the following columns:

• LINE_TEMPLATE_ID — surrogate primary key uniquely identifying each variable rent line template record.
• AGREEMENT_TEMPLATE_ID — foreign key to PN_VAR_TEMPLATES_ALL, tying the line to its parent variable rent agreement template.
• LINE_DETAIL_NUM — sequence or detail number ordering lines within a template.
• SALES_TYPE_CODE — classifies the sales or revenue category against which the variable rent line is evaluated.
• ITEM_CATEGORY_CODE — restricts the line to a specific item category for sales-based rent calculations.
• ORG_ID — the operating unit or organization owning the template line, enabling Multi-Org partitioning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle flexfield descriptive columns providing extensibility for client-specific line attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Who columns providing audit and concurrency tracking.

Common Use Cases and Queries

Typical usage centers on validating template configuration, replicating setups across organizations, and reporting variable rent line definitions prior to agreement generation. A standard retrieval joins the parent template to present complete line context:

• Configuration review: SELECT LINE_TEMPLATE_ID, LINE_DETAIL_NUM, SALES_TYPE_CODE, ITEM_CATEGORY_CODE FROM PN_VAR_LINE_TEMPLATES_ALL WHERE AGREEMENT_TEMPLATE_ID = :template_id AND ORG_ID = :org_id ORDER BY LINE_DETAIL_NUM;
• Organization comparison: query the same AGREEMENT_TEMPLATE_ID across multiple ORG_ID values to identify missing or divergent line setups.
• Referential integrity audit: left-join to PN_VAR_LINE_DEFAULTS_ALL to find template lines that are never referenced by a default record.
• Migration and cloning: extract line rows for an operating unit and insert into a target ORG_ID, adjusting LINE_TEMPLATE_ID to a fresh sequence value.

Related Objects

The table participates in a well-defined relationship graph:

• PN_VAR_TEMPLATES_ALL — parent table referenced via PN_VAR_LINE_TEMPLATES_ALL.AGREEMENT_TEMPLATE_ID.
• PN_VAR_LINES_ALL — variable rent lines that reference this template through LINE_TEMPLATE_ID.
• PN_VAR_LINE_DEFAULTS_ALL — default line records referencing this table via LINE_TEMPLATE_ID.
• PN_VAR_BKHD_DEFAULTS_ALL — booking-header defaults that also reference this table via LINE_TEMPLATE_ID.
• PN_VAR_LINE_TEMPLATES_PK / PN_VAR_LINES_TMPLATE_U1 — the primary key and unique index that enforce identity and support efficient lookups on LINE_TEMPLATE_ID.

Because ORG_ID governs visibility, all queries and API calls should respect the active organization context through MOAC initialization.