Results for “enabled_flag”

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

Overview

The ASO_I_TAX_EXEMPT_REASONS_V view is a seeded, read-only database object owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the ASO product family — Order Capture — and is documented as VALID in the ETRM repository. The view exposes the subset of tax exemption reason codes that are currently usable for order capture and order entry processing.

Functionally, the view answers a narrow but recurring question in tax determination: which exemption reasons may be offered to a user or consumed by an integration at a given point in time. It does this by filtering the shared Oracle Receivables lookup set (lookup type TAX_REASON) down to those values flagged as enabled. Because exemption reason values are maintained centrally as Receivables lookups, the view provides the Order Capture module with a consistent, restricted presentation of that reference data rather than requiring callers to query AR_LOOKUPS directly.

The view is typically consumed by tax and exemption validation logic, order-entry user interfaces, and integration programs that must reject or accept an exemption reason code before persisting it on sales order or pricing lines. The search term "tax_reason" aligns directly with the lookup type that drives the view's filter predicate.

Underlying Base Objects

The documented view text is:

• SELECT MEANING, LOOKUP_CODE, ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE FROM AR_LOOKUPS WHERE LOOKUP_TYPE = 'TAX_REASON' AND ENABLED_FLAG = 'Y'

In Oracle EBS Release 12.2.2, the ETRM metadata also records the referenced base objects for this view as FND_GLOBAL (PACKAGE) and FND_LOOKUPS (VIEW). This reflects the standard R12 lookup architecture: AR_LOOKUPS is retained as the Receivables-facing synonym/interface that resolves through the common lookup layer, whose canonical access path is the FND_LOOKUPS view. FND_GLOBAL is referenced for session and application context resolution during evaluation.

Each row in the result corresponds to one active tax exemption reason definition. Only rows whose LOOKUP_TYPE is exactly TAX_REASON and whose ENABLED_FLAG is Y survive the filter, so disabled or obsolete reasons are not exposed. The view is therefore a derived projection over lookup maintenance data rather than a stored table; changes to the underlying lookup rows are reflected immediately, with no additional setup or compilation step.

Key Columns

The view exposes five columns. Note the documented column-alias mapping, which differs from the raw lookup column names:

• TAX_EXEMPT_REASON — maps to MEANING; the user-visible, translatable description of the exemption reason.
• TAX_EXEMPT_REASON_CODE — maps to LOOKUP_CODE; the internal code used to store the exemption reason on business documents.
• ENABLED_FLAG — the enablement indicator; always Y within this view.
• START_DATE_ACTIVE — the date from which the reason becomes effective; may be null where no start constraint applies.
• END_DATE_ACTIVE — the date after which the reason is no longer effective; may be null for open-ended definitions.

Because date range columns are surfaced but not filtered, callers that require strict date-based validity should apply their own SYSDATE comparison against START_DATE_ACTIVE and END_DATE_ACTIVE, treating nulls as unbounded.

Common Use Cases and Queries

The principal use cases are populating exemption-reason list-of-values controls, validating codes submitted by external systems, and driving exemption-related reports. A basic query returning enabled reasons in code order is:

• SELECT TAX_EXEMPT_REASON_CODE, TAX_EXEMPT_REASON FROM APPS.ASO_I_TAX_EXEMPT_REASONS_V ORDER BY TAX_EXEMPT_REASON_CODE;

When only currently effective reasons are required, add the date filter, preserving null-safe semantics:

• SELECT TAX_EXEMPT_REASON_CODE, TAX_EXEMPT_REASON FROM APPS.ASO_I_TAX_EXEMPT_REASONS_V WHERE (START_DATE_ACTIVE IS NULL OR START_DATE_ACTIVE <= SYSDATE) AND (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE >= SYSDATE);

To resolve a code captured on a transaction into its descriptive text:

• SELECT TAX_EXEMPT_REASON FROM APPS.ASO_I_TAX_EXEMPT_REASONS_V WHERE TAX_EXEMPT_REASON_CODE = :p_reason_code;

Typical consumers include order-entry forms, Oracle Order Management pricing and tax validation routines, and custom interfaces. Because the view carries no organization or operating unit column, its contents are global; operating-unit-specific restrictions, if any, must be imposed at the lookup or tax setup layer.