Results for “primary_salesrep_name”

50+ results




Overview
Explore in AI Chat

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

Overview

AR_SITE_USES_V is an APPS-owned view in the Oracle E-Business Suite Receivables (AR) module. Its documented description in the ETRM repository is limited to the note "(Release 11.5 Only)", indicating that the object was originally catalogued in the 11.5 documentation stream and has been retained, in a valid state, through the 12.1.1 and 12.2.2 releases. The view presents site-use level information: the operational attributes that describe how a particular customer account site is used for a specific business purpose, such as Bill-To, Ship-To, Sold-To, or Dunning. It is the reporting-facing projection of the HZ_CUST_SITE_USES base entity, enriched with lookups and denormalized descriptions.

In the Release 12 data model, customer site-use records reside in the Trading Community Architecture (TCA) tables HZ_CUST_SITE_USES and HZ_CUST_ACCT_SITES_ALL, rather than in the legacy AR tables used by 11.5. AR_SITE_USES_V provides a stable, read-only interface over that data, exposing translated lookup meanings and related descriptive columns. This makes it a convenient source for custom reports, inbound/outbound interfaces, and diagnostic queries that need site-use attributes without re-implementing the decode logic and joins against the TCA model.

Underlying Base Objects

The 12.2.2 metadata lists the following referenced objects: AR_LOOKUPS (VIEW), AR_RECEIVABLES_TRX (SYNONYM), FND_COMMON_LOOKUPS (VIEW), FND_GLOBAL (PACKAGE), HR_ALL_ORGANIZATION_UNITS (SYNONYM), HR_GENERAL (PACKAGE), HR_LOCATIONS (VIEW), HR_ORGANIZATION_UNITS (VIEW), HR_SECURITY (PACKAGE), HZ_CUST_ACCOUNT_ROLES (SYNONYM), HZ_CUST_SITE_USES (SYNONYM), HZ_PARTIES (SYNONYM), HZ_RELATIONSHIPS (SYNONYM), PO_LOCATION_ASSOCIATIONS (SYNONYM), QP_PRICE_LIST_PVT (PACKAGE), RA_SALESREPS (VIEW), RA_TERMS (SYNONYM), SO_LOOKUPS (SYNONYM), SO_ORDER_TYPES (SYNONYM), and SO_PRICE_LISTS (SYNONYM).

The principal driving object is HZ_CUST_SITE_USES, aliased as SU in the view text. HZ_CUST_ACCOUNT_ROLES and HZ_PARTIES supply contact-name information via a DECODE on the account role identifier. Lookup meanings are resolved through AR_LOOKUPS and FND_COMMON_LOOKUPS, joined by lookup code, while SO_LOOKUPS supplies order-management lookup values. HR_LOCATIONS, HR_ALL_ORGANIZATION_UNITS, and HR_ORGANIZATION_UNITS provide location and organization descriptions. RA_TERMS, SO_ORDER_TYPES, and SO_PRICE_LISTS contribute payment-term, order-type, and price-list names. HR_GENERAL and HR_SECURITY participate in organization security resolution, and FND_GLOBAL supplies runtime session context. QP_PRICE_LIST_PVT and AR_RECEIVABLES_TRX, PO_LOCATION_ASSOCIATIONS, and RA_SALESREPS appear as supporting references. The view text additionally exposes HRL.LOCATION_ID, HRL.LOCATION_CODE, and INV_ORG.ORGANIZATION_ID/NAME, along with the full ATTRIBUTE1–25 and GLOBAL_ATTRIBUTE1–16 flexfield columns.

Key Columns

Common Use Cases and Queries

Because the view resolves lookup meanings in the database rather than in application code, it is frequently used in reports that must display FOB point, freight terms, and shipping defaults for customer sites. A typical query filtering on the FOB lookup meaning is:

  • SELECT site_use_id, cust_acct_site_id, site_use_code, l_fob.meaning fob_meaning, fob_point FROM apps.ar_site_uses_v WHERE l_fob.meaning IS NOT NULL;
  • SELECT site_use_id, site_use_code, primary_flag, status, contact_name FROM apps.ar_site_uses_v WHERE status = 'A';
  • SELECT site_use_id, payment_term_id, name FROM apps.ar_site_uses_v WHERE site_use_code = 'BILL_TO';

Typical scenarios include customer master data extracts, ship-to/bill-to validation reports, order-entry default verification, and interfaces that feed downstream logistics or pricing systems with site-specific FOB, freight, warehouse, and price-list assignments.