Results for “pop_def_tax_classif_code”

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

Overview

The APPS.ZX_VALIDATE_API_PKG package is a core component of the Oracle E-Business Tax (EBTax) engine, delivered with Oracle EBS 12.1.1 and 12.2.2. Its primary business function is to default and validate tax attributes for transaction lines before the tax calculation engine (ZX) determines applicable tax regimes, taxes, rates, and jurisdictions. When transactional data flows into EBTax from source applications such as Order Management, Receivables, Payables, and Purchasing, not all tax-determining attributes are known or populated. This package resolves that gap by applying hierarchical defaults and then validating the resulting attribute set against the tax configuration repository.

The package operates against the global temporary tables ZX_TRANSACTION_LINES_GT, ZX_TRX_HEADERS_GT, and ZX_IMPORT_TAX_LINES_GT, which act as the staging interface between calling applications and the tax engine. A distinctive feature of the package is its extensive use of PL/SQL collection types (index-by tables) mirroring columns of these GT tables — for example trx_line_id_tbl, product_id_tbl, account_ccid_tbl, and ship_to_location_id_tbl — enabling bulk processing of transaction lines in a single invocation rather than row-by-row calls.

Key Procedures and Functions

• DEFAULT_AND_VALIDATE_TAX_ATTR — The principal entry point. It performs defaulting and validation of tax attributes in a single call, sequencing the internal logic so that defaults are applied first and the resulting attribute set is then validated before tax determination proceeds.
• DEFAULT_TAX_ATTR — Populates tax-determining attributes that are missing or null on the transaction line or header. Defaulting relies on configuration hierarchies such as country defaults, party tax profiles, and event class mappings.
• VALIDATE_TAX_ATTR — Verifies that the defaulted and supplied attributes are internally consistent and valid with respect to the tax configuration, flagging errors that would otherwise cause tax calculation failure.
• POP_DEF_TAX_CLASSIF_CODE — Populates the default tax classification code for a transaction line. The tax classification code is a key determinant in identifying the applicable tax regime and tax, and this routine derives the default from the configuration tables based on the ship-to, ship-from, product, and party context. This is the procedure referenced by users searching for pop_def_tax_classif_code.

Tables Accessed

The package reads and writes the staging GT tables ZX_TRANSACTION_LINES_GT, ZX_TRX_HEADERS_GT, and ZX_IMPORT_TAX_LINES_GT. Configuration and reference data are read from FND_TERRITORIES, XLE_ENTITY_PROFILES, XLE_ETB_PROFILES (legal entity and establishment), ZX_EVNT_CLS_MAPPINGS (event class to tax regime/tax mapping), ZX_FC_CODES_B, ZX_FC_TYPES_B, and ZX_FC_COUNTRY_DEFAULTS (tax classification codes, types, and country-level defaults), ZX_JURISDICTIONS_B, ZX_PARTY_TAX_PROFILE, and ZX_RATES_B. Calculated tax lines and their determining factors are handled through ZX_LINES and ZX_LINES_DET_FACTORS. Collectively these tables supply the geographic, party, product, and classification context required for defaulting and validation.

Usage Notes

ZX_VALIDATE_API_PKG is invoked internally by the EBTax application programming interface layer, typically during the tax determination phase of transactions originating in Order Management, Receivables, Payables, Purchasing, and other source modules. It is also callable from custom PL/SQL integrations that populate the ZX global temporary tables directly prior to invoking the tax engine. Because the package is declared AUTHID CURRENT_USER, execution privileges and any unqualified object resolution follow the invoking schema. Developers should note the header version (120.9) and confirm behavior against the specific patch level of their 12.1.1 or 12.2.2 instance. It is referenced by one other package within the tax engine. Customizations should avoid direct modification; extensions should instead leverage the supported ZX public APIs that ultimately call this package.