Search Results a_ship




Overview
Explore in AI Chat

Overview

OE_TAX_LINES_SUMMARY_V_A is an Order Management (ONT) view whose documented purpose is to expose order line data to the Oracle Tax Engine so that tax can be calculated on order lines when the external tax vendor Taxware is configured as the tax provider. It is therefore an integration-oriented view: it presents the taxable attributes of a sales order line in a normalized, tax-engine-compatible shape rather than acting as a general-purpose reporting view. The "A" suffix and the placement of the object under the ONT product indicate that it functions as an Application Programming Interface (API) view consumed by the Tax Engine's tax calculation routines, not as an end-user query view. The user search term "a_ship" aligns directly with the view's internal aliasing convention: the view joins address subqueries aliased A_SHIP (ship-to address) and A_BILL (bill-to address), and the ship-to side of each expression is commonly wrapped in NVL(A_SHIP., A_BILL.) so that bill-to values are substituted when a ship-to value is unavailable.

Underlying Base Objects

The ETRM metadata documents no referenced base objects and the implementation notes record "Not implemented in this database" for the catalogued instance, but the published view text shows the view is defined over Order Management order header and order line entities (aliased H and L, supplying HEADER_ID, LINE_ID, TAX_DATE, TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, TAX_EXEMPT_REASON_CODE, INVENTORY_ITEM_ID, INVOICING_RULE_ID, ORDERED_QUANTITY, UNIT_SELLING_PRICE, SHIP_FROM_ORG_ID and SALESREP_ID). Address data is drawn from address objects aliased A_SHIP and A_BILL, with site use identifiers from S_SHIP and S_BILL. Currency attributes (CURRENCY_CODE, MINIMUM_ACCOUNTABLE_UNIT, PRECISION) come from the currency entity aliased C, and the exchange rate from the header entity H. Tax code and tax rate are supplied by the entity aliased V, and several columns are populated by calls to the ARP_TAX_VIEW_TAXWARE package, which returns Taxware address codes for point of order, point of acceptance, ship-from and ship-to locations.

Key Columns

Common Use Cases and Queries

The view is consumed by the Tax Engine when Taxware is the external tax vendor, so direct querying is primarily diagnostic: confirming that the correct ship-to address, tax date and taxable amount are being passed for a given order line.

Sample query tracing a line and its ship-to versus bill-to resolution:

  • SELECT TRX_HEADER_ID, TRX_LINE_ID, TRX_DATE, SHIP_TO_CUSTOMER_ID, BILL_TO_CUSTOMER_ID, SHIP_TO_POSTAL_CODE, TAX_CODE, TAX_RATE, EXTENDED_AMOUNT FROM OE_TAX_LINES_SUMMARY_V_A WHERE TRX_HEADER_ID = :p_header_id;
  • SELECT TRX_LINE_ID, SHIP_TO_SITE_USE_ID, SHIP_TO_LOCATION_CCID, SHIP_TO_ADDRESS_CODE FROM OE_TAX_LINES_SUMMARY_V_A WHERE TRX_LINE_ID = :p_line_id;

Because the view references the ARP_TAX_VIEW_TAXWARE package for address codes, it is available only where the Taxware integration objects are installed; in environments without that integration the view is not implemented, and tax calculation falls to the native EBS Tax Engine views instead.