Search Results jtf_state_transitions




Overview
Explore in AI Chat

Overview

JTF_STATE_TRANSITIONS is a CRM Foundation (JTF) table that stores the permitted transitions between states for objects governed by the JTF state management engine. It defines the directed edges of a state model: each row asserts that an entity may move from an initial state to a final state under a named rule. State models are consumed by Oracle EBS components such as Oracle Interaction Center, TeleSales, and other CRM Foundation-based modules that require configurable lifecycle or workflow state machines rather than hard-coded transitions.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table heuristically as a link. The classification is a modeling suggestion only: the table's role is to associate a rule with an originating state and a resulting state, which is characteristic of a relationship (link) entity rather than a descriptive satellite. In physical EBS terms, the table is owned by the JTF schema with a documented column count of 28 and a primary key constraint named JTF_STATE_TRANSITIONS_PK.

Key Information Stored

The table records the transition definition itself along with standard EBS auditing and multi-tenant attributes. The most significant columns are:

The documented unique index JTF_STATE_TRANSITIONS_U1 covers (STATE_TRANSITION_ID, ZD_EDITION_NAME), reflecting the 12.2 editioning model where the surrogate key alone is not globally unique across editions. No separate business-key unique index is documented beyond this edition-aware index.

Common Use Cases and Queries

Typical usage centers on validating whether a proposed state change is legal for a given rule, and on reporting the state model for administrative review. A representative query joins transitions to their governing rules:

  • Listing all transitions for a rule: SELECT INITIAL_STATE_ID, FINAL_STATE_ID FROM JTF.JTF_STATE_TRANSITIONS WHERE RULE_ID = :p_rule_id.
  • Validating a specific move: select the row matching both INITIAL_STATE_ID and FINAL_STATE_ID for the rule to confirm the transition exists before permitting it.
  • Auditing recent configuration changes using LAST_UPDATED_BY and LAST_UPDATE_DATE, useful after patches that alter the CRM state model.
  • Reconciling DFF attributes (ATTRIBUTE_CATEGORY and ATTRIBUTE1–15) where customers have extended transition metadata for custom workflow rules.

Reporting is generally read-only; transitions are normally maintained through the CRM Foundation state management setup rather than direct DML.

Related Objects

The most significant related objects, based on the documented foreign-key relationships, are:

  • JTF_STATE_RULES_B — referenced by JTF_STATE_TRANSITIONS.RULE_ID; the base table holding the state rule definitions that govern valid transitions.
  • FND_SECURITY_GROUPS — referenced by JTF_STATE_TRANSITIONS.SECURITY_GROUP_ID; supplies the security grouping used to partition transition visibility.
  • JTF_STATE_RULES_TL — the translation companion to JTF_STATE_RULES_B, providing rule names and descriptions by language.
  • JTF_STATE_TRANSITIONS_PK — the primary key constraint object, relevant to index and constraint analysis.
  • JTF_STATE_TRANSITIONS_U1 — the edition-aware unique index, relevant in 12.2 online patching diagnostics.

Joins to state definition tables (via INITIAL_STATE_ID and FINAL_STATE_ID) are required to render human-readable state names in reports, since the transition table itself stores only state identifiers.