Results for “jtf_tty_role_prod_int”

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

Overview

JTF_TTY_ROD_PROD_INT — formally JTF.JTF_TTY_ROLE_PROD_INT — is a CRM Foundation (JTF) table that stores product interest for territory groups. It associates a territory group role (as defined in JTF_TTY_TERR_GRP_ROLES) with a specific product interest type (from AS_INTEREST_TYPES_B) and an optional product category. In Oracle EBS 12.1.1 and 12.2.2, this table is part of the Territory Manager (TTY) subsystem, which underpins lead and opportunity qualification, territory assignment, and product-based routing in Trade Management and Sales Foundation modules.

The ETRM metadata classifies this object with a heuristic Data Vault designation of satellite-leaning. In modeling terms, this suggests JTF_TTY_ROLE_PROD_INT functions as a descriptive satellite attached to the territory group role hub represented by JTF_TTY_TERR_GRP_ROLES, capturing attribute-level detail (product interest and category) rather than acting as an independent hub or a pure many-to-many link.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• TERR_GROUP_ROLE_PROD_INT_ID — the surrogate primary key (JTF_TTY_ROLE_PROD_INT_PK) and sole business-key candidate (unique index JTF_TTY_ROLE_PROD_INT_U1).
• TERR_GROUP_ROLE_ID — foreign key to JTF_TTY_TERR_GRP_ROLES; identifies the territory group role to which the product interest applies.
• INTEREST_TYPE_ID — foreign key to AS_INTEREST_TYPES_B; the interest classification (e.g., a specific product interest) linked to the role.
• PRODUCT_CATEGORY_ID and PRODUCT_CATEGORY_SET_ID — identify the product category and its category set, scoping the interest to a particular product hierarchy node.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework for concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking record provenance and change history.

The primary key is surrogate and generated; the unique index on TERR_GROUP_ROLE_PROD_INT_ID reinforces its role as the persistent identifier rather than a composite business key.

Common Use Cases and Queries

Typical reporting scenarios include listing all product interests defined for a territory group role, or identifying which territory roles target a given interest type. A representative query joining the parent role table is:

• SELECT r.terr_group_role_id, rpi.interest_type_id, rpi.product_category_id FROM jtf.jtf_tty_role_prod_int rpi, jtf.jtf_tty_terr_grp_roles r WHERE rpi.terr_group_role_id = r.terr_group_role_id AND rpi.interest_type_id = :interest_type;
• Interest-type resolution against AS_INTEREST_TYPES_B: SELECT rpi.terr_group_role_prod_int_id, it.interest_type FROM jtf.jtf_tty_role_prod_int rpi, as_interest_types_b it WHERE rpi.interest_type_id = it.interest_type_id;
• Audit or data-migration extracts filtered on CREATION_DATE or LAST_UPDATE_DATE ranges.

These patterns support territory setup validation, product-based lead routing analysis, and CRM personalization reporting.

Related Objects

The following objects are most significant in relation to this table:

• JTF_TTY_TERR_GRP_ROLES — parent table joined on TERR_GROUP_ROLE_ID.
• AS_INTEREST_TYPES_B — interest type lookup joined on INTEREST_TYPE_ID.
• JTF_TTY_ROLE_PROD_INT_PK — primary key constraint.
• JTF_TTY_ROLE_PROD_INT_U1 — unique index on TERR_GROUP_ROLE_PROD_INT_ID.
• JTF_TTY_TERR_GRP_ROLES_PK — referenced key constraint on the parent table.
• AS_INTEREST_TYPES_B_PK — referenced key constraint on the interest type table.
• Territory Manager setup and CRM Foundation APIs that read product-interest configuration when evaluating territory qualification rules.