Search Results csc_billing_preferences_v




Overview
Explore in AI Chat

Overview

CSC_BILLING_PREFERENCES_V is an APPS-owned database view within the Oracle E-Business Suite Customer Care (CSC) product family. Its documented purpose is to retrieve billing preferences for a customer account. In Oracle EBS 12.1.1 and 12.2.2, the object is registered as a VALID view in the APPS schema, making it available to reporting tools, concurrent programs, and integration interfaces that operate within the EBS database tier.

The view functions as a denormalized read layer over the transactional billing preferences data stored in HZ_BILLING_PREFERENCES. Rather than requiring report authors and integration developers to join the base preferences table to customer, language, and currency reference data manually, the view performs those joins and exposes a single, report-ready result set. This is consistent with the broader EBS design pattern in which "_V" views simplify downstream consumption while preserving the normalized storage model underneath.

Because the view is defined with outer joins to the language and currency lookup views, a billing preference record remains visible even when its language code or currency code does not resolve to a valid reference row. This behavior is important for completeness in reporting, since it prevents silently dropping preference rows that reference obsolete or unmaintained lookup codes.

Underlying Base Objects

The view text is defined over four referenced objects, as documented in the ETRM 12.2.2 metadata:

  • HZ_BILLING_PREFERENCES (SYNONYM) — the driving table, aliased BILL. It supplies all billing preference attributes, including round number, bill type, media format, media type, number of copies, hold flags, and audit columns.
  • HZ_CUST_ACCOUNTS (SYNONYM) — aliased CUST. It is inner-joined to the preferences table on CUST_ACCOUNT_ID, ensuring that only preferences tied to a valid customer account are returned.
  • FND_LANGUAGES_VL (VIEW) — aliased LANG. It is outer-joined on BILL_LANGUAGE = LANGUAGE_CODE to resolve the language description and NLS language.
  • FND_CURRENCIES_VL (VIEW) — aliased CURRENCY. It is outer-joined on CURRENCY_CODE to resolve the currency name.

The join structure therefore consists of one inner join (customer account) and two outer joins (language and currency), with the billing preferences table at the center of the query.

Key Columns

Common Use Cases and Queries

The view is typically used to report billing configuration by account, to feed outbound document generation, and to audit hold flags and media settings across a customer base.

SELECT cust_account_id,
       billing_preferences_id,
       bill_language,
       language_description,
       bill_type,
       media_type,
       number_of_copies,
       currency_code,
       currency_name,
       hold_bill_flag,
       held_bill_expiration_date
FROM   apps.csc_billing_preferences_v
WHERE  cust_account_id = :p_cust_account_id;

A second common pattern is identifying accounts with active billing holds:

SELECT cust_account_id, hold_bill_flag, held_bill_expiration_date
FROM   apps.csc_billing_preferences_v
WHERE  hold_bill_flag = 'Y'
AND    (held_bill_expiration_date IS NULL
        OR held_bill_expiration_date > SYSDATE);

Because the underlying objects are synonyms and views rather than tables with row-level security, queries should be restricted by customer account or operating unit context appropriate to the deployment. As with all APPS reporting views, direct DML against the view is not supported; changes to billing preferences must be made through the Customer Care application or the underlying HZ_BILLING_PREFERENCES table APIs.