Results for “ar_default_tax_code_v”

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

Overview

AR_DEFAULT_TAX_CODE_V is a Receivables view shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to implement the defaulting of Tax Codes from within Order Entry. In other words, the view does not itself store tax data; it is a resolution engine expressed as a SQL statement that derives the tax code that should apply to a given customer, site use, and inventory item combination, based on the tax defaulting rules configured in Oracle Receivables system parameters.

The view is relevant to any user searching for "sales_tax" because two of the driving parameters, TAX_METHOD and the various TAX_USE_* flags read from AR_SYSTEM_PARAMETERS, directly control whether the environment operates with Sales Tax (a location-based tax type) versus a VAT-style regime. The view is listed in the ETRM repository as "Not implemented in this database," meaning it is a seeded dictionary object and not a customer-created artifact.

Underlying Base Objects

The view text joins six base tables. HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES provide the customer account header and the account site, while HZ_CUST_SITE_USES supplies the site-use level record, including its SITE_USE_ID and any site-level TAX_CODE. MTL_SYSTEM_ITEMS supplies the inventory item and organization, including the item-level TAX_CODE. AR_VAT_TAX contributes the candidate tax code and its validity window (START_DATE, END_DATE) together with TAX_TYPE. AR_SYSTEM_PARAMETERS contributes the SET_OF_BOOKS_ID and the control flags and tax method that drive the decoding logic.

The join structure is: customer account to account site, account site to site use, and cross-joined against MTL_SYSTEM_ITEMS, AR_VAT_TAX, and AR_SYSTEM_PARAMETERS, with the final match on TAX_CODE determined by a deeply nested DECODE. No documented base objects were recorded in the ETRM metadata beyond the view definition itself.

Key Columns

• SITE_USE_ID — identifier of the customer site use; the key context for site-level defaulting.
• CUSTOMER_ID (CUST_ACCOUNT_ID) — the customer account for which the tax code is being resolved.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — the item and inventory organization, enabling product-level tax defaulting.
• SET_OF_BOOKS_ID — the ledger context sourced from AR_SYSTEM_PARAMETERS.
• START_DATE and END_DATE — the effective window of the resolved tax code from AR_VAT_TAX.
• TAX_CODE — the resolved default tax code after applying the priority chain.

Common Use Cases and Queries

The view is typically queried by Order Entry tax defaulting logic and by developers diagnosing why a particular tax code was or was not defaulted. The nested DECODE implements a precedence chain: site-use tax code first (when TAX_USE_SITE_EXC_RATE_FLAG is 'Y'), then customer-level TAX_CODE, then item-level TAX_CODE, and finally a fallback that only returns a tax code when TAX_METHOD is SALES_TAX and the tax type is LOCATION.

A representative query returning the resolved tax code for a given site use and item follows:

• SELECT site_use_id, customer_id, inventory_item_id, organization_id, tax_code, start_date, end_date FROM ar_default_tax_code_v WHERE site_use_id = :site_use_id AND inventory_item_id = :item_id;

Because the view depends on AR_SYSTEM_PARAMETERS flags, results are sensitive to the current tax method configuration. When TAX_METHOD is not 'SALES_TAX', the fallback branch returns NULL, and the code must be supplied through site, customer, or item level assignment. This behavior makes the view a reliable diagnostic for sales tax defaulting issues in Receivables and Order Management integrations.