Results for “text_use_type”

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

Overview

AR_STANDARD_TEXT_B is the Receivables (AR) standard text base table, owned by the AR schema. It stores the reusable standard statement messages and related text definitions that Oracle Receivables uses for dunning letters, statement messages, and other configurable customer-facing communications. The table serves as the multilingual base container: installable translations reside in the companion AR_STANDARD_TEXT_TL table, while the base table holds language-independent attributes, usage classification, and effective-dating information.

From a modeling perspective, ETRM's heuristic Data Vault classification is hub-leaning. Operationally, this means STANDARD_TEXT_ID functions as a stable business key around which descriptive and descriptive-effective-dated attributes are attached, with dependent satellite-style attributes (NAME, TEXT_TYPE, TEXT_USE_TYPE, START_DATE, END_DATE, and the ATTRIBUTE1–15 descriptive flexfield columns) varying over time. Downstream legacy Brazilian localization tables treat this row as a referenced hub via MESSAGE_ID.

The object is documented as VALID and contains 28 physical columns in the 12.2.2 schema. It is a setup/configuration table rather than a transactional table, so its row counts are typically low (hundreds) and its DML activity is concentrated in implementation and periodic maintenance windows.

Key Information Stored

The most significant columns documented for this table are:

• STANDARD_TEXT_ID — surrogate primary key (AR_STANDARD_TEXT_B_PK) and the value exposed to dependent tables as MESSAGE_ID. It is also the leading column of the unique business-key candidate AR_STANDARD_TEXT_B_U1 (STANDARD_TEXT_ID, ZD_EDITION_NAME).
• ZD_EDITION_NAME — the edition/version discriminator added by the Online Patching (ad/zd) architecture in EBS 12.2.2; combined with STANDARD_TEXT_ID it forms the unique index U1 and is essential for correct querying under multi-tenant/editioned access.
• NAME — the internal name of the standard text reference.
• TEXT_TYPE — classifies the kind of text stored (for example, statement message versus dunning letter text).
• TEXT_USE_TYPE — indicates where the text is applied within the AutoInvoice, dunning, or statement flow.
• START_DATE and END_DATE — effective-dating range that governs whether the message is active for a given business date.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns for audit and change tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield (DFF) context and segment columns used for user-defined extensions described in the metadata.

Common Use Cases and Queries

The table is chiefly queried to enumerate configured statement and dunning messages, to filter active messages by date, and to resolve the message identifiers consumed by the Brazilian localization tables. Typical patterns include:

• Listing active messages as of a business date: SELECT standard_text_id, name, text_type, text_use_type FROM ar.ar_standard_text_b WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);
• Joining to translations in AR_STANDARD_TEXT_TL on STANDARD_TEXT_ID to obtain user-facing text in a specific language.
• Reporting on message usage classification grouped by TEXT_TYPE and TEXT_USE_TYPE.
• Reconciling localization references, for example joining JL_BR_TAX_LMSG_ALL.MESSAGE_ID back to AR_STANDARD_TEXT_B.STANDARD_TEXT_ID to identify messages consumed by Brazilian tax legal messages.
• Extracting user-defined DFF context values via ATTRIBUTE_CATEGORY and the ATTRIBUTE1–15 columns.

Because statements execute against the base table on the application tier, queries should consistently include the ZD_EDITION_NAME constraint under 12.2.2 to return only the active edition.

Related Objects

The following objects reference or depend on AR_STANDARD_TEXT_B, using the join columns shown:

• JL_BR_TAX_LMSG_ALL — references AR_STANDARD_TEXT_B via MESSAGE_ID → STANDARD_TEXT_ID.
• JL_ZZ_AR_TX_LGL_MSG_ALL — references AR_STANDARD_TEXT_B via MESSAGE_ID → STANDARD_TEXT_ID.
• AR_STANDARD_TEXT_TL — the translated-text child table, keyed by STANDARD_TEXT_ID and language, supplying the rendition displayed to users.
• AR statement and dunning generation logic, which reads active rows filtered by START_DATE and END_DATE.
• Receivables DFF setup, which drives ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 usage.