Search Results ja_in_cust_default_taxes




Overview
Explore in AI Chat

Overview

JAI_CMN_TAX_DEFAULTATION_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that is part of the Oracle Financials for India (JAI) localization layer. Its business function is to resolve and apply default tax determination rules for Indian statutory taxation across the EBS sub-ledgers. Whenever a transaction is created or modified in Payables, Receivables, Purchasing, Order Management, Projects, or Inventory, the localization must decide which tax categories, tax types, and threshold tax rates apply to the document line before tax can be calculated and posted. This package centralizes that defaulting logic: it inspects the party context (customer, vendor, or operating unit/inventory organization), locates the tax categories and taxes effective for that context, and returns the default tax values that downstream tax engines consume. The package is registered in the ETRM repository with an API classification of OTHER, indicating it is an internal helper package rather than a formally published public API, although it is heavily reused by other JAI packages. Its status is VALID in both the 12.1.1 and 12.2.2 reference environments.

Key Procedures and Functions

The documented program units are as follows. No parameter lists are reproduced here because none are published in the metadata.

  • JA_IN_CUST_DEFAULT_TAXES — Derives default tax values for a customer context, typically by inspecting the customer's bill-to or ship-to site and returning the applicable tax categories and taxes.
  • JA_IN_VENDOR_DEFAULT_TAXES — Performs the equivalent defaulting for a supplier and supplier site, including withholding/threshold tax applicability relevant to Indian TDS requirements.
  • JA_IN_ORG_DEFAULT_TAXES — Resolves defaults based on the operating unit or inventory organization, which governs which tax regime and tax registration apply to the transaction.
  • JA_IN_CALC_PREC_TAXES — Computes or prepares default taxes that must be applied before the main tax calculation step, establishing precedence among multiple candidate taxes.
  • GET_TAX_CAT_TAXES_CUR — Retrieves the set of taxes associated with a given tax category for the current effective context, returning the tax list used by callers for defaulting.
  • IS — A token entry that in ETRM listings often denotes the package specification/initialization or an internal validity check rather than a callable business procedure; it should be treated as an internal artifact.

Tables Accessed

The package reads and writes the core Indian tax configuration and transaction tables through APPS synonyms. JAI_CMN_TAXES_ALL holds the master tax definitions; JAI_CMN_TAX_CTGS_ALL and JAI_CMN_TAX_CTG_LINES hold tax categories and their constituent lines. JAI_CMN_DOCUMENT_TAXES and its sequence-backed sibling JAI_CMN_DOCUMENT_TAXES_S store the taxes attached to a specific document, which is the primary output of defaulting. JAI_AP_TDS_THHOLD_TAXES and JAI_AP_TDS_INV_TAXES support withholding tax determination. JAI_CMN_CUS_ADDRESSES and JAI_CMN_VENDOR_SITES provide the party address context, while HZ_CUST_SITE_USES_ALL supplies customer site usage information. PO_REQUISITION_LINES_ALL is referenced for purchasing-side defaulting. Receivables and other sub-ledger transaction data appear through JAI_AR_TRXS, JAI_AR_TRX_TAX_LINES, and JAI_BOE_DETAIL_TAXES (with JAI_BOE_DETAIL_TAXES_S).

Usage Notes

JAI_CMN_TAX_DEFAULTATION_PKG is an internal dependency rather than a user-facing entry point. It is invoked programmatically by higher-level JAI packages, including JAI_AP_STND_TAX_PROCESS, JAI_AR_RCTA_TRIGGER_PKG, JAI_AR_RCTLA_TRIGGER_PKG, JAI_CMN_MTAX_PKG, JAI_MTL_TRXS_PKG, JAI_OE_OLA_TRIGGER_PKG, JAI_PA_TAX_PKG, JAI_PO_RLA_TRIGGER_PKG, JAI_PO_TAX_PKG, and JAI_RGM_THHOLD_PROC_PKG, and it is referenced by seventeen packages in total. Customizations should not call it directly unless the calling contract of these JAI packages is fully understood; upgrades of the India localization may change its internal behavior. Custom code that must be touched should be validated against the dependent packages listed above.