Search Results jtf_tty_admin_bin_summ_pk

Overview

JTF_TTY_ADMIN_BIN_SUMM is a table in the JTF schema (CRM Foundation module) that stores summarized data for territory administrator bins. It is part of the Oracle Territory Manager infrastructure, which governs how sales territories are defined, qualified, and assigned across CRM applications such as Oracle Sales, Oracle TeleSales, and Oracle Service. The "administrator bin" concept refers to grouped territories maintained and refreshed for administrative or bulk-assignment purposes, and this summary table acts as a precomputed aggregate layer over that bin membership data.

From a Data Vault modeling perspective, the mined relationship structure suggests classifying this object as a satellite. It carries descriptive and derived metrics (counts of leads, opportunities, accounts, and named-account percentages) rather than serving purely as a hub of business keys or a link between entities. The heuristic classification is standalone, meaning the mining did not identify it as a pure junction between two hubs. This distinction matters when mapping EBS CRM territory data into an analytical warehouse.

Key Information Stored

The table contains 17 documented columns. Its surrogate primary key is ADMIN_BIN_TERR_GRP_ID, defined by the constraint JTF_TTY_ADMIN_BIN_SUMM_PK. A unique index, JTF_TTY_ADMIN_BIN_SUMM_U1, also covers ADMIN_BIN_TERR_GRP_ID, making it the primary business-key candidate for uniquely resolving a summary row.

• ADMIN_BIN_TERR_GRP_ID — Surrogate key and unique identifier for each administrator-bin territory group summary row.
• TERR_GROUP_ID — Foreign key to JTF_TTY_TERR_GROUPS, identifying the underlying territory group being summarized.
• TERR_GROUP_NAME — Denormalized display name of the associated territory group.
• LEADS, OPPORTUNITIES, ACCOUNTS — Counts of leads, opportunities, and accounts reflected in the bin summary.
• TOTAL_NAMED_ACCOUNT — Total named accounts within the territory group.
• MAPPED_NAMED_ACC_PER, ASSIGNED_NAMED_ACC_PER — Percentage of named accounts that have been mapped versus assigned, supporting coverage analysis.
• CATCH_ALL_UPDATE_DATE, KPI_UPDATE_DATE — Refresh timestamps for catch-all processing and KPI recalculation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle framework for concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO-column audit trail.

Common Use Cases and Queries

Typical usage centers on territory coverage dashboards and administrator bin monitoring. A report might surface territory groups with low assigned-account percentages to flag assignment gaps.

• Identify bins with high lead or opportunity counts but low account assignment: SELECT TERR_GROUP_NAME, LEADS, OPPORTUNITIES, ASSIGNED_NAMED_ACC_PER FROM JTF.JTF_TTY_ADMIN_BIN_SUMM WHERE ASSIGNED_NAMED_ACC_PER < 50 ORDER BY OPPORTUNITIES DESC;
• Detect stale summaries by comparing KPI_UPDATE_DATE against a threshold.
• Join to JTF_TTY_TERR_GROUPS to enrich summaries with full territory-group attributes.
• Feed territory KPI extracts into CRM analytics or a data warehouse.

Related Objects

The documented foreign key establishes the primary relationship:

• JTF_TTY_TERR_GROUPS — Referenced by TERR_GROUP_ID; the parent territory-group definition table.
• JTF_TTY_TERRITORIES and related territory assignment tables — Supply the underlying membership data summarized here.
• JTF_TTY_BIN_* family tables — Companion bin and resource-group objects sharing the ADMIN_BIN_TERR_GRP_ID lineage.
• JTF_TERR_ASSIGNMENT / resource assignment objects — Consume territory bin data for quota and coverage calculations.
• Territory Manager concurrent programs — Populate and refresh this summary table on scheduled runs.