Search Results get_tax_group

Overview

APPS.PN_R12_UTIL_PKG is a utility package within the Oracle Property Manager (PN) module of Oracle E-Business Suite, engineered to support the transition from pre-R12 to Release 12 tax and lease structures. Its source header ($Header: PNUTL12S.pls 120.7 2006/06/21 ... noship $) dates the shipped package to the early R12 development cycle, reflecting its role as a bridge utility for R12 tax engine (E-Business Tax / ZX) and lease classification logic. The package centralizes a collection of helper functions that resolve tax classification codes, tax codes, associated leases, and tax-party profiles required by Property Manager lease and payment-term processing. It is classified as OTHER in the ETRM metadata, meaning it is not a public product API but an internal support package referenced by fourteen other packages across the application.

In the Oracle EBS 12.1.1 and 12.2.2 environments, the package is registered under the APPS schema and remains a core dependency for Property Manager tax derivation used by payables-facing lease flows.

Key Procedures and Functions

The package exposes thirteen documented functions. Among these, the following are most frequently referenced by dependent code:

• GET_AP_TCC and GET_TCC_NAME — resolve Tax Classification Codes (TCC) and their display names for payment terms, factoring lease class code, org, and as-of date. These drive tax determination on lease payment terms.
• GET_AP_TAX_CODE_NAME — returns the tax code name associated with a given tax identifier, used to present readable tax labels to users and downstream processes. This is the function the user searched for.
• GET_AR_TAX_CODE_NAME — the receivables counterpart, resolving tax code names for AR-side tax identifiers.
• GET_TAX_GROUP — retrieves the tax group description for a supplied tax group identifier.
• VALIDATE_TERM_TEMPLATE_TAX — validates whether a payment term template is properly associated with tax setup for a lease class.
• IS_LE_COMPATIBLE — determines whether a legal entity is compatible with a given account, vendor site, payment term, template, or distribution, honoring the caller-supplied mode.
• IS_R12 — returns a boolean indicating whether the current environment operates under the R12 model, gating R12-specific logic across the module.
• GET_LE_FOR_AR and GET_LE_FOR_AP — derive the legal entity responsible for AR customer/transaction-type context and AP account/location context respectively.
• GET_TAX_FLAG — returns the tax flag indicating tax applicability for a vendor and vendor site.
• CHECK_TAX_UPGRADE — inspects whether tax classification or group data requires upgrade to the R12 tax model.

Tables Accessed

Via APPS synonyms, the package reads Property Manager transactional and setup tables including PN_PAYMENT_TERMS, PN_PAYMENT_TERMS_ALL, PN_TERM_TEMPLATES, PN_TERM_TEMPLATES_ALL, PN_LEASES, and PN_DISTRIBUTIONS. These provide payment terms, term template, lease classification, and distribution context. It also references the E-Business Tax tables ZX_ID_TCC_MAPPING, which maps tax regimes to tax classification codes, and ZX_PARTY_TAX_PROFILE, which stores party-level tax registration and configuration. The ZX tables underpin the tax code name resolution performed by GET_AP_TAX_CODE_NAME and related functions.

Usage Notes

PN_R12_UTIL_PKG is typically invoked indirectly through Oracle Property Manager forms, concurrent programs, and dependent PL/SQL packages rather than being called directly from user interfaces. Given its classification as OTHER and its noship header state, it is intended for internal consumption; customizations should treat the package as a private implementation detail and avoid hard-coded reliance on its signatures. In both 12.1.1 and 12.2.2, the package remains available in the APPS schema, and its functions such as GET_AP_TAX_CODE_NAME are useful for diagnostic SQL and reporting when a tax code name must be resolved from a stored tax identifier. Because the header is dated 2006 and the file revision is 120.7, the package has remained stable across the R12.x line, though callers should validate behavior against the current E-Business Tax configuration before relying on results in customized flows.