Results for “ship_to_address_id”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view APPS.PA_OUTPUT_TAX_EXEMPT_NUMBER_V is a Projects (PA) module database object shipped in Oracle E-Business Suite 12.1.1 and 12.2.2. ETRM metadata classifies the object as a VIEW owned by the APPS schema with VALID status, and its description field carries the notation "10SC Only," indicating that the object is scoped to a specific localization or release configuration rather than to the general global feature set. The view is not a standalone tax-exemption store; it is a thin projection built on top of the E-Business Tax / Oracle Receivables tax exemption infrastructure, and it exists to expose a filtered, Projects-relevant subset of exemption records to downstream reporting and integration consumers.

Practically, the view presents one row per customer exemption record that is currently active and that has an associated ship-to site use. It is designed to return the tax exemption number, the reason for exemption, the customer identifier, and the ship-to account site, allowing Projects output tax and invoicing logic to determine whether a transaction counterparty holds a valid exemption certificate on the effective date.

Underlying Base Objects

ETRM records two referenced base objects for this view: HZ_CUST_SITE_USES (referenced as a SYNONYM) and TAX_EXEMPTIONS_QP_V (a VIEW). The view text confirms this composition, with TAX_EXEMPTIONS_QP_V aliased as TE and HZ_CUST_SITE_USES aliased as HZ_SU.

  • TAX_EXEMPTIONS_QP_V — the primary source of exemption attributes, supplying tax exemption number, reason code, reason meaning, customer identifiers, ship-to site use, status, and the start/end dates of the exemption.
  • HZ_CUST_SITE_USES — the Trading Community Architecture (TCA) table holding customer account site use assignments; it is joined to resolve the ship-to site use to a customer account site identifier.

The join is driven by TE.SHIP_TO_CUSTOMER_ID = TE.BILL_TO_CUSTOMER_ID and TE.SHIP_TO_SITE_USE_ID = HZ_SU.SITE_USE_ID. The self-referencing condition on the exemption view restricts output to records where the ship-to and bill-to customer are identical, a common simplification for Projects billing scenarios.

Key Columns

The column list documented in ETRM is as follows:

  • TAX_EXEMPT_NUMBER — the exemption certificate or registration number issued to the customer.
  • TAX_EXEMPT_REASON_CODE — the coded reason for the exemption, used for reporting and for driving downstream tax determination rules.
  • TAX_EXEMPT_REASON — the descriptive meaning of the reason code; note that ETRM documents the column as TAX_EXEMPT_REASON, while the underlying view text aliases it as TAX_EXEMPT_REASON_MEANING sourced from TE.TAX_EXEMPT_REASON_MEANING.
  • CUSTOMER_ID — the customer identifier associated with the exemption, mapped in the view text to TE.SHIP_TO_CUSTOMER_ID.
  • SHIP_TO_ADDRESS_ID — the ship-to account site identifier, mapped in the view text to HZ_SU.CUST_ACCT_SITE_ID.

The view applies three filters. First, the customer and site conditions described above. Second, TE.STATUS_CODE IN ('PRIMARY', 'UNAPPROVED', 'MANUAL'), which admits primary, manually entered, and unapproved exemption records while excluding other status values. Third, an effective-date test: SYSDATE BETWEEN NVL(TE.START_DATE, SYSDATE) AND NVL(TE.END_DATE, SYSDATE), which ensures only currently effective exemptions are returned and treats open-ended dates as unbounded.

Common Use Cases and Queries

Because the view is date-filtered at runtime, each execution reflects the current point in time, which makes it suitable for operational checks rather than historical audit reporting. A typical query retrieves an exemption certificate for a given customer and site:

  • SELECT tax_exempt_number, tax_exempt_reason_code, tax_exempt_reason
  • FROM apps.pa_output_tax_exempt_number_v
  • WHERE customer_id = :p_customer_id
  • AND ship_to_address_id = :p_site_id;

Common integration scenarios include Projects billing and invoice generation routines that must validate exemption status before tax calculation, reporting extracts feeding exemption dashboards, and interfaces that reconcile Projects transactions against TCA customer site data. Queries that require the operator name, let-alone the user name, should join to HZ_CUST_ACCOUNTS and related TCA tables. Consumers should be aware that the ship-to-equals-bill-to restriction and the fixed status list limit results; records excluded by those conditions must be obtained directly from TAX_EXEMPTIONS_QP_V.