Search Results tax_point_code




Overview
Explore in AI Chat

Overview

The OE_AK_TAX_POINT_V view is a lightweight, read-only database object owned by the APPS schema in Oracle E-Business Suite, residing within the Order Management (ONT) product family. Its purpose is narrow and well-defined: it exposes the set of valid tax point codes configured in the application as a simple, single-column list of lookup codes. Rather than requiring developers and integrators to query the underlying lookup infrastructure directly, the view provides a filtered, purpose-built interface that returns only those lookup codes associated with the TAX_POINT_CODE lookup type.

Within Oracle EBS, a tax point determines the moment at which a tax event is considered to occur for a given transaction line. Common tax point values govern whether tax is calculated, for example, at the point of order entry, shipment, invoice, or receipt. Because these values are seeded and maintained through the Oracle Order Management lookup framework, the OE_AK_TAX_POINT_V view serves as the canonical reference for the valid tax point codes available to the order-to-cash flow. It is typically consumed by reporting layers, extensions, interfaces, and integrations that must validate or display tax point selections without hard-coding the lookup domain.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view is defined over a single referenced base object: OE_LOOKUPS, itself a view within the APPS schema. OE_LOOKUPS is the Order Management lookup repository, which exposes enabled lookup codes and their meanings across the various lookup types used by the ONT module, including tax-related configurations.

The view text is deliberately minimal. It performs a projection and filter, selecting the LOOKUP_CODE column from OE_LOOKUPS while restricting results to rows where LOOKUP_TYPE equals 'TAX_POINT_CODE'. Consequently, OE_AK_TAX_POINT_V acts purely as a convenience wrapper around a subset of OE_LOOKUPS. No joins, aggregations, or computed expressions are involved, and the view retains the read-only nature of its underlying source. Because OE_LOOKUPS is itself a view, the effective lineage extends further into the lookup tables maintained by the application, but the documented dependency chain for this object terminates at OE_LOOKUPS.

Key Columns

The view exposes a single documented column:

  • TAX_POINT_CODE — The lookup code value drawn from the TAX_POINT_CODE lookup type. Each row represents one valid tax point code that may be assigned within Order Management tax determination logic. The column carries the short code used programmatically and in stored references, rather than the longer descriptive meaning that would be retrieved from the underlying lookup's MEANING column.

Because only the code is projected, consumers needing the human-readable description must resolve it separately against OE_LOOKUPS or the appropriate lookup query, rather than relying on this view alone.

Common Use Cases and Queries

The primary use case is populating selection lists, validating incoming tax point values, and supporting reporting on order tax configuration. A typical query retrieves the full set of valid codes:

  • SELECT tax_point_code FROM oe_ak_tax_point_v;
  • SELECT tax_point_code FROM oe_ak_tax_point_v WHERE tax_point_code = :p_code; — used to validate a specific code supplied by an interface or user entry.
  • SELECT tax_point_code FROM oe_ak_tax_point_v ORDER BY tax_point_code; — used to drive a sorted list of values in a concurrent program parameter or a custom form LOV.

Integration developers frequently reference this view when building outbound extracts or inbound order interfaces that carry tax point indicators, ensuring the values they transmit conform to the configured lookup domain. Reporting analysts use it to enumerate tax point options for audit and configuration documentation. Because the view is lightweight and unfiltered beyond the lookup type, it performs efficiently and is safe for repeated invocation in batch and interactive contexts. As with all APPS-owned views, direct DML is not supported; any change to the available tax point codes must be made through the standard lookup maintenance functionality rather than through the view itself.