Search Results jts_config_versions_b




Overview
Explore in AI Chat

Overview

JTS_CONFIG_VERSIONS_B is a transactional table owned by the JTS schema, which corresponds to the CRM Self Service Administration module. The object stores configuration versions as described on the Version Summary page of the ETRM self-service configuration framework. Within the broader Oracle E-Business Suite architecture, it functions as the persistent record of a named configuration version, including its lifecycle state, queue assignment, replay status, and descriptive flexfield context.

The ETRM classification for this object is noted as obsolete in release 12.1.1 and 12.2.2, and the implementation/DBA note states that it is not implemented in this database. This is significant: the table definition is retained for schema compatibility and upgrade paths, but no application logic in the current release actively writes to or reads from it. Consultants encountering the object should treat it as a legacy artifact rather than an operational data source.

Under a heuristic Data Vault classification, JTS_CONFIG_VERSIONS_B is modeled as a standalone object, meaning the mined foreign-key structure does not place it as a dependent satellite of a single parent hub. It carries its own surrogate key and business key, and references external entities (VEA_VERSIONS and FND_SECURITY_GROUPS) through foreign keys, which suggests a hub-like anchoring role with descriptive attributes attached.

Key Information Stored

The documented physical schema for 12.1.1 lists 32 columns. The most operationally meaningful are:

Common Use Cases and Queries

Because the object is not implemented in the current database, most practical activity involves confirming its absence or analyzing historical extracts. A typical verification query checks whether the table exists and holds rows in the target environment.

  • Inventory check: SELECT COUNT(*) FROM jts_config_versions_b; against the JTS schema.
  • Join to the parent version registry using the documented foreign key: SELECT c.VERSION_ID, c.VERSION_NAME, v.* FROM jts_config_versions_b c, vea_versions v WHERE c.VERSION_ID = v.VERSION_ID;
  • Security group reporting: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to attribute configuration versions to a security partition.
  • Replay audit: filter on REPLAY_STATUS_CODE and REPLAYED_ON to reconstruct historical replay activity during migration or upgrade testing.
  • Flexfield reporting: query ATTRIBUTE_CATEGORY together with ATTRIBUTE1 through ATTRIBUTE15 when analyzing legacy descriptive data.

Related Objects

The foreign-key metadata identifies the principal dependencies of JTS_CONFIG_VERSIONS_B:

  • VEA_VERSIONS — referenced through VERSION_ID; the primary external anchor for version identity.
  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; provides the security partitioning context.
  • The configuration parent implied by CONFIGURATION_ID, forming the U2 business key alongside VERSION_NAME.
  • Standard EBS WHO columns integrate with FND_USER and FND_LOGINS for user and session attribution.

Given the obsolete status, no active JTS self-service API or concurrent program in 12.1.1 or 12.2.2 is expected to depend on this table at runtime. It should be treated strictly as a reference object when interpreting legacy schema documentation.