Search Results jts_configurations_b




Overview
Explore in AI Chat

Overview

The table JTS_CONFIGURATIONS_B resides in the JTS schema and belongs to the CRM Self Service Administration product within Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores configuration data and serves as the starting point for configuration management as presented on the My Configuration page of the self-service administrative interface. In practical terms, each row in this table represents a named configuration definition that the application uses to drive the display and behavior of configuration records accessible to end users.

The ETRM metadata classifies this object as standalone, with no foreign keys pointing outward except a reference to FND_SECURITY_GROUPS through SECURITY_GROUP_ID. From a Data Vault modeling perspective, this object is best characterized as a hub: it holds a durable business key (CONFIG_NAME) plus a surrogate identifier (CONFIGURATION_ID), which is the classic pattern for a hub entity. The remaining descriptive and audit columns behave as satellite-style attributes attached to that hub, though the physical implementation follows the standard EBS single-table convention rather than a normalized Data Vault schema.

Key Information Stored

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

  • CONFIGURATION_ID — the surrogate primary key, enforced by unique index JTS_CONFIGURATIONS_B_U1. This is the internal identifier used by all dependent records.
  • CONFIG_NAME — the business-key candidate, enforced by unique index JTS_CONFIGURATIONS_B_U2. This is the human-readable name shown on the My Configuration page.
  • FLOW_ID — identifies the workflow or processing flow associated with the configuration.
  • RECORD_MODE — indicates the operational mode under which the configuration record is processed.
  • OBJECT_VERSION_NUMBER — supports optimistic locking and concurrent update control, a standard EBS 12.2.x pattern.
  • SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, controlling which security group may access the configuration.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns, reserved for customer-defined extensions.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns that track record provenance and change history.

Common Use Cases and Queries

Typical usage centers on configuration lookup, security validation, and audit reporting. A simple retrieval by business key follows this pattern:

  • SELECT configuration_id, config_name, flow_id, record_mode FROM jts.jts_configurations_b WHERE config_name = :p_name;
  • SELECT c.config_name, g.security_group_name FROM jts.jts_configurations_b c, fnd_security_groups g WHERE c.security_group_id = g.security_group_id;
  • SELECT config_name, creation_date, created_by, last_update_date FROM jts.jts_configurations_b WHERE last_update_date >= :p_since ORDER BY last_update_date DESC;

Reporting scenarios include inventorying all defined configurations per security group, auditing changes for compliance, and diagnosing missing or misconfigured entries when the My Configuration page does not render expected records. Because CONFIG_NAME is uniquely indexed, direct joins between external reference data and this table are reliable without risk of fan-out.

Related Objects

The following objects are most significant in relation to JTS_CONFIGURATIONS_B:

  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs access to each configuration.
  • JTS_CONFIGURATIONS_TL — the translated (language) companion table, typical for EBS objects whose names are localized, joined on CONFIGURATION_ID.
  • JTS_CONFIGURATIONS_VL — the multi-language view combining the base and translation tables.
  • JTS_CONFIGURATIONS_B_U1 and JTS_CONFIGURATIONS_B_U2 — the unique indexes on CONFIGURATION_ID and CONFIG_NAME that define the primary and business keys.
  • FND_USER and FND_LOGINS — referenced indirectly through CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for audit traceability.

Together, these objects define how configuration definitions are stored, secured, localized, and audited within the JTS self-service administrative framework.