Search Results tax_control_flag




Overview
Explore in AI Chat

Overview

APPS.SO_TAX_STATUSES_V is a lightweight reporting and integration view within the Oracle E-Business Suite Applications (APPS) schema. Its purpose is to expose the valid tax control / tax exemption statuses used by Oracle Receivables and related order-to-cash flows in a denormalized, presentation-ready form. Rather than requiring downstream reports, concurrent programs, or external integrations to understand the internal encoding of Oracle Receivables lookup types, the view surfaces only those lookup codes associated with the tax control flag, pairing each code with its human-readable display value. In releases 12.1.1 and 12.2.2 the view remains a thin wrapper over the Receivables lookup infrastructure and therefore carries no independent data storage of its own.

Underlying Base Objects

The view is defined entirely over a single referenced object, AR_LOOKUPS. The documented ETRM view text is:

AR_LOOKUPS is the Receivables lookup table that stores seeded and user-defined lookup codes across many lookup types. This view filters that table to the single lookup type TAX_CONTROL_FLAG, which is the lookup type that governs the tax control / tax exemption status values available on customer, site, and transaction records. Because the view selects from AR_LOOKUPS without joins, its rows change whenever the underlying lookup values for that type are added, end-dated, or disabled. The view therefore functions as a filtered projection of the AR_LOOKUPS lookup type set rather than as a materialized or cached structure.

Key Columns

The view exposes two columns, both derived directly from AR_LOOKUPS:

  • TAX_EXEMPT_FLAG_DISPLAY — Maps to AR_LOOKUPS.MEANING. This is the descriptive, user-facing label for the tax control status (for example, a "Tax Exempt" or "Taxable" style meaning), suitable for display in reports, LOVs, and integration payloads.
  • TAX_EXEMPT_FLAG — Maps to AR_LOOKUPS.LOOKUP_CODE. This is the internal code value that is stored against the tax control flag field on transactional and party records, and is the value that business logic and validations typically evaluate.

Although AR_LOOKUPS contains additional attributes such as description, enabled flag, start and end dates, tag, and attribute columns, the view deliberately restricts output to these two columns. Consequently, the view does not expose enablement or date-range information directly; consumers that need to distinguish currently active lookups from disabled or end-dated ones must query AR_LOOKUPS itself rather than relying on this view.

Common Use Cases and Queries

The view is principally used to populate selection lists and decode reports, and to provide a stable interface for external systems that must translate between tax status codes and their display meanings. A typical reporting query retrieves all tax control statuses for a picklist or validation reference:

  • SELECT tax_exempt_flag, tax_exempt_flag_display FROM apps.so_tax_statuses_v ORDER BY tax_exempt_flag_display;

A common integration pattern joins the view to tax or customer data to render descriptive status text alongside stored codes:

  • SELECT t.customer_id, s.tax_exempt_flag_display FROM apps.so_tax_statuses_v s, apps.ra_customers t WHERE t.tax_control_flag = s.tax_exempt_flag;

Because the view is a simple filter over a seeded lookup type, it requires no special grants beyond the standard APPS synonym and is safe to query in read-only reporting environments. When additional lookup attributes such as description or enabled status are required, the recommended approach is to query AR_LOOKUPS directly with the same LOOKUP_TYPE = 'TAX_CONTROL_FLAG' predicate and applicable enabled and date filters.