Search Results jtf_msite_resps_b_pk

Overview

The JTF_MSITE_RESPS_B table is a core data object within the Oracle E-Business Suite CRM Foundation module (JTF). It serves as the master definition table for mapping responsibilities to minisites. A minisite is a specialized, branded portal within the CRM framework, often used for partner or customer extranets. This table's primary role is to control access by defining which specific EBS responsibilities (and their associated application menus and functions) are authorized for use within a given minisite. It acts as a critical security and personalization layer, ensuring that users accessing the system via a minisite interface are presented with only the appropriate responsibilities and functionality.

Key Information Stored

The table stores the essential linkage between a minisite and EBS responsibilities. Its key columns include MSITE_RESP_ID, which is the unique primary key identifier for each mapping record. The MSITE_ID column is a foreign key that references a specific minisite defined in the JTF_MSITES_B table. The RESPONSIBILITY_ID and APPLICATION_ID columns together uniquely identify a specific responsibility within the Oracle Applications core (FND_RESPONSIBILITY table). This combination enforces which responsibility from which application is enabled for the linked minisite. The table typically includes standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing.

Common Use Cases and Queries

A primary use case is administering minisite security, where an administrator needs to grant or revoke responsibility access for a partner portal. This is often managed through the CRM minisite administration UI. For reporting and troubleshooting, common queries involve listing all responsibilities available for a specific minisite or identifying which minisites a particular responsibility is assigned to. A sample SQL pattern to retrieve this data is:

• SELECT msite.msite_name, resp.responsibility_name, resp.application_id FROM jtf_msite_resps_b map, jtf_msites_b msite, fnd_responsibility_vl resp WHERE map.msite_id = msite.msite_id AND map.responsibility_id = resp.responsibility_id AND map.application_id = resp.application_id AND msite.msite_id = :p_msite_id;

Data integrity checks are another common scenario, such as verifying that all MSITE_ID values in JTF_MSITE_RESPS_B have valid parent records in JTF_MSITES_B.

Related Objects

The table has defined relationships with several key objects, as per the provided metadata. It references the JTF_MSITES_B table via a foreign key on the MSITE_ID column, establishing the parent minisite. The table is itself referenced by the JTF_MSITE_RESPS_TL table, which holds translated descriptive information (like a description) for the responsibility-minisite mapping, linked by the MSITE_RESP_ID primary key. While not listed in the provided excerpt, the RESPONSIBILITY_ID and APPLICATION_ID columns functionally relate to the core FND_RESPONSIBILITY table. The primary key constraint JTF_MSITE_RESPS_B_PK is on MSITE_RESP_ID, and a unique key constraint (JTF_MSITE_RESPS_B_UK1) exists on the combination of MSITE_ID, RESPONSIBILITY_ID, and APPLICATION_ID to prevent duplicate mappings.