Results for “jtf_tae_rpt_obj_winners”

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

Overview

JTF.JTF_TAE_RPT_OBJ_WINNERS is a CRM Foundation (JTF) table that persists the winning territories produced by the Territory Assignment Engine (TAE). Its documented description states simply that it "stores winning territories" — the post-evaluation result set that identifies which territory (and its associated resource assignment) ultimately won for a given transaction object after the TAE ran its rule and qualifier logic. In Oracle EBS 12.1.1 and 12.2.2, this table is the reporting-oriented landing point of territory matching for objects such as leads, opportunities, or other transactional entities referenced by TRANS_OBJECT_ID and TRANS_OBJECT_TYPE_ID.

From a Data Vault modeling perspective, the ETRM heuristic classifies this table as standalone. Independently, the presence of a surrogate-style key (RESULT_ID), multiple foreign keys, and a dense set of descriptive and audit attributes suggests it behaves as a satellite-like result fact enclosing the resolved territory assignment per object instance, rather than as a reusable hub. This classification is offered only as a modeling suggestion.

Key Information Stored

The table is physically owned by JTF and contains 32 documented columns. The most operationally significant are:

• RESULT_ID — surrogate primary key for each winning-territory row.
• TERR_ID — foreign key to JTF_TERR_ALL; the territory that won.
• TERR_RSC_ID — foreign key to JTF_TERR_RSC_ALL; the territory-resource row that won.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; enforces multi-org / data security.
• TRANS_OBJECT_ID, TRANS_DETAIL_OBJECT_ID, TRANS_OBJECT_TYPE_ID — identify the transaction object (and its detail) for which territories were evaluated.
• HEADER_ID1, HEADER_ID2, SOURCE_ID — business context identifiers carried from the source transaction.
• ABSOLUTE_RANK, NUM_WINNERS, TOP_LEVEL_TERR_ID — ranking and winner-count metadata.
• RESOURCE_ID, RESOURCE_TYPE, GROUP_ID, ROLE, PERSON_ID, ORG_ID — the resolved resource assignment details.
• PRIMARY_CONTACT_FLAG, FULL_ACCESS_FLAG — access/authority flags on the winning resource.
• RESULT_ID together with SESSION_ID, REQUEST_ID, PROGRAM_ID and standard WHO columns (CREATION_DATE, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER) provides the audit and concurrency trail.

Business-key candidates are the composite of TRANS_OBJECT_ID, TRANS_OBJECT_TYPE_ID, TERR_ID, and TERR_RSC_ID, which together uniquely identify a resolved winner for a given object.

Common Use Cases and Queries

The principal use of this table is reporting on territory wins and auditing TAE outcomes. Typical scenarios include verifying which territory claimed a lead, listing all resources assigned to an opportunity, and reconciling winner counts per transaction.

A canonical join retrieves winners with their territory and resource detail:

SELECT w.RESULT_ID, w.TRANS_OBJECT_ID, w.TERR_ID, t.TERR_NAME, w.RESOURCE_ID, w.ABSOLUTE_RANK FROM JTF.JTF_TAE_RPT_OBJ_WINNERS w JOIN JTF.JTF_TERR_ALL t ON w.TERR_ID = t.TERR_ID WHERE w.TRANS_OBJECT_ID = :object_id ORDER BY w.ABSOLUTE_RANK;

Raking the top winner per object uses ABSOLUTE_RANK = 1 combined with NUM_WINNERS and TOP_LEVEL_TERR_ID to determine the decisive territory. Counting winners by territory supports coverage analysis:

SELECT TERR_ID, COUNT(*) FROM JTF.JTF_TAE_RPT_OBJ_WINNERS GROUP BY TERR_ID;

Filtering by SECURITY_GROUP_ID and ORG_ID is essential under multi-org security. Session and request columns (SESSION_ID, REQUEST_ID) help trace a specific TAE run.

Related Objects

• JTF.JTF_TERR_ALL — joined on TERR_ID; the master territory definition.
• JTF.JTF_TERR_RSC_ALL — joined on TERR_RSC_ID; territory-to-resource assignments.
• FND.FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; security group resolution.
• JTF.JTF_TAE_RPT_OBJ and related TAE report tables — share TRANS_OBJECT_ID/SESSION_ID context for full evaluation results.
• TAE engine program (concurrent program identified via PROGRAM_ID/REQUEST_ID) — the process that populates this table.

Because the table is documented as standalone with no child tables, it is treated as a terminal result store rather than a parent in the CRM Foundation territory model.