Search Results jtf_state_responsibilities_n1

Overview

JTF.JTF_STATE_RESPONSIBILITIES is a VALID table owned by the JTF schema and registered in FND Design Data as JTF.JTF_STATE_RESPONSIBILITIES. Its documented purpose is precise: it is an intersection table between State Rules and Responsibilities, associating rules with the responsibilities to which they apply. In the Oracle E-Business Suite 12.1.1 and 12.2.2 architectures, JTF serves as the common technology foundation shared by CRM and self-service applications, and state rules drive conditional UI behavior, task visibility, and workflow routing. By mapping a rule to one or more responsibilities, this table determines which users, by virtue of the responsibilities they hold, are governed by a given rule at runtime.

From a Data Vault modeling perspective, the mined classification for this object is satellite-leaning. This is offered as a heuristic suggestion rather than a definitive designation: although the table carries a surrogate primary key and standard who-columns typical of a satellite, its two foreign keys (RESPONSIBILITY_ID and RULE_ID) also give it link-like connective characteristics. Analysts should treat the classification as a starting hypothesis for reverse-engineering, not as a fixed attribute of the schema.

Key Information Stored

The table is stored in the APPS_TS_SEED tablespace with PCTFREE 10 and contains 27 documented columns. The most consequential of these are:

• STATE_RESPONSIBILITY_ID — the surrogate primary key, defined by the constraint JTF_STATE_RESPONSIBILITIES_PK, and the sole unique business-key candidate shown in the unique index JTF_STATE_RESPONSIBILITIES_U1.
• RESPONSIBILITY_ID — the foreign key to FND_RESPONSIBILITY defining the responsibility associated with the rule; indexed non-uniquely by JTF_STATE_RESPONSIBILITIES_N1.
• RULE_ID — the foreign key to JTF_STATE_RULES_VL (documented as referencing JTF_STATE_RULES_B) identifying the state rule; indexed non-uniquely by JTF_STATE_RESPONSIBILITIES_N2.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS supporting multi-organization security partitioning.
• OBJECT_VERSION_NUMBER — the sequence used for optimistic database locking in HTML-based user interfaces.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns recording row audit history.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — descriptive flexfield segments available for extensibility.
• ZD_EDITION_NAME — the editioning column used to track row versions across editions.

Notably, the documented unique index JTF_STATE_RESPONSIBILITIES_U1 is a composite of STATE_RESPONSIBILITY_ID and ZD_EDITION_NAME, meaning uniqueness is enforced per edition rather than on the surrogate alone.

Common Use Cases and Queries

The primary operational use case is resolving which responsibilities a given rule applies to, or conversely which rules govern a specific responsibility. A representative query follows:

• Determine the responsibilities bound to a rule: SELECT ar.RESPONSIBILITY_ID, fr.RESPONSIBILITY_NAME FROM JTF.JTF_STATE_RESPONSIBILITIES ar, FND_RESPONSIBILITY fr WHERE ar.RULE_ID = :rule_id AND ar.RESPONSIBILITY_ID = fr.RESPONSIBILITY_ID;
• Detect unassigned state rules: identify rows in JTF_STATE_RULES_B with no corresponding entry in this intersection table, which commonly indicates rules that will never execute for any user.
• Audit responsibility-to-rule coverage for a security group by filtering on SECURITY_GROUP_ID.
• Seed data comparison: because the table resides in APPS_TS_SEED, administrators frequently compare seeded rows against customized ones using the Who columns.

Because run-time evaluation of state rules is performance-sensitive, the N1 and N2 indexes exist to support lookups by responsibility or rule respectively; queries should honor those predicates to avoid full scans.

Related Objects

The following objects are most significant to this table based on documented foreign keys and the surrounding JTF state model:

• JTF.JTF_STATE_RULES_B / JTF_STATE_RULES_VL — the parent rule definitions joined via RULE_ID; the VL view supplies translatable rule text.
• FND_RESPONSIBILITY — the responsibility definition joined via RESPONSIBILITY_ID.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for secured access control.
• FND_USER — via the Who columns CREATED_BY, LAST_UPDATED_BY, for audit reporting.
• FND_LOGINS — via LAST_UPDATE_LOGIN for originating session identification.

Together these dependencies confirm the table's role as a lightweight but essential binding layer between the JTF state rule engine and the EBS responsibility security model.