Results for “jtf_msite_resps_b”

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

Overview

JTF_MSITE_RESPS_B is a CRM Foundation (JTF) base table that defines the responsibilities supported by a minisite within Oracle E-Business Suite. Minisites are lightweight, targeted self-service web pages commonly used for iStore, iSupport, and partner-facing portals. This table acts as the association layer that maps an Oracle Applications responsibility to a specific minisite, enabling the EBS framework to determine which responsibility context should be presented to a user visiting that minisite. The _B suffix indicates this is the base (non-translated) table, with translatable descriptive attributes stored in a companion _TL table.

Under the heuristic Data Vault classification mined from its foreign key structure, this table is satellite-leaning. In practice, it behaves as a link-style intersection between JTF_MSITES_B and the FND responsibility model, enriched with effective-dating and ordering attributes. Modelers may treat it as a satellite to a minisite hub, or as a link between minisite and responsibility, depending on the intended reporting granularity.

Key Information Stored

The table is owned by the JTF schema and contains 14 documented columns. The most significant columns for functional and integration purposes are:

• MSITE_RESP_ID — Surrogate primary key, enforced by the unique index JTF_MSITE_RESPS_B_PK. This is the column referenced by the user search term jtf_msite_resps_b_pk. It is also unique via JTF_MSITE_RESPS_B_U1.
• MSITE_ID — Foreign key to JTF_MSITES_B, identifying the parent minisite.
• RESPONSIBILITY_ID — Foreign key to the FND responsibility definition, indicating which responsibility is supported.
• APPLICATION_ID — The application owning the referenced responsibility; together with the two preceding columns it forms the business-key unique index JTF_MSITE_RESPS_B_U2.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective-dating columns controlling the active window of the responsibility-minisite association.
• SORT_ORDER — Controls display ordering of responsibilities on the minisite.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org / data security partitioning.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO-style audit and concurrency columns.

The distinction between the surrogate key and the composite business key (MSITE_ID, RESPONSIBILITY_ID, APPLICATION_ID) is important: integrations should generally use the composite natural key for idempotent load logic, while foreign references from the _TL table use MSITE_RESP_ID.

Common Use Cases and Queries

Typical scenarios include auditing which responsibilities are exposed on a given minisite, validating that duplicate responsibility mappings do not exist, and generating reports of currently active mappings. A common join pattern is:

SELECT m.MSITE_ID, m.NAME, r.RESPONSIBILITY_ID, r.APPLICATION_ID, j.SORT_ORDER
FROM   JTF_MSITE_RESPS_B j,
       JTF_MSITES_B      m,
       FND_RESPONSIBILITY r
WHERE  j.MSITE_ID = m.MSITE_ID
AND    j.RESPONSIBILITY_ID = r.RESPONSIBILITY_ID
AND    j.APPLICATION_ID = r.APPLICATION_ID
AND    TRUNC(SYSDATE) BETWEEN NVL(j.START_DATE_ACTIVE, SYSDATE-1)
                          AND NVL(j.END_DATE_ACTIVE, SYSDATE+1);

A duplicate-detection query checks for rows violating the U2 business key, and a lookup by the surrogate key uses MSITE_RESP_ID directly. Because translatable names reside in JTF_MSITE_RESPS_TL, reporting queries requiring localized descriptions must join on MSITE_RESP_ID and filter by the appropriate language column.

Related Objects

The most significant related objects, grounded in the documented FK relationships, are:

• JTF_MSITES_B — Parent table; joined via JTF_MSITE_RESPS_B.MSITE_ID = JTF_MSITES_B.MSITE_ID.
• JTF_MSITE_RESPS_TL — Translated table referencing MSITE_RESP_ID; joined on the surrogate key.
• FND_SECURITY_GROUPS — Joined via SECURITY_GROUP_ID for data-security filtering.
• FND_RESPONSIBILITY — Supplies responsibility name and application context via RESPONSIBILITY_ID and APPLICATION_ID.
• FND_APPLICATION — Resolves the application owning each responsibility.

Together these objects form the responsibility-to-minisite mapping chain that underlies CRM Foundation minisite personalization.