Search Results active_status

Overview

The CS_FORUM_MESSAGES_VL view is a multi-lingual (ML) reporting view owned by the APPS schema in Oracle E-Business Suite release 12.1.1 and 12.2.2. It belongs to the CS (Service) product family and provides a single, translated read interface over the forum message data stored in the CS_FORUM_MESSAGES_B and CS_FORUM_MESSAGES_TL tables. The "_VL" suffix denotes a view that joins a base table (_B) with its translation table (_TL), automatically resolving the language-specific columns for the session's current language.

Because it exposes both the transactional attributes held on the base table and the translated descriptive columns, the view is the standard object used for reporting, inquiry, and integration against Service forum messages without requiring callers to manage the _B/_TL join themselves. It carries the standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and a descriptive flexfield segment set (ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15), making it suitable for concurrent programs, BI Publisher reports, and outbound interfaces.

Underlying Base Objects

Per the ETRM metadata, the view is defined over two referenced base objects, both resolved through APPS synonyms:

• CS_FORUM_MESSAGES_B — the base table holding the language-independent (non-translatable) message attributes such as identifiers, posting information, status, and flexfield values.
• CS_FORUM_MESSAGES_TL — the translation table holding the language-dependent text columns (NAME, DESCRIPTION) keyed by MESSAGE_ID and LANGUAGE.

The view text joins the two on B.MESSAGE_ID = T.MESSAGE_ID and filters T.LANGUAGE = USERENV('LANG'), so each row is returned only in the language of the current session. This is the mechanism that makes the view "multi-lingual": a French-language session sees the French translation, while an English-language session sees the English translation, using the same query.

Key Columns

The view projects 34 columns. The most significant include:

• ROW_ID — the base table rowid, exposed from CS_FORUM_MESSAGES_B; useful as a surrogate for updates.
• MESSAGE_ID — the primary key linking base and translation rows.
• MESSAGE_NUMBER and MESSAGE_NAME — the message identifier and internal name.
• POSTED_USER and POSTED_DATE — who posted the message and when.
• MESSAGE_TYPE and DISTRIBUTION_TYPE — classify the message and govern how it is distributed.
• NAME and DESCRIPTION — the translated descriptive text drawn from the _TL table.
• ACTIVE_STATUS — the enabled/disabled flag on the message; this is the column most relevant to the "active_status" search, and it is one of the primary filtering attributes for identifying currently usable messages.
• COMPOSITE_ASSOC_COL — the composite association column projected from the _TL table.

Common Use Cases and Queries

Typical uses include listing active forum messages, auditing message configuration, and feeding message metadata into integrations. A representative query that addresses the "active_status" search is:

• SELECT message_id, message_number, name, active_status, posted_date FROM cs_forum_messages_vl WHERE active_status = 'Y';
• SELECT m.message_id, m.name, m.description FROM cs_forum_messages_vl m WHERE m.active_status = 'Y' AND m.message_type = :p_type ORDER BY m.name;
• SELECT m.message_number, m.posted_user, m.posted_date FROM cs_forum_messages_vl m WHERE m.posted_date >= :p_from_date;

Because the view is a query-only object, it supports reporting and integration safely; all DML must target the underlying _B/_TL tables. Queries are automatically language-filtered, so no explicit LANGUAGE predicate is required.