Search Results jtf_state_responsibilities_pk

Overview

JTF_STATE_RESPONSIBILITIES is an intersection table in the JTF (CRM Foundation) product schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to associate State Rules with Responsibilities—that is, it binds a rule definition to one or more application responsibilities so that the rule is evaluated only within the context of the assigned responsibility. This table sits at the heart of the CRM Foundation State Rules framework, which governs conditional behavior in CRM modules such as TeleSales, iStore, and interaction/document management.

From a Data Vault modeling perspective (heuristic, mined from the foreign key structure), this object is classified as satellite-leaning. It carries descriptive and associative attributes—including the standard 15 flex attributes and audit columns—attached to a parent rule. Despite exhibiting link-like behavior by joining RULE_ID to RESPONSIBILITY_ID, the presence of a surrogate primary key, descriptive columns, and the ZD_EDITION_NAME column point toward a satellite role in a dimensional/data vault design. Practitioners designing a warehouse layer should treat it as a satellite hanging off the rule hub.

Key Information Stored

The table is documented with 27 columns. The following are the most operationally significant:

• STATE_RESPONSIBILITY_ID — Surrogate primary key. Uniquely identifies each association row via JTF_STATE_RESPONSIBILITIES_PK.
• RULE_ID — Foreign key to JTF_STATE_RULES_B. Identifies the state rule being associated.
• RESPONSIBILITY_ID — Identifies the responsibility (definition) bound to the rule. Combined with RULE_ID, it forms the substantive business relationship.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS. Enables multi-tenant / security-group partitioning of the row.
• ZD_EDITION_NAME — Editioning column supporting EBS 12.2 online patching (edition-based redefinition). It participates in the unique index JTF_STATE_RESPONSIBILITIES_U1.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield (DFF) columns for customer-extensible data.

The unique index JTF_STATE_RESPONSIBILITIES_U1 covers (STATE_RESPONSIBILITY_ID, ZD_EDITION_NAME), which is the editioning-aware uniqueness constraint rather than a pure business key over RULE_ID and RESPONSIBILITY_ID. The surrogate PK therefore remains the primary reference point for other tables.

Common Use Cases and Queries

Typical uses of this table include resolving which responsibilities a given rule applies to, building administrative reports of rule-to-responsibility mappings, and diagnosing why a CRM rule fires (or does not fire) for a given user session.

• List all responsibilities assigned to a rule:

  SELECT r.responsibility_id, a.responsibility_name
  FROM   jtf_state_responsibilities r,
         fnd_responsibility_vl a
  WHERE  r.responsibility_id = a.responsibility_id
  AND    r.rule_id = :p_rule_id;

• Find all rules tied to a specific responsibility:

  SELECT rule_id FROM jtf_state_responsibilities
  WHERE  responsibility_id = :p_responsibility_id;

• Security-group partitioning reports joining FND_SECURITY_GROUPS on SECURITY_GROUP_ID.
• Audit queries filtering on LAST_UPDATE_DATE or LAST_UPDATED_BY for change tracking.

Because editioning is in effect (12.2), queries should ideally reference the base table so the runtime edition view is applied automatically.

Related Objects

• JTF_STATE_RULES_B — Parent table; join on RULE_ID. Holds the rule definition.
• JTF_STATE_RULES_TL — Translated rule names/descriptions, joined via RULE_ID.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for security partitioning.
• FND_RESPONSIBILITY_VL / FND_RESPONSIBILITY_B — Responsibility definitions joined on RESPONSIBILITY_ID.
• FND_USER_RESP_GROUPS — Links users to responsibilities; useful when tracing rule applicability to a logged-in user.
• JTF_STATE_RULES (view layer) — Public API-facing view of the rules framework.
• JTF_STATE_ACCESS / JTF_STATE_DETAILS — Related state-rule components in the same framework.