Results for “customer_exception_number”

12 results




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

Overview

OKX_TAX_EXEMPTIONS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, registered under the OKX – Contracts Integration product family. In EBS 12.1.1 and 12.2.2 the view presents tax exemption records that originate in Oracle Receivables and exposes them in a shape suitable for consumption by Oracle Contracts and related integration flows. The view is documented as VALID in the ETRM repository, and its description is simply "Tax exemptions."

Functionally, the view is a thin projection over the Receivables tax exemption table. It does not perform aggregation or joins across multiple base objects; instead it renames, decodes, and reorders columns so downstream Oracle Contracts logic, service-oriented integration, and custom reports can retrieve exemption data using a stable OKX-prefixed interface. Because the OKX layer sits between Receivables and Contracts, changes to the underlying RA tables can be insulated from contract-facing code by adjustments within this view.

Underlying Base Objects

The view is defined over a single referenced base object, documented in the ETRM metadata as the synonym RA_TAX_EXEMPTIONS_ALL. That synonym resolves to the Receivables tax exemptions entity, which stores exemption definitions at the organization, customer, site, and inventory item level.

Key derivation rules in the view text are limited and mechanical: the primary key TAX_EXEMPTION_ID is aliased to ID1; a literal '#' is returned as ID2 to satisfy a two-part identifier convention; EXEMPTION_TYPE is exposed as NAME; START_DATE and END_DATE are exposed as START_DATE_ACTIVE and END_DATE_ACTIVE; and REASON_CODE is exposed as DESCRIPTION. The STATUS column is recomputed with a DECODE so that both 'MANUAL' and 'PRIMARY' source statuses map to 'A', and all remaining values map to 'I'. The original source status is retained separately as B_STATUS.

Key Columns

  • APPROVAL_STATUS – passes through the raw TE.STATUS value from the base table, presented as an approval-oriented attribute.
  • NAME – the exemption type (from EXEMPTION_TYPE), used to classify the exemption.
  • TAX_CODE, PERCENT_EXEMPT – the tax code being exempted and the percentage of exemption applied.
  • START_DATE_ACTIVE, END_DATE_ACTIVE – effective date range of the exemption.
  • B_STATUS, STATUS – B_STATUS holds the original Receivables status; STATUS is the derived active/inactive indicator ('A' or 'I').
  • DESCRIPTION – carried from REASON_CODE, describing why the exemption was granted.
  • ORG_ID – operating unit identifier supporting multi-org filtering.
  • INVENTORY_ITEM_ID, CUSTOMER_ID, SITE_USE_ID – the item, customer, and site-use qualifiers that scope the exemption.
  • CUSTOMER_EXCEPTION_NUMBER – the customer exemption number (the view deliberately spells it EXCEPTION rather than EXEMPTION).
  • IN_USE_FLAG – the user's search term; this column is passed straight through from the base table and indicates whether the exemption record is currently in use and therefore protected from deletion.

Common Use Cases and Queries

Typical uses include validating exemption coverage for a customer or item before contract pricing, reconciling active exemptions by operating unit, and restricting maintenance operations to records that are not flagged in use. The IN_USE_FLAG column is frequently referenced to prevent the removal of exemptions that are referenced elsewhere.

List active exemptions for a customer:

  • SELECT customer_id, tax_code, percent_exempt, start_date_active, end_date_active, status, in_use_flag FROM okx_tax_exemptions_v WHERE customer_id = :customer_id AND status = 'A';

Find exemptions currently flagged in use:

  • SELECT tax_code, customer_id, inventory_item_id, org_id, in_use_flag FROM okx_tax_exemptions_v WHERE in_use_flag = 'Y';

Report exemptions effective on a given date by operating unit:

  • SELECT org_id, tax_code, percent_exempt FROM okx_tax_exemptions_v WHERE :as_of_date BETWEEN start_date_active AND NVL(end_date_active, :as_of_date) AND org_id = :org_id;

Because the view performs no aggregation, queries are inexpensive, but multi-org security must still be applied explicitly through ORG_ID when the view is used outside standard EBS report contexts.