Search Results jts_config_versions_vl

Overview

JTS_CONFIG_VERSIONS_VL is a seeded, VALID view owned by the APPS schema within Oracle E-Business Suite. It belongs to the JTS product family, which provides the CRM Self Service Administration foundation used by Oracle's self-service and configuration management modules. The view exposes configuration version records — the discrete, numbered iterations of a configuration definition — together with their lifecycle status, replay processing state, descriptive translation text, and standard EBS audit and descriptive flexfield columns.

The suffix _VL indicates a "view language" object. It is the translated, language-aware presentation layer over the underlying base entity. The view joins the base table to its translation table and filters on USERENV('LANG'), so consumers automatically receive Description text in the session's current language rather than in every installed language. This makes it the appropriate access point for Forms, OAF pages, concurrent programs, and custom reporting that must respect multilingual deployments.

Because it is a view and not a table, JTS_CONFIG_VERSIONS_VL holds no data of its own. It is a read-only projection. DML against configuration versions is performed against the underlying base and translation tables; the view is intended for query, reporting, and integration. In a 12.1.1 or 12.2.2 environment the object should be registered with a status of VALID in the APPS schema, with grants typically extended to the standard EBS access roles.

Underlying Base Objects

The documented view text defines the object over exactly two base tables in the APPS schema:

• JTS_CONFIG_VERSIONS_B — the base ("B") table holding the language-independent attributes of each configuration version, including identifiers, status codes, replay information, workflow queue name, audit columns, and the ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield segments.
• JTS_CONFIG_VERSIONS_TL — the translation ("TL") table holding the language-specific DESCRIPTION for each version, keyed by VERSION_ID and LANGUAGE.

The join is an inner equijoin on B.VERSION_ID = T.VERSION_ID restricted by T.LANGUAGE = USERENV('LANG'). The view supplies B.ROWID as ROW_ID, which preserves a pseudo-key for the base row. The ETRM 12.2.2 metadata lists no separately documented referenced base objects beyond what the view text itself reveals, so the two tables above are the authoritative dependency set. Any query performance characteristic of the view derives from the indexes on VERSION_ID in both tables and on LANGUAGE in the translation table.

Key Columns

• VERSION_ID — Primary identifier of the configuration version; the join key between base and translation tables.
• VERSION_NAME — Functional display name of the version.
• CONFIGURATION_ID — Foreign reference to the parent configuration to which this version belongs.
• VERSION_NUMBER — Sequential numbering that orders versions within a configuration.
• VERSION_STATUS_CODE — The lifecycle status of the version. Because no lookup view is joined in the exposed text, consumers normally resolve this code through the relevant JTS lookup type. This is the column referenced by searches for "version_status_code".
• REPLAY_STATUS_CODE, REPLAYED_ON, REPLAYED_BY — Track the replay (re-processing) state of the version, when it was replayed, and by which user.
• QUEUE_NAME — The advanced queue associated with version processing.
• DESCRIPTION — Translated descriptive text sourced from the TL table.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework for concurrent update detection.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segment values.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-columns for audit and incremental extraction.

Common Use Cases and Queries

Typical use cases include operational dashboards of configuration version status, replay monitoring, migration verification between environments, and integration extracts feeding external configuration repositories.

List all versions for a given configuration in version order:

• SELECT version_id, version_name, version_number, version_status_code FROM apps.jts_config_versions_vl WHERE configuration_id = :p_config_id ORDER BY version_number;

Monitor replay activity and identify versions that have not been replayed:

• SELECT version_id, version_name, replay_status_code, replayed_on, replayed_by FROM apps.jts_config_versions_vl WHERE replay_status_code IS NULL OR replayed_on IS NULL;

Incremental extraction based on the audit columns:

• SELECT version_id, version_name, version_status_code, last_update_date, last_updated_by FROM apps.jts_config_versions_vl WHERE last_update_date >= :p_since;

When filtering on VERSION_STATUS_CODE, resolve the code against the corresponding JTS lookup to present a user-friendly meaning in reports. All queries should be issued against the APPS-owned view; direct DML must target JTS_CONFIG_VERSIONS_B and JTS_CONFIG_VERSIONS_TL instead.