Search Results initialize_lte

Overview

ZX_TCM_CONTROL_PKG is a core Tax Calculation and Maintenance (TCM) engine component within the Oracle E-Business Suite ETRM (E-Business Tax) module, owned by the APPS schema. It is declared AUTHID CURRENT_USER, meaning that execution privileges are resolved against the calling user's schema rather than the package owner. The package encapsulates the controlling logic that drives fiscal classification, tax registration lookup, and tax determination for transactions processed through the E-Business Tax engine. In effect, it acts as the orchestration layer between transaction lines and the underlying tax configuration data stored in the ZX tables. Because it is referenced by eight other packages, it functions as a shared internal service library rather than a standalone user-facing API. Its principal value is performance optimization: several of its public routines are designed to populate in-memory PL/SQL caches so that repeated lookups against the database are avoided during high-volume tax calculation runs.

Key Procedures and Functions

• INITIALIZE_LTE — Initializes the tax engine session state, priming the internal caches used by the remaining routines in the package. It is the entry point that establishes the working context for subsequent classification and registration calls.
• GET_FISCAL_CLASSIFICATION — Resolves fiscal classification information for a transaction, returning data consistent with the zx_fiscal_class_info_rec record type. That record carries classification category and type codes, condition values, event class code, tax determination date, tax regime code, classified entity, application and item organization identifiers, effective dates, and the fsc_code field. The fsc_code column (ZX_CONDITIONS.ALPHANUMERIC_VALUE) is the fiscal classification code the user searched for.
• GET_PROD_TRX_CATE_VALUE — Retrieves product transaction category values used during tax determination, supporting the mapping between product fiscal classifications and transaction business categories.
• GET_TAX_REGISTRATION — Locates the applicable tax registration for a given party, regime, tax, and jurisdiction. The package comments note that true registrations are searched first, but during migration true registration records may not exist, so a negative (dummy) result is cached to prevent repeated futile database access per tax line.

Tables Accessed

• ZX_CONDITIONS, ZX_FC_TYPES_B, ZX_REGIMES_B, ZX_TAXES_B, ZX_JURISDICTIONS_B — tax configuration and classification setup; the fsc_code value originates in ZX_CONDITIONS.
• ZX_LINES and ZX_LINES_DET_FACTORS — transaction-level tax lines and their determining factors.
• ZX_PARTY_TAX_PROFILE and ZX_REGISTRATIONS — registration and party tax profile resolution, including the migration scenario described above.
• HZ_CUST_SITE_USES_ALL, AP_SUPPLIER_SITES_ALL — customer and supplier site context for determining the relevant registration.
• FND_ID_FLEX_STRUCTURES, FND_LOOKUP_VALUES, FND_PRODUCT_INSTALLATIONS, FND_LOG_MESSAGES — key flexfield structure resolution, lookup decoding, installation checking, and diagnostic logging.

Usage Notes

ZX_TCM_CONTROL_PKG is typically invoked indirectly. It is called by the higher-level E-Business Tax calculation packages (the eight referencing packages) during transaction processing, tax calculation on sales orders, invoices, and purchase orders, and during migration or data conversion routines. Custom code should not call the internal cache-population routines directly without first invoking INITIALIZE_LTE, as the caches and dummy-flag behavior described in the source expect that initialization. Because the package is AUTHID CURRENT_USER, any custom caller must hold execute privilege on the package as well as select privileges on the referenced ZX, HZ, AP, and FND objects through APPS synonyms.