Results for “site_use”

50+ results




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

Overview

AR_CMGT_PARTY_ACCOUNTS is a reporting view owned by the APPS schema and registered under the Oracle Receivables (AR) product. It is part of the customer management (CMGT) family of views used by the Receivables Customer Management subsystem, and it presents a denormalized, query-friendly picture of customer accounts, parties, addresses, and site usages. A user searching for the term "bill_to" arrives at this view because it is one of the canonical sources that expose the BILL_TO site-use designation for a customer account in a single SELECT statement.

The view consolidates data from the Oracle Trading Community Architecture (TCA) model — parties, customer accounts, account sites, party sites, locations, and site uses — and returns one row per address/site combination plus an additional roll-up row per account. The DETAILS_LEVEL column distinguishes these two levels of granularity: rows with a value of 'SITE' represent a specific customer account site, while rows with 'ACCOUNT' represent the account header. This makes the view suitable both for address-level reporting and for account-level summaries.

Underlying Base Objects

The documented base objects referenced by AR_CMGT_PARTY_ACCOUNTS are:

The join logic requires the account to be active (CA.STATUS = 'A'), the account site to be active (CAS.STATUS = 'A'), and the account site to carry a BILL_TO_FLAG of 'Y' or 'P' (primary). A UNION ALL then appends distinct account-level rows so that accounts without qualifying bill-to sites still appear with DETAILS_LEVEL = 'ACCOUNT'.

Key Columns

  • ACCOUNT_NUMBER / ACCOUNT_NAME — the customer account identifier and description.
  • PARTY_ID / PARTY_NAME / PARTY_NUMBER — the owning party and its human-readable identifiers.
  • SITE_USE — a DECODE-derived label; values include 'BILL_TO', 'MARKET', or 'SHIP_TO', derived from the BILL_TO_FLAG, MARKET_FLAG, and SHIP_TO_FLAG on the account site.
  • CUST_ACCT_SITE_ID / CUST_ACCOUNT_ID / SITE_USE_ID — the surrogate keys used for joins back to TCA tables.
  • CONCATENATED_ADDRESS / ADDRESS / CITY / STATE / PROVINCE / POSTAL_CODE / COUNTRY — formatted and component address values produced via ARP_ADDR_PKG.FORMAT_ADDRESS.
  • DETAILS_LEVEL — 'SITE' or 'ACCOUNT', indicating the row's granularity; account-level rows carry sentinel values such as -99.
  • PRIMARY_SALESREP_ID / ORG_ID — sales representative and operating unit context, used for multi-org reporting.

Common Use Cases and Queries

The view is most commonly used to list bill-to addresses for a customer or party, to feed downstream integrations, or to validate site-use assignments. A typical query filtering on the bill-to designation is:

SELECT account_number, party_name, site_use, concatenated_address
FROM ar_cmgt_party_accounts
WHERE site_use = 'BILL_TO'
ORDER BY account_number;

To restrict by party, apply a predicate on PARTY_ID or PARTY_NUMBER. To retrieve only address-level rows, add WHERE details_level = 'SITE'; to obtain account headers, use WHERE details_level = 'ACCOUNT'. Because the view joins active records only, it is well suited for current-state reporting; historical or inactive records must be sourced from the underlying TCA tables directly.