Results for “jtf_type_qtype_usgs_u1”

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

Overview

JTF_TYPE_QTYPE_USGS_ALL is a CRM Foundation table in the JTF schema that stores the transaction types that can be assigned to a territory type. Its functional role is to define the valid association between a territory type (such as Sales, Service, or Collections territory classifications) and a qualifying transaction type usage, effectively governing which transaction categories a given territory type is permitted to use within Oracle Territory Manager and related CRM modules.

The table sits within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model under the CRM Foundation product family, which provides shared infrastructure for Oracle Sales, Oracle Service, Oracle Marketing, and Oracle Trade Management. Territory and qualifier configuration is central to how leads, opportunities, service requests, and other transactional entities are routed and assigned to the correct sales or service organizations.

Based on the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a link table. It resolves a many-to-many relationship between territory types and qualifying transaction type usages, and it carries its own surrogate identity rather than being a pure descriptive satellite. This classification is a modeling suggestion derived from the FK topology, not a declaration present in the base EBS dictionary.

Key Information Stored

The table is documented with ten columns. The most significant are described below.

• TYPE_QTYPE_USG_ID — The surrogate primary key, defined by constraint JTF_TYPE_QTYPE_USGS_ALL_PK. It uniquely identifies each territory-type-to-qtype-usage association row.
• TERR_TYPE_ID — Foreign key to JTF_TERR_TYPES_ALL. Identifies the territory type to which the transaction type assignment applies.
• QUAL_TYPE_USG_ID — Foreign key to JTF_QUAL_TYPE_USGS_ALL. Identifies the qualifying transaction type usage being associated with the territory type.
• ORG_ID — The operating unit or organization identifier, supporting multi-org partitioning of configuration data.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, used for multi-tenant and security-group based data isolation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing creation and last-modification metadata.

The unique index JTF_TYPE_QTYPE_USGS_U1 is defined over (TYPE_QTYPE_USG_ID, ORG_ID), indicating the business-key candidate combines the surrogate identifier with the organization context. This composite uniqueness constraint ensures that a given usage record is not duplicated within an operating unit.

Common Use Cases and Queries

A primary use case is validating which transaction types are permissible for a specific territory type during territory definition and assignment in Territory Manager. Administrators and implementers query this table to audit territory-type configuration and to troubleshoot why a transaction type cannot be assigned to a territory.

A representative query joining to the territory type and qualifier usage tables would read:

• SELECT ttu.TYPE_QTYPE_USG_ID, tta.TERR_TYPE_NAME, qtu.QUAL_TYPE_USG_ID FROM JTF_TYPE_QTYPE_USGS_ALL ttu, JTF_TERR_TYPES_ALL tta, JTF_QUAL_TYPE_USGS_ALL qtu WHERE ttu.TERR_TYPE_ID = tta.TERR_TYPE_ID AND ttu.QUAL_TYPE_USG_ID = qtu.QUAL_TYPE_USG_ID AND ttu.ORG_ID = :org_id;

Reporting scenarios include generating a matrix of territory types versus assigned transaction categories, auditing multi-org configuration consistency, and extracting configuration for migration between instances. Because ORG_ID participates in the unique index, aggregate reports should group by organization to avoid conflating independent operating unit setups.

Related Objects

• JTF_TERR_TYPES_ALL — Referenced via TERR_TYPE_ID; the parent table of territory type definitions.
• JTF_QUAL_TYPE_USGS_ALL — Referenced via QUAL_TYPE_USG_ID; defines qualifying transaction type usages.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs security-group isolation.
• JTF_TERR_TYPES_TL — Translation table supplying territory type names for reporting joins.
• JTF_TERRITORIES_ALL — Territory instances whose behavior depends on the territory type configuration governed here.
• JTF_QUALIFIERS_ALL — Qualifier definitions that ultimately rely on the transaction type usage associations.
• FND_ORG_ASSIGNMENTS / HR_OPERATING_UNITS — Provides the organizational context for ORG_ID partitioning.

Together these objects form the configuration backbone for territory assignment and qualifier resolution across Oracle CRM Foundation and its dependent application modules.