Results for “schedule_day”

50+ results




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

Overview

PN_TERM_TEMPLATES_ALL is a Property Manager (PN) table in Oracle EBS 12.1.1 and 12.2.2 that stores default payment and billing term details. It serves as the master repository from which term templates are defined and then applied to lease payment terms, distributions, variable rents, and other financial constructs within the Property Manager module. Because the table defines defaults for how a lease or agreement will be billed and paid, it is foundational to lease financial setup and scheduling.

The table is owned by the PN schema and is documented as VALID. It contains 59 columns and is uniquely identified by the primary key constraint PN_TERM_TEMPLATES_PK, defined on TERM_TEMPLATE_ID. Heuristically, the Data Vault classification for this table is a hub, since the primary key (TERM_TEMPLATE_ID) is referenced as a foreign key by many dependent tables while the table itself has relatively few outbound dependencies. This classification is a suggested modeling interpretation based on the foreign key structure rather than a documented attribute.

Key Information Stored

The table's central identifier is the surrogate primary key TERM_TEMPLATE_ID. Two unique indexes are documented: PN_TERM_TEMPLATES_U2 on TERM_TEMPLATE_ID and PN_TERM_TEMPLATES_U1 on NAME, making NAME a business-key candidate that users recognize in the application.

The most significant columns include:

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and 15 flexfield ATTRIBUTE columns with ATTRIBUTE_CATEGORY support auditing and extensibility. ORG_ID enables multi-organization access control.

Common Use Cases and Queries

Term templates are typically queried when configuring or troubleshooting lease billing, verifying payment defaults before generating payment terms, and reporting on active templates for a given ledger. A representative query retrieving active templates for a ledger follows:

  • SELECT term_template_id, name, currency_code, payment_term_type_code, active FROM pn_term_templates_all WHERE set_of_books_id = :p_sob_id AND active = 'Y';
  • Joining to PN_PAYMENT_TERMS_ALL on TERM_TEMPLATE_ID shows which payment terms derive from each template.
  • Reporting templates that feed variable rents through INCLUDE_IN_VAR_RENT and PN_VAR_RENTS_ALL.
  • Validating customer-facing defaults by joining to HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL.

Related Objects

The table participates in several foreign key relationships. It references GL_SETS_OF_BOOKS_11I via SET_OF_BOOKS_ID, HZ_CUST_ACCOUNTS via CUSTOMER_ID, HZ_CUST_SITE_USES_ALL via CUSTOMER_SITE_USE_ID and CUST_SHIP_SITE_ID, RA_CUST_TRX_TYPES_ALL via CUST_TRX_TYPE_ID, MTL_INV_PICKING_RULES via INV_RULE_ID, PO_RULE_EXPENSE_ACCOUNTS via ACCOUNT_RULE_ID, and AR_RECEIPT_METHODS via RECEIPT_METHOD_ID. Numerous dependent tables reference TERM_TEMPLATE_ID, notably PN_DISTRIBUTIONS_ALL, PN_PAYMENT_TERMS_ALL, PN_VAR_RENTS_ALL, PN_REC_AGREEMENTS_ALL, PN_INDEX_LEASES_ALL, PN_LEASE_DETAILS_ALL, and PN_VAR_TEMPLATES_ALL.