Search Results jts_configurations_b_u1

Overview

The table JTS.JTS_CONFIGURATIONS_B is the core configuration registry of the Oracle E-Business Suite JTS (Configuration Management / "My Configurations") product family. As documented in the ETRM repository for release 12.1.1 and validated in 12.2.2, the object is owned by the JTS schema, carries a status of VALID, and is physically stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. Its documented purpose is to "Store Configurations data," and it is described as the starting point for Configuration Management as surfaced through the My Configurations page. In practical terms, every configuration record that an end user creates, versions, or retrieves through that UI is anchored to a row in this table.

The metadata assigns a heuristic Data Vault classification of standalone, derived from the mined foreign-key structure. This suggests modeling the object as an independent hub rather than as a link or satellite, because it participates in no parent-child relationships among the mined objects other than the single FND reference noted below. Its unique business keys make it suitable as a hub anchor in a raw-vault layer, while its descriptive attributes would normally be split into a companion satellite.

Key Information Stored

The table contains 27 documented columns. The most significant are:

• CONFIGURATION_ID — the numeric surrogate primary key. It is enforced by the unique index JTS_CONFIGURATIONS_B_U1 on APPS_TS_TX_IDX.
• CONFIG_NAME — the user-visible configuration name (VARCHAR2(80)). It is the second business-key candidate, enforced by the unique index JTS_CONFIGURATIONS_B_U2, which is the index referenced in the user's search term.
• FLOW_ID — the identifier linking the configuration to its defining flow. A non-unique index, JTS_CONFIGURATIONS_B_N1, supports lookups by this column.
• RECORD_MODE — VARCHAR2(30) describing how the configuration payload is persisted; documented values include xml, db, and xmldb.
• OBJECT_VERSION_NUMBER — the standard optimistic-locking column used by the Oracle Application Framework to detect concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF/descriptive flexfield segment set for extensibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.
• SECURITY_GROUP_ID — the security-group discriminator, referencing FND_SECURITY_GROUPS.

Common Use Cases and Queries

Typical reporting and support queries resolve a configuration by name or list configurations per flow. For example, locating a configuration by its business name:

SELECT configuration_id, config_name, flow_id, record_mode FROM jts.jts_configurations_b WHERE config_name = :p_name;

Listing all configurations attached to a given flow, using the N1 index:

SELECT configuration_id, config_name, record_mode FROM jts.jts_configurations_b WHERE flow_id = :p_flow_id ORDER BY config_name;

Diagnosing stale rows or audit issues uses the WHO columns:

SELECT configuration_id, config_name, last_update_date, last_updated_by FROM jts.jts_configurations_b WHERE last_update_date > SYSDATE - 30;

A common support check is verifying uniqueness of CONFIG_NAME after a failed creation, since JTS_CONFIGURATIONS_B_U2 will raise ORA-00001 on duplicate insert. Join work usually pairs this table with its translation table via CONFIGURATION_ID and with flow metadata via FLOW_ID.

Related Objects

• FND_SECURITY_GROUPS — referenced through the documented foreign key JTS_CONFIGURATIONS_B.SECURITY_GROUP_ID → FND_SECURITY_GROUPS (almost certainly SECURITY_GROUP_ID).
• JTS_CONFIGURATIONS_TL — the translation table holding language-specific CONFIG_NAME descriptions, joined on CONFIGURATION_ID.
• JTS_CONFIGURATIONS_B dependent entities (config line/detail tables) — joined on CONFIGURATION_ID.
• Flow metadata tables — joined on FLOW_ID via the non-unique JTS_CONFIGURATIONS_B_N1 index.
• FND_USER — implicit join for CREATED_BY / LAST_UPDATED_BY display.