Results for “get_default_tax_classification”

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

Overview

ZX_TAX_DEFAULT_PKG is an E-Business Tax (EBTax / ETRM) utility package owned by APPS and classified as OTHER in the Oracle EBS 12.2.2 data model. Its central business function is tax classification defaulting. Rather than reimplement defaulting logic, the package acts as an application-aware wrapper that routes a request for a default tax classification code to the correct subledger API — Receivables (AR), Payables (AP), or Projects (PA) — based on the application identifier supplied by the caller. This allows a single, consistent entry point for derivation of tax classification codes across multiple transactional flows.

The package is of particular interest to integrations and diagnostics involving the event class PURCHASE_TRANSACTION_TAX_QUOTE. The shipped source header references Bug 4395918, which added explicit handling for the PURCHASE_TRANSACTION_TAX_QUOTE and SALES_TRANSACTION_TAX_QUOTE event classes, confirming that tax quoting for purchase (and sales) transactions is a first-class path within this wrapper.

Key Procedures and Functions

The documented public interface consists of a single procedure:

• GET_DEFAULT_TAX_CLASSIFICATION — The public wrapper procedure that obtains a default tax classification code for a given transaction context. It begins by initializing the standard EBS API return status and error buffer to a success baseline. It then applies conditional branching based on the incoming event class code and application identifier: when the event class is PURCHASE_TRANSACTION_TAX_QUOTE, or when the application belongs to the set (200, 201, 230, 401) and the event class is not SALES_TRANSACTION_TAX_QUOTE, the procedure follows the application-appropriate path. Depending on the application id, it dispatches to the corresponding Receivables, Payables, or Projects defaulting API for tax classification. The procedure receives a definition-information record structure (the def_tax_cls_code_info type from ZX_API_PUB) as an IN OUT parameter, together with standard return status and error buffer outputs, and is instrumented with FND_LOG calls at procedure, statement, and unexpected levels.

No other procedures or functions are documented for this package in the ETRM metadata; the remaining source comprises private constants and cursor declarations supporting this single entry point.

Tables Accessed

The only documented table reference is via an APPS synonym:

• RA_CUST_TRX_TYPES_ALL — Read by the private cursor get_tax_calc_flag, which selects the tax_calculation_flag column for a given organization id and receivables transaction type id. This lookup determines whether tax calculation is enabled for the transaction type before defaulting proceeds, thereby gating the AR-related defaulting path.

All other application data access is delegated to the downstream AR, AP, and PA defaulting APIs invoked by the wrapper.

Usage Notes

ZX_TAX_DEFAULT_PKG is an internal ETRM component rather than an end-user-facing program. It is typically invoked indirectly: E-Business Tax and subledger forms, tax engines, and tax quoting flows call it when a default tax classification is required for a transaction line. The documented reference count of four dependent packages indicates that it is consumed by other PL/SQL APIs within the tax and subledger stack, most plausibly during tax determination for purchase and sales transaction tax quotes and during invoice and credit memo entry.

For custom development, the package should be called only through its documented signature, supplying a populated ZX_API_PUB def_tax_cls_code_info record and inspecting the returned status and error buffer using the standard FND_API convention. Direct calls are appropriate in custom concurrent programs and extensions that must replicate standard tax classification defaulting behavior; bypassing the wrapper to call subledger APIs directly risks divergence from the shipped PURCHASE_TRANSACTION_TAX_QUOTE handling. The package is present in both 12.1.1 and 12.2.2; the documented header version (120.14) predates 12.2 and remains the functional basis in later releases. As with all seeded ETRM code, it should not be modified, and any wrapper behavior should be extended through supported APIs or customization layers.