Results for “csc_acct_site_uses_v”

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

Overview

The CSC_ACCT_SITE_USES_V view is an APPS-owned database view in the Oracle E-Business Suite Customer Care (CSC) module. It is a denormalized, reporting-friendly projection of customer account site uses that joins the underlying site use records to the Accounts Receivable lookup definitions, so that a caller can retrieve the descriptive meaning of every site use code without performing the lookup join itself.

Because CSC spans multiple functional areas — order capture, service, contact center, and collections — the view exists to provide a stable, product-neutral read interface over the Accounts Receivable customer site use model. Users searching for site_use_code typically arrive at this object when they need to enumerate, filter, or describe the roles that a customer account site plays, such as Bill-To, Ship-To, Statement-To, and Dunning. The view is registered as VALID in the APPS schema and is exposed for direct query, making it suitable for custom reports, concurrent programs, OAF/ADF extensions, and integration extracts.

Underlying Base Objects

Documented ETRM metadata lists the referenced base objects as AR_LOOKUPS (VIEW), HR_OPERATING_UNITS (VIEW), and HZ_CUST_SITE_USES (SYNONYM). The view text confirms the core join relationship: HZ_CUST_SITE_USES_ALL supplies the site use records, while AR_LOOKUPS supplies the lookup meaning.

Specifically, the join condition is:

• CUST.SITE_USE_CODE = LOOKUP.LOOKUP_CODE
• LOOKUP.LOOKUP_TYPE = 'SITE_USE_CODE'

The synonym HZ_CUST_SITE_USES resolves to the customer site uses entity, and AR_LOOKUPS resolves to the lookup definitions that carry the seeded and user-defined site use codes. HR_OPERATING_UNITS is referenced as a supporting base object, consistent with the operating unit context under which customer site uses are partitioned in multi-org EBS installations. The view therefore inherits the multi-org and lookup-driven semantics of its base objects, and results are sensitive to the operating unit and lookup set in effect at query time.

Key Columns

The view exposes the following principal columns:

• SITE_USE_CODE — The code defining the site use, joined to the SITE_USE_CODE lookup type. This is the column central to the user's search.
• SITE_USE_MEANING — The descriptive meaning of the site use code, sourced from AR_LOOKUPS.MEANING.
• SITE_USE_ID — Primary identifier of the site use record.
• CUST_ACCT_SITE_ID — Identifier of the customer account site to which the site use belongs.
• BILL_TO_SITE_USE_ID — Reference to the associated Bill-To site use, where applicable.
• PRIMARY_FLAG — Indicates whether the site use is the primary use for its purpose.
• STATUS — Active/inactive status of the site use record.
• LOCATION — Location reference associated with the site use.
• ROW_ID — Row identifier exposed as ROW_ID in the column list (ROWID in the view text).
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard EBS descriptive flexfield columns, available for customer-defined extensions.

Common Use Cases and Queries

Typical scenarios include validating site use assignments for a customer account, extracting Bill-To or Ship-To relationships for an integration, and reporting on the descriptive meaning of site use codes for end users.

Example — list all site uses with meanings:

• SELECT site_use_id, cust_acct_site_id, site_use_code, site_use_meaning, primary_flag, status FROM csc_acct_site_uses_v WHERE status = 'A';

Example — filter by a specific site use code:

• SELECT site_use_id, cust_acct_site_id, site_use_meaning FROM csc_acct_site_uses_v WHERE site_use_code = 'BILL_TO';

Example — retrieve the primary site use for an account site:

• SELECT site_use_id, site_use_code, site_use_meaning FROM csc_acct_site_uses_v WHERE cust_acct_site_id = :p_site_id AND primary_flag = 'Y';

Because the view already resolves the lookup meaning, consumers avoid re-implementing the AR_LOOKUPS join, ensuring consistency with the seeded SITE_USE_CODE lookup set across Oracle EBS 12.1.1 and 12.2.2.