Search Results pn_term_templates




Overview
Explore in AI Chat

Overview

APPS.PN_R12_UTIL_PKG is a utility package body in the Oracle Property Manager (PN) module. Its purpose is to provide shared helper logic that supports the module's transition to and operation under the Oracle E-Business Tax (EBTax) architecture introduced in Release 12. The package centralizes repetitive lookups and validation routines that other Property Manager packages, concurrent programs, and forms would otherwise duplicate, particularly around tax classification codes, tax regimes, and legal entity resolution.

The dependency list confirms a Release 12 orientation. References to MO_GLOBAL, XLE_BUSINESSINFO_GRP, ZX_ID_TCC_MAPPING, ZX_PARTY_TAX_PROFILE, and the ZX input/output classification views place the package firmly within the EBTax and Subledger Accounting framework rather than the legacy 11i tax engine. The IS_R12 function provides an explicit runtime switch, allowing callers to branch behaviour between Release 11i and Release 12 code paths, which is characteristic of upgrade-spanning utility code shipped with the R12 family.

Key Procedures and Functions

The package exposes thirteen documented program units, grouped by function:

  • GET_TCC and GET_TCC_NAME — Retrieve a Tax Classification Code and its descriptive name, reading from ZX_ID_TCC_MAPPING, which maps transaction identifiers to tax classification codes. These are the primary accessors used by lease and payment-term logic that must stamp a tax classification code onto a transaction.
  • VALIDATE_TERM_TEMPLATE_TAX — Validates that the tax setup associated with a payment term template is consistent and usable. This is the routine most directly implicated by the search term pn_term_templates, since it is the link between the PN_TERM_TEMPLATES tables and the EBTax configuration.
  • IS_LE_COMPATIBLE and IS_R12 — Boolean-style capability checks. IS_R12 reports whether the installation is running Release 12 or later; IS_LE_COMPATIBLE reports whether the current legal entity configuration is compatible with the calling code path.
  • GET_LE_FOR_AR and GET_LE_FOR_AP — Resolve the appropriate legal entity for a receivable or payable transaction respectively, consulting XLE_BUSINESSINFO_GRP and related legal entity sources.
  • GET_TAX_FLAG — Returns the tax indicator applicable to a given entity or transaction context.
  • GET_AP_TAX_CODE_NAME and GET_AR_TAX_CODE_NAME — Return the display name of the payables or receivables tax code, drawn from the ZX classification views so that Property Manager can present consistent tax code descriptions.
  • GET_TAX_GROUP — Retrieves the tax group associated with a party tax profile, used to select the correct tax determination rules.
  • CHECK_TAX_UPGRADE — Determines whether tax-related upgrade processing has completed, guarding code that must not execute against partially migrated data.

Tables Accessed

The package reads and, where applicable, writes the following documented tables through APPS synonyms:

  • PN_TERM_TEMPLATES and PN_TERM_TEMPLATES_ALL — Payment term templates and their multi-org (ALL) counterparts; inspected by VALIDATE_TERM_TEMPLATE_TAX.
  • PN_PAYMENT_TERMS and PN_PAYMENT_TERMS_ALL — Payment terms definitions and their multi-org counterparts, used when resolving term-level tax attributes.
  • PN_LEASES and PN_DISTRIBUTIONS — Lease headers and their accounting distributions, which carry the tax classification codes the utility resolves.
  • ZX_ID_TCC_MAPPING — The EBTax mapping of transaction identifiers to tax classification codes.
  • ZX_PARTY_TAX_PROFILE — Party-level tax configuration, read by GET_TAX_GROUP and related lookups.
  • PO_VENDORS and PO_VENDOR_SITES_ALL — Supplier and supplier site records, consulted during legal entity and tax profile resolution for payables-side processing.

Additional dependencies include MO_GLOBAL for multi-org context, XLE_BUSINESSINFO_GRP for legal entity information, and the ZX input/output classification views.

Usage Notes

PN_R12_UTIL_PKG is not an end-user-callable API. It is invoked internally by other Property Manager packages — the ETRM metadata records it as referenced by fourteen other database objects — and by concurrent programs, forms, and OAF pages during lease creation, payment term maintenance, and tax defaulting. Because it has no documented inbound public API contract and no dependents outside APPS, customizations should not call it directly; instead, custom code should rely on the supported Property Manager APIs, which in turn delegate to these utilities. The IS_R12 check makes the package safe to ship into environments mid-upgrade, but implementations should verify CHECK_TAX_UPGRADE returns a completed status before depending on tax classification results.