Search Results l_fob




Overview
Explore in AI Chat

Overview

APPS.AR_SITE_USES_V is a reporting and integration view in Oracle E-Business Suite Releases 12.1.1 and 12.2.2 that exposes customer site use information maintained by Receivables. A "site use" represents a specific business purpose associated with a customer account site — for example a Bill-To, Ship-To, Statement-To, or Dunning site use — and carries the operational defaults used by Order Management, Shipping, Pricing, and Receivables when transactions are entered for that customer location.

The view's primary role is to denormalize the normalized Trading Community Architecture (TCA) model into a flat, human-readable structure. The base table HZ_CUST_SITE_USES stores foreign key identifiers (site use codes, FOB point codes, freight terms, payment terms, price lists, order types, warehouse organizations, and sales territories), whereas the view resolves each of these into its corresponding descriptive meaning through joins to lookup, party, and setup entities. This makes the view suitable for direct querying in reports, interfaces, and outbound integrations without requiring report authors to reconstruct TCA relationships.

Because the view is owned by APPS and is defined over TCA and shared setup objects, it is secured by the standard Oracle EBS organization and party security model. Access is therefore implicitly filtered by the responsibility-level security profile, and the view should be treated as a read-only, point-in-time projection rather than a DML target.

Underlying Base Objects

The view is defined primarily over the synonym HZ_CUST_SITE_USES, aliased as SU, which supplies the core site use rows and the ROWID and SITE_USE_ID used for identification. The account-level context is obtained through HZ_CUST_ACCOUNT_ROLES, HZ_PARTIES, and HZ_RELATIONSHIPS, which together yield the contact name exposed through the DECODE on CUST_ACCOUNT_ROLE_ID and the concatenation of PERSON_LAST_NAME and PERSON_FIRST_NAME.

Descriptive meanings for the various coded columns are resolved through AR_LOOKUPS, FND_COMMON_LOOKUPS, and SO_LOOKUPS — the latter used for the FOB point and freight term lookups — while operational setup is resolved through SYNONYM objects including RA_TERMS (payment terms), SO_ORDER_TYPES (order type), SO_PRICE_LISTS (price list), and HR_ALL_ORGANIZATION_UNITS (warehouse). Location and organization details are drawn from HR_LOCATIONS, HR_ORGANIZATION_UNITS, and HR_GENERAL, with HR_SECURITY enforcing row-level access. Pricing validation logic is referenced through the QP_PRICE_LIST_PVT package, and RA_SALESREPS, AR_RECEIVABLES_TRX, and PO_LOCATION_ASSOCIATIONS are also referenced. FND_GLOBAL supplies session context attributes.

Key Columns

Common Use Cases and Queries

A frequent requirement is to report the shipping defaults configured per ship-to site use. The following query lists active ship-to site uses with their FOB point, freight terms, and warehouse:

SELECT site_use_id, address_id, site_use_code, meaning,
       fob_point, fob_point%TYPE, freight_term, warehouse_id, org_name
FROM apps.ar_site_uses_v
WHERE site_use_code = 'SHIP_TO'
  AND status = 'A';

Because the view decodes FOB point through L_FOB.MEANING, it is the appropriate source when searching for l_fob values — for example, to retrieve the FOB description alongside the raw code for a given customer site. A second common scenario verifies inbound order defaulting: joining ORDER_TYPE_ID and PRICE_LIST_ID to confirm that each customer ship-to resolves to a valid order type and price list before order import. Third, integrations exporting customer master data frequently select from this view to flatten TCA site uses into a single extract, including the ATTRIBUTE and GLOBAL_ATTRIBUTE columns required to carry customer-specific descriptive flexfield values. In all cases, queries should filter on STATUS and, where applicable, on PRIMARY_FLAG to avoid returning inactive or secondary site uses.