Search Results jts_config_version_flows

Overview

JTS_CONFIG_VERSION_FLOWS is a configuration association table within the Oracle E-Business Suite CRM Self Service Administration module (product code JTS). The object records the relationship between a configuration version and the specific flows that belong to that version. In the ETRM 12.1.1 documented schema, the table is owned by the JTS schema and contains 10 columns.

The ETRM metadata explicitly notes that this object is not implemented in this database, and the product is classified as Obsolete. Consequently, the table exists in legacy data models and historical reference documentation rather than as an active component of a current 12.1.1 or 12.2.2 deployment. Organizations upgrading from earlier releases may still encounter residual definitions, but no runtime behavior should be expected.

From a Data Vault modeling perspective, the ETRM heuristic classification for this table is standalone. This suggests it is best modeled as an independent structure rather than as a hub, link, or satellite. Despite carrying two foreign key references, the mined classification treats the table as a self-contained association entity rather than a hub-to-hub link.

Key Information Stored

The table's most significant columns are as follows:

• VERSION_ID — Identifies the parent configuration version. This is also a foreign key to VEA_VERSIONS and forms part of the composite unique key.
• FLOW_ID — Identifies the individual flow associated with the version. Together with VERSION_ID, it constitutes the business-key candidate.
• COMPLETE_FLAG — Indicates whether the flow configuration for the version has been completed, providing a processing or readiness status.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing data-level security and access partitioning.
• CREATION_DATE — Timestamp recording when the association row was first created.
• CREATED_BY — The application user who created the record.
• LAST_UPDATE_DATE — Timestamp of the most recent modification.
• LAST_UPDATED_BY — The user who performed the most recent update.
• LAST_UPDATE_LOGIN — Login session identifier associated with the last update.
• OBJECT_VERSION_NUMBER — Optimistic locking token used to detect concurrent modification.

The documented unique index JTS_CONFIG_VERSION_FLOWS_U1 covers (VERSION_ID, FLOW_ID), establishing these two columns as the business-key candidate that guarantees one flow entry per configuration version. No separate surrogate primary key column is documented in the ETRM excerpt; the composite unique index serves as the principal identifier.

Common Use Cases and Queries

Because the object is obsolete, use cases are largely historical, migration-related, or audit-driven. Typical scenarios include:

• Reconstructing which flows were deployed within a given configuration version prior to an upgrade.
• Auditing incomplete configurations where COMPLETE_FLAG is not set.
• Validating referential integrity between legacy configuration data and its parent versions.

A representative query listing flows and their completion status for a specific version:

SELECT version_id, flow_id, complete_flag, creation_date
FROM jts_config_version_flows
WHERE version_id = :p_version_id;

A reporting query joining parent version metadata:

SELECT v.version_id, v.version_name, f.flow_id, f.complete_flag
FROM jts_config_version_flows f, vea_versions v
WHERE f.version_id = v.version_id
AND f.security_group_id = :p_security_group_id;

Related Objects

The following objects are most significant to JTS_CONFIG_VERSION_FLOWS, based on documented FK relationships and the standard EBS audit/security columns:

• VEA_VERSIONS — Referenced via JTS_CONFIG_VERSION_FLOWS.VERSION_ID; the parent configuration version.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs row-level access.
• FND_USER — Implicitly referenced through CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — Implicitly referenced through LAST_UPDATE_LOGIN.
• JTS_CONFIG_VERSION_FLOWS_U1 — The unique index enforcing the (VERSION_ID, FLOW_ID) business key.

Given the obsolete status, no active PL/SQL APIs or public views are documented as depending on this table in current releases.