Search Results tax_exempt_reason_code




Overview
Explore in AI Chat

Overview

The OE_AK_T_EXEMPT_REASON_V view is a lightweight, read-only database object owned by the APPS schema in Oracle E-Business Suite. It is registered under the Order Management (ONT) product family and carries a VALID status in both the 12.1.1 and 12.2.2 releases. Its purpose is narrow and well defined: it exposes the list of valid tax exemption reason codes that are available to the Order Management application. The name incorporates the "AK" convention historically used by Oracle's Application Toolkit and descriptive flexfield infrastructure, but the view itself functions as a simple lookup access layer. Rather than requiring callers to know the internal structure of the lookups table, the view returns a single, clean column that application code, concurrent programs, and external integrations can consume directly.

Underlying Base Objects

The view is defined over a single base object, OE_LOOKUPS, which is itself a view rather than a physical table. The documented view text is:

This definition filters OE_LOOKUPS to the row set where the lookup type equals TAX_EXEMPT_REASON_CODE. In practice, OE_LOOKUPS resolves to the underlying Oracle Applications lookup tables (typically FND_LOOKUP_VALUES, filtered for the Order Management lookup types). Because the view is a projection with a hard-coded predicate rather than a join across multiple entities, there is no referential dependency on order headers, lines, or tax detail tables. Its relationship to the base objects is therefore strictly one-to-many in the lookup sense: one lookup type yields many exemption reason codes.

Key Columns

The view exposes exactly one column, documented as TAX_EXEMPT_REASON_CODE:

  • TAX_EXEMPT_REASON_CODE — The lookup code value drawn from the LOOKUP_CODE column of OE_LOOKUPS. Each row represents one selectable reason for a tax exemption. Typical values in a standard installation include codes for resale, government, charitable, and similar statutory categories, though the exact set is customer-maintainable through the Application Lookups setup form.

Because only the code is returned, the view does not carry the associated meaning, description, enabled flag, display sequence, or effective dates that exist in the fuller lookup structures. Callers needing descriptive text must join back to FND_LOOKUP_VALUES or query OE_LOOKUPS directly.

Common Use Cases and Queries

The primary scenario is populating a list of values or validating an exemption reason supplied through an order import, an order entry screen, or an external tax integration. The view is also useful for reconciliation reporting, confirming which codes are defined in a given environment before a data migration.

A typical query to enumerate all available exemption reasons:

  • SELECT TAX_EXEMPT_REASON_CODE FROM APPS.OE_AK_T_EXEMPT_REASON_V ORDER BY 1;

To confirm that a specific code is valid before inserting an order line interface record:

  • SELECT TAX_EXEMPT_REASON_CODE FROM APPS.OE_AK_T_EXEMPT_REASON_V WHERE TAX_EXEMPT_REASON_CODE = 'RESALE';

To obtain the human-readable meaning alongside each code, the view is joined to the underlying lookup values:

  • SELECT v.TAX_EXEMPT_REASON_CODE, l.MEANING FROM APPS.OE_AK_T_EXEMPT_REASON_V v, APPS.FND_LOOKUP_VALUES l WHERE l.LOOKUP_TYPE = 'TAX_EXEMPT_REASON_CODE' AND l.LOOKUP_CODE = v.TAX_EXEMPT_REASON_CODE AND l.VIEW_APPLICATION_ID = 0;

Because the object is a view over lookup data, no DML is permitted; maintenance of the exemption reason list is performed through the Application Developer responsibility or the Order Management setup menu, not through this object.