Results for “fm_text_tbl”

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

Overview

APPS.FM_TEXT_TBL_VL is a language-specific (VL, "view layer") Oracle E-Business Suite view owned by the APPS schema. It exposes translated text fragments maintained in the Oracle EBS text repository, which is used to store paragraph-level and line-level textual content referenced by application code rather than being entered by end users at runtime. In Oracle EBS 12.1.1 and 12.2.2, the view is one of the standard report-building objects used by Oracle Reports, BI Publisher, and custom concurrent programs that need to resolve a text code into its localized display text.

The view is not a transactional entity. It is a lookup/translation view whose behavior is governed by the session language, meaning the same query returns different rows depending on the value of USERENV('LANG') for the current database session. This design is consistent with the broader EBS multi-language architecture, in which the _TL (translation) table holds one row per installed language and the _VL view restricts that data to the runtime language.

Underlying Base Objects

The view is defined over a single base object, documented in the ETRM metadata as the synonym FM_TEXT_TBL_TL. The view text is:

• SELECT B.ROWID ROW_ID, B.TEXT_CODE, B.LANG_CODE, B.PARAGRAPH_CODE, B.SUB_PARACODE, B.LINE_NO, B.LAST_UPDATED_BY, B.CREATED_BY, B.LAST_UPDATE_DATE, B.CREATION_DATE, B.LAST_UPDATE_LOGIN, B.TEXT FROM FM_TEXT_TBL_TL B WHERE B.LANGUAGE = USERENV('LANG')

The _TL suffix denotes the translation table, which stores the same logical text record replicated across every installed language, each row distinguished by its LANGUAGE column. The _VL suffix denotes the view layer that filters this translation table by the session language. The synonym FM_TEXT_TBL_TL resolves to the underlying application table owned by the Oracle Forms/FM product family, and the view is created in the APPS schema so that it is accessible to all EBS responsibilities without additional grants.

Because the view is defined as a filtered join on the translation table, there is no separate _B (base) table referenced in the documented definition. The row identity exposed as ROW_ID is derived from the ROWID of the underlying translation row, not from a primary key column, which is significant for any code that attempts to use ROW_ID as a stable identifier.

Key Columns

• TEXT_CODE — The logical identifier for the text fragment. Application code and reports join to this view using TEXT_CODE to retrieve the correct localized string.
• LANG_CODE — The language code of the row. In the view definition, this is returned from the base table; the filter is applied on the separate LANGUAGE column.
• PARAGRAPH_CODE — Identifies the paragraph grouping to which the text line belongs, allowing multi-line text to be reconstructed in the correct sequence.
• SUB_PARACODE — Sub-paragraph identifier, providing finer-grained ordering within a paragraph.
• LINE_NO — The line sequence number within the paragraph/sub-paragraph grouping. Combined with PARAGRAPH_CODE and SUB_PARACODE, it defines the display order of the text.
• TEXT — The actual text content in the session language. This is the column typically consumed by reports and integrations.
• ROW_ID — The ROWID of the underlying FM_TEXT_TBL_TL row, exposed under the alias ROW_ID.
• LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns, inherited from the base translation table and useful for tracking when a translated text fragment was last maintained.

Common Use Cases and Queries

The primary use case is retrieval of localized text for report output and integration payloads. A typical query selects the text content for a known code, ordered by paragraph and line:

• SELECT text_code, paragraph_code, sub_paracode, line_no, text FROM apps.fm_text_tbl_vl WHERE text_code = :p_text_code ORDER BY paragraph_code, sub_paracode, line_no;

Because the view filters on USERENV('LANG'), no explicit language predicate is required; the result automatically matches the session language. For multilingual reporting, a developer may instead query the base translation table directly to retrieve all languages.

A second use case is reconstructing multi-line text blocks, sensitive to paragraph and subparagraph grouping:

• SELECT paragraph_code, sub_paracode, line_no, text FROM apps.fm_text_tbl_vl WHERE text_code = :p_code ORDER BY paragraph_code, sub_paracode, line_no;

A third use case is auditing translation maintenance, using the inherited audit columns:

• SELECT text_code, lang_code, last_updated_by, last_update_date FROM apps.fm_text_tbl_vl WHERE last_update_date >= :p_since;

Note that the user search term "como pasar un audio a texto" (how to convert audio to text) is unrelated to this view. FM_TEXT_TBL_VL stores pre-existing text fragments; it performs no speech-to-text or audio transcription. Any expectation that this view provides audio conversion is incorrect. The view is purely a localized text-retrieval layer within the Oracle EBS Forms/FM schema.