Search Results jtf_state_rules_b




Overview
Explore in AI Chat

Overview

JTF_STATE_RULES_B is the base table in the JTF (CRM Foundation) schema that stores rule definitions used by the Oracle E-Business Suite state management framework. This framework governs the lifecycle of CRM entities — leads, opportunities, notes, tasks, and similar objects — by defining which state transitions are permitted for a given object type. Each row in JTF_STATE_RULES_B represents a single named rule that ties together an object type, an owning application, and a set of transition and responsibility assignments. The table is the parent of the operational rule configuration stored in JTF_STATE_TRANSITIONS and JTF_STATE_RESPONSIBILITIES, making it the central definition point for state-model behavior.

In Data Vault terms, the mined foreign-key structure indicates a satellite-leaning classification. The table holds descriptive attributes about a rule definition (attributes, application, object type) keyed by a single surrogate RULE_ID rather than modeling a many-to-many business event. This classification is a modeling suggestion only; the physical table functions as a master definition table with a stable surrogate key and a dependent child hierarchy.

Key Information Stored

The surrogate primary key is RULE_ID, enforced by the constraint JTF_STATE_RULES_B_PK. A documented unique index, JTF_STATE_RULES_B_U1, spans RULE_ID and ZD_EDITION_NAME, making a rule identifier plus edition a candidate business key for edition-aware lookups. The most significant columns are:

Common Use Cases and Queries

Typical usage includes diagnosing why a user cannot move a CRM entity to a target state, reporting on configured state rules by application, and auditing rule definitions after an upgrade or patch. A common join pattern resolves the rule to its object type and transitions:

  • List rules for a given object type: SELECT r.rule_id, r.state_type, r.application_id FROM jtf_state_rules_b r WHERE r.state_type = :p_object_type;
  • Resolve transitions for a rule: SELECT t.* FROM jtf_state_transitions t WHERE t.rule_id = :p_rule_id;
  • Find responsibility assignments: SELECT s.* FROM jtf_state_responsibilities s WHERE s.rule_id = :p_rule_id;
  • Resolve the owning application: SELECT a.application_name FROM fnd_application a, jtf_state_rules_b r WHERE a.application_id = r.application_id;

Reporting extracts often join JTF_STATE_RULES_B to JTF_OBJECTS_B to translate STATE_TYPE into a user-friendly object name, and filter on SECURITY_GROUP_ID to respect data security in multi-org installs. Because flexfield columns are frequently referenced, reports may join FND_FLEX_VALUES for attribute decoding.

Related Objects

  • JTF_STATE_TRANSITIONS — child table joined on RULE_ID; defines the allowed from/to state transitions for each rule.
  • JTF_STATE_RESPONSIBILITIES — child table joined on RULE_ID; maps responsibilities to rules for authorization.
  • JTF_OBJECTS_B — parent of STATE_TYPE; provides the object type definitions used by rules.
  • FND_APPLICATION — parent of APPLICATION_ID; identifies the owning application.
  • FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID; enforces data security grouping.
  • JTF_STATE_RULES_TL — the translatable (language) companion table holding rule names and descriptions.