Results for “tax_control_flag”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.ASO_I_TAX_STATUSES_V is a lightweight, read-only view in Oracle E-Business Suite that exposes the set of valid tax control statuses used by the Order Capture / Order Management product family (ASO schema). Rather than storing data of its own, the view projects a filtered subset of the AR_LOOKUPS lookup table, specifically the lookup rows whose LOOKUP_TYPE equals TAX_CONTROL_FLAG. In this way it acts as a controlled vocabulary of taxation statuses (for example, taxable versus exempt or exempt-with-certificate designations) that order and quote processing logic can reference.
Because the view is owned by APPS and defined entirely over an existing lookup source, it presents no independent data storage. Its role is one of abstraction and safety: consumers obtain the current, enabled tax status values without querying the generic AR_LOOKUPS table directly, and the filter guarantees that only tax-control lookups are returned. In reporting and integration contexts, this view provides the de-reference layer that translates a stored lookup code into its user-facing meaning, and simultaneously carries the enablement flag and effective-date columns needed to determine whether a given status is currently active.
Underlying Base Objects
The view is defined over a single documented base object: AR_LOOKUPS, itself exposed within the database as a view. AR_LOOKUPS is the shared Oracle Receivables lookup repository, organizing reference values by LOOKUP_TYPE. The definition of ASO_I_TAX_STATUSES_V is a straightforward filtered projection:
- SELECT MEANING, LOOKUP_CODE, ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE FROM AR_LOOKUPS WHERE LOOKUP_TYPE = 'TAX_CONTROL_FLAG'
Two practical consequences follow from this definition. First, the view is bound to the naming and semantics of the TAX_CONTROL_FLAG lookup type; any lookup maintained under that type immediately becomes visible through the view, and any change to its meaning, enablement, or date range is reflected without further maintenance. Second, because AR_LOOKUPS is itself a view over the underlying lookup tables, the object chain terminates in the base lookup storage, but the documented reference in ETRM 12.2.2 lists AR_LOOKUPS as the referenced base object.
Key Columns
- LOOKUP_CODE — The stored code value for the tax control status. This is the value typically persisted on order, line, or party records and is the join key back to source transactions.
- MEANING — The translatable, user-facing description of the status. Reports and integrations generally present MEANING rather than the raw code.
- ENABLED_FLAG — Indicates whether the lookup value is active (Y) or disabled (N). Standard practice is to filter on 'Y' when presenting selectable statuses, while retaining 'N' rows where historical values must still be resolvable.
- START_DATE_ACTIVE — The date from which the status became effective; null typically denotes no lower bound.
- END_DATE_ACTIVE — The date after which the status is no longer effective; null typically denotes no upper bound.
The view exposes no primary key column of its own; LOOKUP_CODE is unique within the TAX_CONTROL_FLAG lookup type and serves as the de facto identifier.
Common Use Cases and Queries
The most frequent use is populating a list of values or resolving a code to its meaning in a report. A typical query retrieves only currently enabled statuses:
- SELECT lookup_code, meaning FROM apps.aso_i_tax_statuses_v WHERE enabled_flag = 'Y' ORDER BY meaning;
Where historical accuracy matters, the effective-date columns support as-of resolution. For example, a query may include all rows and let the consumer compare a transaction date against START_DATE_ACTIVE and END_DATE_ACTIVE. Integrations extracting tax status reference data commonly select the full column set for a staging load, while LOV definitions in Order Management forms and OA Framework pages bind to the enabled subset. Because the view performs no aggregation and carries no ordering, performance is effectively that of the underlying lookup access, making it suitable for high-frequency lookup resolution as well as batch reference-data extracts.
-
Override of Tax calculation
-
Override of Tax calculation
-
VIEW: APPS.SO_TAX_STATUSES_V 12.1.1
-
VIEW: APPS.SO_TAX_STATUSES_V 12.2.2
-
View: ASO_I_TAX_STATUSES_V 12.2.2
View based on AR lookups
-
View: SO_TAX_STATUSES_V 12.2.2
-
View: SO_TAX_STATUSES_V 12.1.1
-
View: ASO_I_TAX_STATUSES_V 12.1.1
View based on AR lookups
-
APPS.IGI_RA_CUSTOMER_TRX_PARTIAL_V·↳ ARPT_SQL_FUNC_UTIL·↳ AR_LOOKUPS·↳ AR_PAYMENT_SCHEDULES_ALL·Explore IGI module →
-
APPS.IGI_RA_CUSTOMER_TRX_PARTIAL_V·↳ ARPT_SQL_FUNC_UTIL·↳ AR_LOOKUPS·↳ AR_PAYMENT_SCHEDULES_ALL·Explore IGI module →
-
View: ICX_SO_HEADERS_V 12.2.2
Order Entry Header View
Not implemented in this database·Explore ICX module →
-
View: ICX_SO_HEADERS_V 12.1.1
Order Entry Header View
Not implemented in this database·Explore ICX module →
-
10SC Only
APPS.PA_DRAFT_INVOICE_LINES_ALL_V·↳ AR_LOOKUPS·↳ AR_VAT_TAX_ALL·↳ HZ_CUST_ACCT_SITES_ALL·Explore PA module →
-
10SC Only
APPS.PA_DRAFT_INVOICE_LINES_ALL_V·↳ AR_LOOKUPS·↳ AR_VAT_TAX_ALL·↳ HZ_CUST_ACCT_SITES_ALL·Explore PA module →
-
This will select data from pa_draft_invoices, pa_mc_draft_inv_items, pa_draft_invoice_items
Not implemented in this database·Explore PA module →
-
This will select data from pa_draft_invoices, pa_mc_draft_inv_items, pa_draft_invoice_items
Not implemented in this database·Explore PA module →
-
View: SO_HEADERS_RMA_V 12.1.1
Not implemented in this database·Explore OE module →
-
View: SO_HEADERS_RMA_V 12.2.2
Not implemented in this database·Explore OE module →
-
View: SO_HEADERS_V 12.2.2
Not implemented in this database·Explore OE module →
-
12.1.1 FND Design Data 12.1.1
-
View: SO_HEADERS_V 12.1.1
Not implemented in this database·Explore OE module →
-
12.2.2 FND Design Data 12.2.2
-
Line and distribution-level archive information
-
Line and distribution-level archive information