Results for “ar_standard_text_vl”

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

Overview

The AR_STANDARD_TEXT_VL view is a seeded, valid database object owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and functions as a multilingual (MLS) "VL" view — a translated view that presents standard text definitions alongside their language-specific text content for the session's active language. In the Oracle EBS naming convention, the "_VL" suffix indicates a view that joins a base ("_B") table with its translation ("_TL") table, exposing only the rows corresponding to the current runtime language.

The view supplies the reference data behind Oracle Receivables' standard text feature, which allows organizations to store and reuse configurable text blocks — such as dunning messages, invoice footer notes, statement messaging, and collection correspondence clauses. Because it resolves language automatically via USERENV('LANG'), it is the preferred object for reporting, integration, and concurrent programs that must display standard text in the user's own language without manually issuing join logic against the underlying tables.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two synonyms:

• AR_STANDARD_TEXT_B — the base table holding language-independent attributes of each standard text record, including identifiers, audit columns, effective dates, name, text type, use type, and the descriptive flexfield (DFF) attribute columns.
• AR_STANDARD_TEXT_TL — the translation table holding the actual TEXT content per language, keyed by STANDARD_TEXT_ID and LANGUAGE.

The view joins these two objects on STANDARD_TEXT_ID and filters the translation table with the condition T.LANGUAGE = USERENV('LANG'). It also exposes B.ROWID as ROW_ID, preserving row addressing from the base table. This join pattern is identical to other AR reference-data VL views and ensures a single row is returned per standard text record for the queried language.

Key Columns

• ROW_ID — the ROWID of the underlying base-table record; useful for direct row access.
• STANDARD_TEXT_ID — the primary key linking base and translation records.
• NAME — the user-defined identifier/name of the standard text.
• TEXT_TYPE and TEXT_USE_TYPE — classify the standard text by category and intended use (for example, dunning or statement text).
• TEXT — the language-specific content retrieved from AR_STANDARD_TEXT_TL.
• START_DATE and END_DATE — effective dating for the standard text record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns for extensible, customer-defined data.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns for change tracking.

Common Use Cases and Queries

Typical scenarios include building BI Publisher or Oracle Reports output that must render collection or dunning text in the user's language, and integration routines that must fetch the correct translated text block for outbound correspondence. A representative query listing active standard text by use type is:

• SELECT standard_text_id, name, text_type, text_use_type, text FROM ar_standard_text_vl WHERE text_use_type = :p_use_type AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
• SELECT text FROM ar_standard_text_vl WHERE name = :p_name;
• SELECT standard_text_id, name, text FROM ar_standard_text_vl WHERE text_type = :p_type ORDER BY name;

Because the view filters on the session language, callers must ensure the correct language context (for example, via FND session initialization) before executing queries to avoid returning no translation rows. The absence of a matching AR_STANDARD_TEXT_TL row for the active language causes the standard text to be excluded from the result set.