Search Results jts_configurations_vl

Overview

The view JTS_CONFIGURATIONS_VL belongs to the JTS product family, designated in Oracle E-Business Suite Release 12.1.1 and 12.2.2 as CRM Self Service Administration (Obsolete). It is a translated (VL, or "view label") view that presents configuration records maintained by the JTS self-service administration framework, joining base configuration data with language-specific descriptive text. The "_VL" suffix indicates that the view resolves translated columns according to the session language, exposing a single descriptive field (DESCRIPTION) selected from the translation table based on USERENV('LANG').

Because JTS Self Service Administration is marked Obsolete in the ETRM metadata, this view is not implemented in the current database instance, and Oracle documents it as reference-only. Its role in reporting and integration is therefore historical: in environments where the JTS schema objects still exist, the view provides a language-aware, flattened read interface over the configuration definitions used by the self-service administration module. In R12.1.1 and R12.2.2 databases where the object is absent, queries against it will fail with ORA-00942, and developers should treat it as a legacy artifact rather than an active interface.

Underlying Base Objects

Although the ETRM metadata lists no referenced base objects, the published view text defines the view over two tables:

• JTS_CONFIGURATIONS_B — the base (non-translated) table holding configuration identifiers, names, flow references, record mode, DFF attribute columns, and standard WHO audit columns.
• JTS_CONFIGURATIONS_TL — the translation table supplying the language-specific DESCRIPTION column.

The two are joined on CONFIGURATION_ID, with the translation filtered by T.LANGUAGE = USERENV('LANG'). The B and TL naming convention follows the standard Oracle multi-language schema pattern, in which the B table stores language-independent data and the TL table stores translated text keyed by language. The view's SELECT list explicitly enumerates every column from the B table along with DESCRIPTION from the TL table, using B.ROWID as ROW_ID.

Key Columns

• ROW_ID — the ROWID of the underlying base-table row, exposed for row identification.
• CONFIGURATION_ID — primary identifier for a configuration record; the join key between the B and TL tables.
• CONFIG_NAME — the configuration name, typically the user-facing identifier.
• FLOW_ID — reference to the flow associated with the configuration.
• RECORD_MODE — mode indicator governing how the configuration record is processed.
• DESCRIPTION — translated descriptive text resolved by session language.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework for concurrent update control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield (DFF) columns for customer-defined extension data.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking record creation and modification.

Common Use Cases and Queries

In legacy instances where the JTS objects survive an upgrade, the view supports configuration inventory reporting and integration extracts. A typical query lists configurations with their translated descriptions:

SELECT configuration_id,
       config_name,
       flow_id,
       record_mode,
       description
FROM   jts_configurations_vl
ORDER BY config_name;

Because the DESCRIPTION is language-resolved, the same query returns text in the session's language, making the view convenient for multi-language reporting without explicit joins to the TL table. Audit-oriented queries may select the WHO columns to trace recent configuration changes:

SELECT config_name,
       last_update_date,
       last_updated_by
FROM   jts_configurations_vl
WHERE  last_update_date >= TRUNC(SYSDATE) - 30;

Given the object's Obsolete status and documented absence from the database, these patterns apply only where the JTS configuration tables persist. In supported R12.1.1 and 12.2.2 environments, equivalent current functionality should be sourced from the active CRM self-service administration objects rather than from this view.