Search Results jtf_state_rules_b_n1

Overview

JTF.JTF_STATE_RULES_B is a seed data table in the Oracle E-Business Suite JTF (CRM Foundation) schema that stores the base definitions of status transition rules used by the State Management infrastructure. It holds the rule header records that describe which status types apply to a given object (such as a lead, opportunity, service request, or interaction), and serves as the parent for the responsibilities, transitions, and state application mappings that complete a state model. In EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_SEED tablespace (PCTFREE 10), consistent with its role as seeded, reference-style configuration data rather than high-volume transactional data. The object is classified VALID with FND Design Data identifier JTF.JTF_STATE_RULES_B. Heuristically the object leans toward a satellite classification, in that it extends the core object/status-type definitions with descriptive and flexfield attributes; a Data Vault model would nonetheless treat RULE_ID as a natural business key.

Key Information Stored

The surrogate primary key is RULE_ID, populated via the JTF_STATE_RULES_B_PK constraint. Two unique business-key candidates are documented on the index JTF_STATE_RULES_B_U1: RULE_ID together with ZD_EDITION_NAME, the edition column associated with Online Patching in 12.2.x. The STATE_TYPE column (VARCHAR2(30)) records the object status type governed by the rule and is a foreign key to JTF_OBJECTS_B.OBJECT_CODE; APPLICATION_ID identifies the owning application (foreign key to FND_APPLICATION), and SECURITY_GROUP_ID supports multi-organization security filtering against FND_SECURITY_GROUPS. Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — provide audit history, while OBJECT_VERSION_NUMBER implements optimistic locking for HTML-based user interfaces. ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 (each VARCHAR2(150)) are descriptive flexfield segments that allow customers to extend rule definitions without schema changes. Non-unique indexes JTF_STATE_RULES_B_N1 (APPLICATION_ID) and JTF_STATE_RULES_B_N2 (STATE_TYPE) support the dominant access paths.

Common Use Cases and Queries

Typical use cases include auditing the status rule configuration of an object type, resolving which application owns a rule, and joining rule headers to their transition and responsibility detail rows for a complete state model report. A representative query retrieves all rules for a given status type:

• SELECT r.rule_id, r.state_type, r.application_id, r.security_group_id FROM jtf.jtf_state_rules_b r WHERE r.state_type = :state_type;
• SELECT r.rule_id, t.from_state, t.to_state FROM jtf.jtf_state_rules_b r, jtf.jtf_state_transitions t WHERE r.rule_id = t.rule_id;
• SELECT r.rule_id, a.application_short_name FROM jtf.jtf_state_rules_b r, fnd_application a WHERE r.application_id = a.application_id;

Because flexfield attributes are stored inline, reporting on ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 is common when customers have configured descriptive flexfields. Note that in 12.2.x, queries used for data extraction should account for ZD_EDITION_NAME and the editioning views presented by Online Patching.

Related Objects

The rule header is referenced by JTF_STATE_RESPONSIBILITIES.RULE_ID, which maps rules to responsibilities, and by JTF_STATE_TRANSITIONS.RULE_ID, which defines the permitted from-state/to-state movements. It references JTF_OBJECTS_B via STATE_TYPE, FND_APPLICATION via APPLICATION_ID, and FND_SECURITY_GROUPS via SECURITY_GROUP_ID. Related state infrastructure objects include JTF_STATE_APPLICATIONS and JTF_STATE_RULE_ACTIONS, together with the JTF_OBJECTS_VL view used to resolve object code descriptions. These relationships make JTF_STATE_RULES_B the central hub record from which a complete state model can be reconstructed.