Search Results ship_site

Overview

CS_TAX_LINES_SUMMARY_V is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Service (CS) product family. Its documented purpose is to supply tax-related line summary information to the Oracle EBS Taxation module. In practice the view reshapes service estimate data — the estimate details captured against a service incident — into the column layout expected by the tax engine, so that tax codes, rates, taxable bases, and jurisdiction information can be evaluated for service transactions. It is therefore a reporting and integration construct rather than a transaction table: no data is stored in the view itself, and all values are derived at query time.

The view is especially relevant to users searching for bill_site, because the invoice-to and ship-to party site identifiers flow directly into the view through the RA_SITE_USES table aliased as BILL_SITE and SHIP_SITE. These site-use rows are resolved by the PL/SQL functions CS_CHARGE_CORE_PVT.GET_INVOICE_TO_PARTY_SITE_ID and CS_CHARGE_CORE_PVT.GET_SHIP_TO_SITE_ID, making the billing site a first-class dimension of every tax line returned.

Underlying Base Objects

The view text joins a fixed set of base tables and views:

• CS_ESTIMATE_DETAILS ESTDET — the driving table, supplying estimate line quantity, selling price, conversion rate, item, and the ship-to and invoice-to organization identifiers.
• CS_INCIDENTS_ALL INC — the parent service incident, supplying INCIDENT_ID and ORG_ID.
• RA_SITE_USES BILL_SITE and SHIP_SITE — site-use records resolved through the CS_CHARGE_CORE_PVT functions via outer joins keyed on SITE_USE_ID.
• RA_ADDRESSES BILL_LOC and SHIP_LOC — address records joined on ADDRESS_ID, providing postal codes and location identifiers.
• AR_VAT_TAX V — the tax definition source for tax code, tax rate, VAT tax identifier, taxable basis, and the tax calculation PL/SQL block.
• MTL_SYSTEM_ITEMS MTL — inventory item and organization identification, constrained by CS_STD.GET_ITEM_VALDN_ORGZN_ID.
• FND_CURRENCIES C — currency code and precision.
• CS_BUSINESS_PROCESSES BP and ASO_I_ORDER_TYPES_V ASO — business process and order type context.

Documented ETRM metadata for 12.2.2 also lists CS_TXN_BILLING_TYPES (as a synonym) among referenced base objects, reflecting the billing-type context used when tax is applied to service transactions.

Key Columns

• CUSTOMER_ID (two occurrences, from SHIP_LOC and BILL_LOC) — ship-to and bill-to customer identifiers.
• LOCATION_ID (two occurrences) — ship-to and bill-to address identifiers.
• POSTAL_CODE (two occurrences) — ship-to and bill-to postal codes, used for jurisdiction determination.
• SHIP_TO_ORG_ID and INVOICE_TO_ORG_ID — the party site identifiers that resolve the bill_site and ship site context.
• TAX_CODE, TAX_RATE, VAT_TAX_ID, TAXABLE_BASIS, TAX_CALCULATION_PLSQL_BLOCK, AMOUNT_INCLUDES_TAX_FLAG — tax attributes inherited from AR_VAT_TAX.
• ESTIMATE_DETAIL_ID and INCIDENT_ID — the service transaction keys.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, QUANTITY_REQUIRED, SELLING_PRICE, CONVERSION_RATE — item and pricing detail used to derive the taxable amount.
• CURRENCY_CODE and PRECISION — currency context.
• Literal values such as 'ALL' and 'Y' populate positional columns expected by the tax engine.

Common Use Cases and Queries

The view is typically queried to retrieve taxable service estimate lines for an incident, to reconcile tax amounts by billing site, or to feed external tax reporting. A representative query filtering on billing site context is:

• SELECT incident_id, estimate_detail_id, invoice_to_org_id, tax_code, tax_rate, taxable_basis, currency_code FROM cs_tax_lines_summary_v WHERE invoice_to_org_id = :p_bill_site_id;
• SELECT i.incident_number, v.tax_code, SUM(v.quantity_required * v.selling_price) FROM cs_tax_lines_summary_v v, cs_incidents_all i WHERE v.incident_id = i.incident_id GROUP BY i.incident_number, v.tax_code;
• SELECT invoice_to_org_id, postal_code, COUNT(*) FROM cs_tax_lines_summary_v WHERE tax_code IS NOT NULL GROUP BY invoice_to_org_id, postal_code;

Because several joins are outer joins, rows may be returned with null bill-to or ship-to attributes when no site use is defined for an estimate line; consumers should account for this when aggregating tax totals.