Results for “tax_exempt_num”

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

Overview

OPM_SITE_USES_ALL is an Oracle E-Business Suite view owned by the APPS schema and registered under the GMF (Process Manufacturing Financials) product family. It is documented in ETRM for releases 12.1.1 and 12.2.2 with a status of VALID. The view is intended to expose OPM (Oracle Process Manufacturing) site uses — the association between inventory organizations and the operational attributes applied when they are used as sites within OPM financial and transaction flows. Its naming convention follows the standard EBS pattern where "_ALL" denotes a multi-organization view that is filtered by ORG_ID at run time.

The view is important because it presents a consistent interface for the same site-use attributes already familiar from Oracle Receivables and Order Management (such as the TAX_* and SITE_USE_CODE columns), but oriented toward process manufacturing organizations. Reporting, extensions, and third-party integrations that require OPM site-level tax and operational configuration can query it rather than the base object directly.

Underlying Base Objects

The documented view metadata for 12.2.2 lists only one referenced base object: DUAL (a SYNONYM). The view text in ETRM confirms this, consisting of a SELECT projection of literal NULL values aliased to the full column set. In other words, OPM_SITE_USES_ALL is defined over DUAL and returns no data rows; every column is a hard-coded NULL.

This structure is a placeholder or compatibility stub. It exposes the expected column shape of a site-uses entity so that dependent code, forms, reports, and APIs can compile and resolve against a stable object name without the object being populated from a physical table. Because only DUAL is referenced, there is no join to a site-use table, no binding variable on ORG_ID, and no WHERE clause filtering by organization or site-use code.

Key Columns

Although no values are returned, the column list is meaningful because it documents the attribute contract. Notable columns include:

• TAX_CLASSIFICATION — the column most relevant to the user search. In populated site-use models it identifies the tax classification applied to a site for tax determination.
• TAX_CODE, TAX_EXEMPT, TAX_EXEMPT_NUM, TAX_EXEMPT_REASON_CODE — tax determination and exemption attributes associated with the site use.
• SITE_USE_CODE, ADDRESS_ID, PRIMARY_FLAG, STATUS, LOCATION — the identity and status of the site use itself.
• ORG_ID — the operating unit or organization key used to scope multi-organization access.
• WAREHOUSE_ID, BILL_TO_SITE_USE_ID, ORDER_TYPE_ID, PRICE_LIST_ID — references to downstream order, warehouse, and billing configuration.
• ATTRIBUTE1 through ATTRIBUTE25 and GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE16 — descriptive flexfield segments for customer-defined extensions.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY — standard EBS audit columns.

Because all columns evaluate to NULL, any logic that depends on their values must tolerate NULL results and should not assume data presence.

Common Use Cases and Queries

The practical use of this view is limited to schema resolution, column-existence checks, and compatibility with code written against the site-uses interface. Queries that expect real site-use records will return empty result sets. A typical diagnostic query is:

• SELECT TAX_CLASSIFICATION, TAX_CODE, ORG_ID FROM APPS.OPM_SITE_USES_ALL; — returns rows only if the object is repointed to a data source; otherwise no rows.
• SELECT column_name FROM all_tab_columns WHERE table_name = 'OPM_SITE_USES_ALL'; — validates the exposed column contract.

For actual site-use data in an EBS environment, the populated source is normally the Receivables site-uses table (RA_SITE_USES_ALL) and its associated views. When investigating TAX_CLASSIFICATION, developers should confirm whether OPM_SITE_USES_ALL is a stub in their release and query the underlying transactional site-use table instead. Treating this view as a reporting source without verifying its content will yield no meaningful results.