Search Results a_bill




Overview
Explore in AI Chat

Overview

The view SO_TAX_LINES_SUMMARY_V is an Order Entry (OE) tax reporting object that presents a pre-calculated, line-level summary of taxable transaction data for sales orders. It belongs to the E-Business Tax (EBTax) integration layer and serves as a staging representation from which tax calculation engines, tax reporting extracts, and reconciliation queries can read order-line attributes in a structure aligned to the generic tax lines interface. In the documented ETRM 12.2.2 metadata the view is marked as "Not implemented in this database," meaning it exists as a seed/deployment artifact that is instantiated only in environments where the corresponding OE tax summary logic has been deployed. Its principal design role is to flatten header, line, address, and currency attributes into a single row per order line, supplying the inputs required by the PL/SQL tax calculation block invoked during order processing.

Underlying Base Objects

The view text references a header table (aliased H, contributing HEADER_ID, TAX_EXEMPT_FLAG, TAX_EXEMPT_NUM, TAX_EXEMPT_REASON_CODE, INVOICING_RULE_ID, CONVERSION_RATE and FOB_CODE), a line table (aliased L, contributing LINE_ID, SCHEDULE_DATE, DATE_REQUESTED_CURRENT, PROMISE_DATE, INVENTORY_ITEM_ID, ORDERED_QUANTITY, CANCELLED_QUANTITY and SELLING_PRICE), customer/location tables for ship-to and bill-to parties (A_SHIP, A_BILL, S_SHIP, S_BILL), a tax code/rate source (aliased V, contributing TAX_CODE and TAX_RATE), and a currency table (aliased C, contributing CURRENCY_CODE, MINIMUM_ACCOUNTABLE_UNIT and PRECISION). ETRM records the referenced base objects as "none documented," so the exact physical table names are inferred from their aliases rather than confirmed; in practice these resolve to OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS and FND_CURRENCIES.

Key Columns

The view exposes paired ship-to and bill-to identities and addresses: SHIP_TO_CUSTOMER_ID, BILL_TO_CUSTOMER_ID, SHIP_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID, SHIP_TO_POSTAL_CODE, BILL_TO_POSTAL_CODE, SHIP_TO_LOCATION_CCID and BILL_TO_LOCATION_CCID. Transaction context is carried by TRX_HEADER_ID and TRX_LINE_ID, with TRX_DATE derived through a nested NVL chain over SCHEDULE_DATE, DATE_REQUESTED_CURRENT, PROMISE_DATE and SYSDATE. Tax-relevant columns include TAX_CODE, TAX_RATE, TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, TAX_EXEMPT_REASON_CODE and TAXED_QUANTITY, the latter computed as ORDERED_QUANTITY minus CANCELLED_QUANTITY. EXTENDED_AMOUNT applies the same net quantity against SELLING_PRICE. Currency precision is supplied through TRX_CURRENCY_CODE, MINIMUM_ACCOUNTABLE_UNIT and PRECISION. Several columns—TAX_AMOUNT, GL_DATE, SET_OF_BOOKS_ID, TRX_NUMBER, MEMO_LINE_ID and the ATTRIBUTE1–5 and NUMERIC_ATTRIBUTE1–5 fields—are returned as NULL placeholders, indicating the view supplies calculation inputs rather than stored tax results. LOCATION_QUALIFIER is hard-coded to 'ALL' and TAXABLE_FLAG to 'Y'.

Common Use Cases and Queries

Typical uses include pre-validation of taxable order lines before invoking tax calculation and reconciliation of order-line amounts against downstream receivables tax records. A representative query:

  • SELECT TRX_HEADER_ID, TRX_LINE_ID, TRX_DATE, TAX_CODE, TAX_RATE, TAXED_QUANTITY, EXTENDED_AMOUNT, TRX_CURRENCY_CODE FROM SO_TAX_LINES_SUMMARY_V WHERE TAX_EXEMPT_FLAG = 'N' AND TAXED_QUANTITY > 0;
  • Joining TRX_LINE_ID to OE_ORDER_LINES_ALL.LINE_ID to enrich the summary with order number and item context.
  • Aggregating EXTENDED_AMOUNT by SHIP_TO_CUSTOMER_ID and TAX_CODE for jurisdictional tax exposure reporting.

Because TAX_AMOUNT is NULL, consumers must apply TAX_RATE to EXTENDED_AMOUNT, or pass the row into the tax_calculation_plsql_block, which is the documented consumer of this structure.