Search Results bill_language

Overview

The AST_BILLING_PREFERENCES_V view is a TeleSales (AST) product database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to retrieve the billing preferences associated with a customer account. The view consolidates billing configuration data—such as billing language, currency, media format, number of invoice copies, and hold flags—into a single denormalized result set that reporting and integration layers can consume without joining multiple base objects themselves.

Because AST (TeleSales) shares the customer model with the Oracle Receivables and Trading Community Architecture (TCA) foundations, this view is relevant whenever a customer account's preferred invoicing attributes must be surfaced. The ETRM metadata records the view with a status of VALID under the APPS schema, confirming it is a supported, queryable object rather than an obsolete or invalidated artifact.

Underlying Base Objects

The view text joins the billing preferences table against several reference and lookup objects. The documented base objects are:

• HZ_BILLING_PREFERENCES (SYNONYM) — the primary transactional table storing per-account billing preference records.
• HZ_CUST_ACCOUNTS (SYNONYM) — the TCA customer account master, joined on CUST_ACCOUNT_ID.
• FND_LANGUAGES_VL (VIEW) — the languages lookup, joined on BILL_LANGUAGE using an outer join, exposing DESCRIPTION and NLS_LANGUAGE.
• FND_CURRENCIES_VL (VIEW) — the currencies lookup, joined on CURRENCY_CODE using an outer join, exposing NAME (aliased as CURRENCY_NAME).

The joins to FND_LANGUAGES_VL and FND_CURRENCIES_VL are outer joins (+), which means billing preference rows survive even when a language or currency code has no matching reference entry. The join to HZ_CUST_ACCOUNTS is an inner join, so only preferences tied to a valid customer account are returned. This design makes the view safe for reporting but means orphaned preference rows will be excluded.

Key Columns

The view exposes the following significant columns:

• ROW_ID — the ROWID of the underlying HZ_BILLING_PREFERENCES row, useful for row-level identification.
• CUST_ACCOUNT_ID / SITE_USE_ID — the customer account and site-level context for the preference.
• BILLING_PREFERENCES_ID — the primary key of the billing preference record.
• BILL_LANGUAGE, LANGUAGE_DESCRIPTION, NLS_LANGUAGE — the billing language code plus its descriptive and NLS language values from FND_LANGUAGES_VL.
• BILL_ROUND_NUMBER, BILL_TYPE, MEDIA_FORMAT, MEDIA_TYPE, NUMBER_OF_COPIES — invoicing presentation attributes controlling rounding, bill type, delivery media, and copy count.
• CURRENCY_CODE / CURRENCY_NAME — the billing currency and its descriptive name from FND_CURRENCIES_VL.
• HOLD_BILL_FLAG / HELD_BILL_EXPIRATION_DATE — indicate whether billing is held and, if so, until when.
• PAYMENT_TERM_ID — reference to the applicable payment term.
• Creation/audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include reconciling billing preferences across customer accounts, auditing hold flags, reviewing media format mix, and feeding downstream invoicing integrations. A representative query retrieving active preferences with resolved language and currency names follows:

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

Because the view performs the reference lookups, callers need only filter by account or site, avoiding direct joins to HZ_BILLING_PREFERENCES and the FND reference views. It is suitable for both ad hoc reporting and programmatic integration where a flattened, presentation-ready projection of billing preferences is required.