Search Results ship_to_address_code




Overview
Explore in AI Chat

Overview

The view OE_TAX_LINES_SUMMARY_V belongs to the Oracle Order Management (ONT) module and exists to serve the Oracle E-Business Tax (Tax Engine / ETRM) during order line tax calculation. Its stated purpose is to present order line attributes in a structure the Tax Engine can consume so that applicable taxes can be determined for each ordered line. The view is a read-only abstraction: rather than exposing the raw base tables that store order headers, lines, and address data, it projects the specific subset of columns that the Tax Engine requires at the time tax is computed for an order line.

Because the Tax Engine expects a consistent, common set of tax-relevant columns—customer identifiers, address information, exemption flags, currency precision, extended amounts, and quantities—this view normalizes those attributes from Order Management source data into the shape the tax calculation interface anticipates. It is not a stored reporting table; it functions as an integration and calculation surface. As documented in the ETRM metadata, the view is marked as "Not implemented in this database" in the reference environment, meaning its presence depends on the specific instance and ETRM installation. This informs both migration testing and impact analysis. In Oracle EBS 12.1.1 and 12.2.2, this view supports the tax determination flow by supplying line-level inputs the Tax Engine evaluates against configuration rules.

Underlying Base Objects

The documented ETRM metadata lists no referenced base objects for this view. The view text, however, reveals the aliased sources from which columns are projected. These include order header and line sources (aliased L for line and H for header), address sources (aliased A_SHIP and A_BILL), site-use sources (aliased S_SHIP and S_BILL), a tax code/rate source (aliased V), and a currency source (aliased C). Header values such as H.CONVERSION_RATE derive from the order header, while quantity and pricing attributes derive from the order line. Address-related sources supply postal code, location CCID, and site-use identifiers for both ship-to and bill-to parties.

Since the official base-object list is not documented, the exact physical mapping should be confirmed against the deployed view definition in each environment. The important structural point is that the view joins order line data against both shipping and billing address context, tax code/rate information, and currency attributes, then labels the entire result set with a location qualifier of 'ALL'.

Key Columns

Notably, SHIP_TO_ADDRESS_CODE—the term the user searched—appears in the projection as NULL, along with POO_ADDRESS_CODE, POA_ADDRESS_CODE, and SHIP_FROM_ADDRESS_CODE. These address-code columns are placeholders in this view; the ship-to address is instead represented through the site-use, postal code, and location CCID columns.

Common Use Cases and Queries

This view is primarily consumed by the Tax Engine rather than by end users writing ad-hoc reports. Typical diagnostic scenarios include tracing the inputs used to calculate tax for a given order line and verifying which ship-to address attributes were passed to tax determination. A representative query follows:

  • SELECT TRX_HEADER_ID, TRX_LINE_ID, SHIP_TO_CUSTOMER_ID, SHIP_TO_SITE_USE_ID, SHIP_TO_POSTAL_CODE, SHIP_TO_LOCATION_CCID, TAX_CODE, TAX_RATE, EXTENDED_AMOUNT, TRX_CURRENCY_CODE FROM OE_TAX_LINES_SUMMARY_V WHERE TRX_HEADER_ID = :header_id;
  • To inspect exemption handling for a line: SELECT TRX_LINE_ID, TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, TAX_EXEMPT_REASON_CODE FROM OE_TAX_LINES_SUMMARY_V WHERE TRX_LINE_ID = :line_id;
  • To review address-related inputs: SELECT TRX_LINE_ID, SHIP_TO_POSTAL_CODE, BILL_TO_POSTAL_CODE, SHIP_TO_ADDRESS_CODE, SHIP_TO_SITE_USE_ID FROM OE_TAX_LINES_SUMMARY_V WHERE TRX_HEADER_ID = :header_id; — noting that SHIP_TO_ADDRESS_CODE resolves to NULL in this projection.

Because the view is documented as not implemented in the reference database, availability should be confirmed in each target instance before relying on it in custom code or queries.