Search Results jts_config_version_flows_u1

Overview

JTS.JTS_CONFIG_VERSION_FLOWS is a transactional table in the JTS (Java Transaction Services / Application Object Library configuration) schema within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It serves as a setup summary repository that records the association between a configuration version and its constituent flows, along with the last-modified timestamp and a completeness indicator for each flow within that version. In practical terms, the table functions as a control ledger that tells the EBS configuration engine whether a given version's flow setup has been fully populated before the version is consumed by downstream processing.

The table is created under the APPS_TS_TX_DATA tablespace and is registered in FND Design Data as JTS.JTS_CONFIG_VERSION_FLOWS, with an object status of VALID. The metadata's heuristic Data Vault classification marks this object as standalone. From a dimensional modeling perspective, the presence of a composite unique key (VERSION_ID, FLOW_ID) and a set of descriptive and audit attributes suggests it behaves most like a link or satellite construct rather than a pure hub; it resolves many-to-many relationships between versions and flows while carrying status and audit payload.

Key Information Stored

The table contains ten documented columns. The most significant are the two key components and the descriptive and audit fields:

• VERSION_ID (NUMBER) – identifies the configuration version; part of the composite business key and a foreign key to VEA_VERSIONS.
• FLOW_ID (NUMBER) – identifies the individual flow within the version; the second component of the composite business key.
• COMPLETE_FLAG (VARCHAR2) – indicates the completeness of the flow setup. Values are 'Y' or 'N', with null treated as 'N'. This is the primary control flag used by setup validation logic.
• CREATION_DATE, CREATED_BY – standard WHO audit columns capturing row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard WHO audit columns capturing the most recent modification, supporting the setup summary's "last modified" reporting.
• SECURITY_GROUP_ID (NUMBER) – security group identifier; a foreign key to FND_SECURITY_GROUPS used for multi-organization data partitioning.
• OBJECT_VERSION_NUMBER (NUMBER) – optimistic locking version counter used by the EBS framework to detect concurrent updates.

The unique index JTS_CONFIG_VERSION_FLOWS_U1, defined on (VERSION_ID, FLOW_ID), is the business-key candidate and enforces that a flow appears at most once per version. It resides in the APPS_TS_TX_IDX tablespace with a NORMAL index type. No single-column surrogate primary key is documented separately in the metadata; the composite unique index serves as the practical row identifier.

Common Use Cases and Queries

Typical uses include validating that a configuration version is complete before activation, reporting on incomplete flow setups, and auditing when a version's flows were last touched. A completeness check for a specific version follows this pattern:

• SELECT FLOW_ID, COMPLETE_FLAG FROM JTS.JTS_CONFIG_VERSION_FLOWS WHERE VERSION_ID = :version_id;
• SELECT COUNT(*) FROM JTS.JTS_CONFIG_VERSION_FLOWS WHERE VERSION_ID = :version_id AND NVL(COMPLETE_FLAG,'N') = 'N'; — returns the number of incomplete flows, which should be zero before the version is consumed.
• Change-reporting query joining to standard WHO columns to show last modification dates for a version's flows.

Because the table is referenced by the APPS synonym JTS_CONFIG_VERSION_FLOWS, applications and reports typically query it through the APPS schema rather than the JTS schema directly.

Related Objects

• VEA_VERSIONS – referenced via VERSION_ID; supplies the version definition each row belongs to.
• FND_SECURITY_GROUPS – referenced via SECURITY_GROUP_ID; governs which security group owns the row.
• APPS.JTS_CONFIG_VERSION_FLOWS – the APPS-synonym wrapper through which this table is exposed to application logic and reporting.
• JTS_CONFIG_VERSION_FLOWS_U1 – the composite unique index on (VERSION_ID, FLOW_ID) that enforces the business key.
• VEA_FLOWS (related by domain) – the flow master referenced conceptually by FLOW_ID, used together with this table to resolve flow names and attributes.