Search Results pn_term_templates_all




Overview
Explore in AI Chat

Overview

The PN_TERM_TEMPLATES_ALL table is a core data object within Oracle E-Business Suite (EBS) Property Manager (PN) module, versions 12.1.1 and 12.2.2. It functions as a master repository for default payment and billing term templates. These templates define the standard financial conditions, such as payment schedules and billing frequencies, that can be consistently applied to leases, agreements, and other property management contracts. Its role is to centralize term definitions, enforce standardization, and streamline the configuration of recurring payment obligations across the portfolio, thereby reducing manual data entry and ensuring consistency in financial operations.

Key Information Stored

The table's primary identifier is the TERM_TEMPLATE_ID, which is enforced by the primary key constraint PN_TERM_TEMPLATES_PK. Critical foreign key columns establish the template's operational and organizational context. The SET_OF_BOOKS_ID links the template to a specific financial ledger via the GL_SETS_OF_BOOKS table, ensuring accounting integrity. Customer-centric columns—CUSTOMER_ID, CUSTOMER_SITE_USE_ID, and CUST_SHIP_SITE_ID—reference tables in the Trading Community Architecture (HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL) to associate templates with specific customers and their bill-to or ship-to locations. While the provided metadata specifies the columns that store these relationships, the exact descriptive attributes of the template (e.g., name, frequency, calculation method) are stored within the table but are not detailed in the excerpt.

Common Use Cases and Queries

A primary use case is the generation of reports to audit which term templates are assigned to active leases or agreements. Administrators often query this table to identify templates by customer or set of books before applying them to new contracts. A typical SQL pattern involves joining PN_TERM_TEMPLATES_ALL with related transaction tables. For example, to list all variable rent agreements using a specific template, one might execute:

  • SELECT ptta.term_template_id, pvra.var_rent_id, pvra.agreement_name FROM pn_term_templates_all ptta JOIN pn_var_rents_all pvra ON ptta.term_template_id = pvra.term_template_id WHERE ptta.customer_id = :cust_id;

Another common operational query is to validate template setup by checking for templates missing critical linkages, such as a defined set of books.

Related Objects

As indicated by its extensive foreign key relationships, PN_TERM_TEMPLATES_ALL is a central reference point for numerous transactional tables in Property Manager. Key dependent objects include: