Results for “jtf_state_responsibilities_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_STATE_RESPONSIBILITIES_V is an APPS-owned, VALID database view that belongs to the JTF – CRM Foundation product family. As its description states, it is an internal view that joins JTF_STATE_RESPONSIBILITIES with FND_RESPONSIBILITY, exposing the association between Oracle E-Business Suite responsibilities and CRM state rules in a single denormalized result set. Because it is an internal (non-public) view, it is not intended as an end-user-facing object; rather, it supports CRM Foundation internal processing, reporting, and integration logic that must resolve a responsibility identifier to its description, its owning application, and the state rule to which it is mapped.

In Oracle EBS 12.1.1 and 12.2.2 the view is a convenient access point for developers and integrators who search on fnd_responsibility: rather than joining the responsibility base tables to the CRM state configuration tables manually, the view presents the already-combined dataset. Its presence is especially relevant in the context of state-based access or behavior rules, where a responsibility must be related to an OBJECT_VERSION_NUMBER-controlled row in JTF_STATE_RESPONSIBILITIES.

Underlying Base Objects

The documented ETRM metadata lists four referenced base objects for this view: FND_RESPONSIBILITY (synonym), FND_RESPONSIBILITY_TL (synonym), JTF_STATE_RESPONSIBILITIES (synonym), and JTF_STATE_RULES_VL (view). The view joins these through the relationship stated in its view text:

• JTF_STATE_RESPONSIBILITIES (alias SRE) is the primary driving table; it supplies the state responsibility identifier, the responsibility identifier, the rule identifier, reference/audit columns, the descriptive flexfield attribute columns, and OBJECT_VERSION_NUMBER.
• FND_RESPONSIBILITY (alias FRE) is joined on SRE.RESPONSIBILITY_ID = FRE.RESPONSIBILITY_ID and contributes APPLICATION_ID.
• FND_RESPONSIBILITY_TL (alias FRL) is joined on both RESPONSIBILITY_ID and APPLICATION_ID to supply the translated RESPONSIBILITY_NAME, with the language restricted to the session language through USERENV('LANG').
• JTF_STATE_RULES_VL (alias SRU) is joined on SRE.RULE_ID = SRU.RULE_ID to supply RULE_NAME and STATE_TYPE.

Because the standard EBS synonyms are referenced, the view resolves against APPS in the same way as direct queries on FND_RESPONSIBILITY or FND_RESPONSIBILITY_TL.

Key Columns

• STATE_RESPONSIBILITY_ID – Surrogate key from JTF_STATE_RESPONSIBILITIES, uniquely identifying each responsibility-to-rule mapping.
• RESPONSIBILITY_ID – The EBS responsibility identifier, the value most commonly searched when users look for fnd_responsibility.
• APPLICATION_ID – The application that owns the responsibility, sourced from FND_RESPONSIBILITY.
• RESPONSIBILITY_NAME – The session-language responsibility name from FND_RESPONSIBILITY_TL.
• RULE_ID, RULE_NAME, STATE_TYPE – The CRM state rule and its type from JTF_STATE_RULES_VL.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 – Descriptive flexfield context and segment columns carried forward from JTF_STATE_RESPONSIBILITIES.
• OBJECT_VERSION_NUMBER – The optimistic locking/version column retained from the base table.

Common Use Cases and Queries

The most frequent use is resolving which state rules are attached to a given responsibility, or conversely, which responsibilities participate in a given rule. The following query returns all state rule assignments for responsibilities in the current language:

SELECT responsibility_id, application_id, responsibility_name, rule_id, rule_name, state_type FROM apps.jtf_state_responsibilities_v ORDER BY responsibility_name;

To locate assignments for a specific responsibility by identifier:

SELECT responsibility_id, responsibility_name, rule_id, rule_name, state_type FROM apps.jtf_state_responsibilities_v WHERE responsibility_id = :responsibility_id;

For integration or interface validation, the view exposes both the responsibility name and its owning application in one pass, avoiding direct multi-table joins across FND_RESPONSIBILITY, FND_RESPONSIBILITY_TL, and the JTF configuration tables. Because the object is documented as internal and is not a supported public interface, customizations and reports should treat it as a read-only convenience view and verify availability in both 12.1.1 and 12.2.2 before relying on it in production code.