Search Results jts_config_version_statuses

Overview

The JTS_CONFIG_VERSION_STATUSES table resides in the JTS schema, which supports the CRM Self Service Administration module within Oracle E-Business Suite 12.1.1 and 12.2.2. This table functions as a status-tracking repository for configuration version records managed by the CRM Self Service Administration framework. It associates a lifecycle or processing status with a specific version held in VEA_VERSIONS, allowing administrators to model the various states a configuration version may occupy — such as draft, submitted, approved, or archived — within a controlled workflow.

From a data modeling perspective, the heuristic Data Vault classification for this table is standalone, as mined from its foreign key structure. This suggests that, rather than acting as a pure hub or link, the table behaves more like a satellite or reference table attached to VEA_VERSIONS, carrying descriptive status attributes. Because it holds a composite of a version reference and a status code alongside standard audit columns, it is best treated as a dependent status satellite in any downstream modeling exercise rather than as a standalone business hub.

Key Information Stored

The documented physical schema contains nine columns. The most significant are outlined below.

• VERSION_ID — Foreign key referencing VEA_VERSIONS. This is the primary link to the configuration version whose status is being tracked, and it is the leading component of the table's business identity.
• STATUS_CODE — The code representing the current lifecycle or processing status of the referenced version. This is the core business attribute maintained by the table.
• SECURITY_GROUP_ID — Foreign key referencing FND_SECURITY_GROUPS, enforcing multi-tenant or organizational data segregation consistent with Oracle EBS security conventions.
• CREATION_DATE — Timestamp recording when the status record was first created.
• CREATED_BY — The user identifier of the individual who inserted the row.
• LAST_UPDATE_DATE — Timestamp of the most recent modification to the record.
• LAST_UPDATED_BY — The user who performed the most recent update.
• LAST_UPDATE_LOGIN — The login session identifier associated with the last update, used for audit trails.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle EBS framework to detect concurrent updates.

No separate surrogate primary key is enumerated beyond VERSION_ID, which, combined with the status context, forms the functional business key. The presence of standard WHO columns confirms adherence to the EBS audit framework.

Common Use Cases and Queries

Typical usage centers on monitoring and reporting the status of configuration versions managed through CRM Self Service Administration. Administrators may query the current status of a specific version, list all versions in a given state, or audit status transitions over time.

SELECT v.version_id, s.status_code, s.last_update_date
FROM   jts_config_version_statuses s,
       vea_versions v
WHERE  s.version_id = v.version_id
AND    s.security_group_id = :sec_group_id;

Reporting scenarios include tracking versions awaiting approval, reconciling status counts against expected workflow states, and feeding dashboards that summarize configuration readiness.

Related Objects

• VEA_VERSIONS — Joined on VERSION_ID; the parent configuration version table.
• FND_SECURITY_GROUPS — Joined on SECURITY_GROUP_ID; governs data access partitioning.
• FND_USER — Implicitly referenced via CREATED_BY and LAST_UPDATED_BY for audit reporting.
• JTS-related configuration tables — Sibling JTS objects that share the SECURITY_GROUP_ID access model.