Search Results jty_denorm_dea_rules_all
Overview
The JTY_DENORM_DEA_RULES_ALL table is a multi-organization (denoted by the _ALL suffix) table owned by the JTF schema within the CRM Foundation product family. Its documented description states that it "stores denormalized territories for date effectivity assignment." In Oracle EBS 12.1.1 and 12.2.2, Territory Manager relies on this structure to flatten the hierarchical parent/child relationships inherent in territory definitions into pre-resolved rows, enabling significantly faster evaluation of date-effective territory rules during runtime qualification.
Territory data in the transactional CRM schema (primarily JTF_TERR_ALL) is organized hierarchically. Evaluating a rule that must ascend the hierarchy at query time is expensive. By denormalizing the territory relationships — pre-computing attributes such as rank, level from root, top-level territory, and immediate-parent flags — this table allows the Territory Manager engine to resolve winners, compute ranks, and enforce date effectivity without recursive traversal. Data Vault modeling heuristics classify this object as standalone, meaning it does not participate in a classic hub/link/satellite pattern mined from its foreign keys; it functions as a purpose-built denormalized cache rather than a normalized entity.
Key Information Stored
The table contains 25 documented columns in the 12.2.2 physical schema. The most significant include:
- TERR_ID — The territory identifier, the primary business key and foreign key to
JTF_TERR_ALL. This anchors each denormalized row to its source territory. - RELATED_TERR_ID and TOP_LEVEL_TERR_ID — The related territory and the root of the hierarchy, populated during denormalization to support hierarchy-aware queries.
- SOURCE_ID — Identifies the source record that generated the denormalized entry.
- RANK, ABSOLUTE_RANK, and NUM_WINNERS — Ranking and winner-count fields used when multiple territories qualify for the same assignment.
- LEVEL_FROM_ROOT, LEVEL_FROM_PARENT, and IMMEDIATE_PARENT_FLAG — Hierarchy depth and relationship indicators used to traverse or filter parent/child logic.
- START_DATE and END_DATE — The date-effectivity range that governs when the rule is applicable.
- ORG_ID — The operating unit, supporting multi-org access control.
- SECURITY_GROUP_ID — Foreign key to
FND_SECURITY_GROUPS, governing row-level security. - OBJECT_VERSION_NUMBER — Optimistic locking column for concurrent update protection.
- Audit columns —
CREATION_DATE,CREATED_BY,LAST_UPDATE_DATE,LAST_UPDATED_BY, and thePROGRAM_*/REQUEST_IDconcurrent program context fields.
The physical row identifier is typically TERR_ID combined with the effectivity range, while TERR_ID alone is the dominant business-key candidate.
Common Use Cases and Queries
This table is primarily consumed by the Territory Manager and trade management evaluation engine. Common practical scenarios include:
- Retrieving all denormalized territories active as of a given date for a specific operating unit.
- Identifying top-level and immediate-parent territories to reconstruct hierarchy views.
- Ranking qualifying territories to determine assignment winners.
A representative query:
SELECT terr_id, rank, absolute_rank, level_from_root, start_date, end_date
FROM jtf.jty_denorm_dea_rules_all
WHERE org_id = :p_org_id
AND TRUNC(SYSDATE) BETWEEN start_date AND end_date
ORDER BY absolute_rank;
Reporting use cases include audit reports on stale denormalized rows, hierarchy-depth analytics, and data-quality checks comparing this table against JTF_TERR_ALL.
Related Objects
- JTF_TERR_ALL — Parent territory definition; joined on
TERR_ID. - FND_SECURITY_GROUPS — Security group reference; joined on
SECURITY_GROUP_ID. - JTF_TERR_RULES / JTF_TERR_DENORM_* related structure — Territory rule definitions feeding the denormalization process.
- FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — referenced through
REQUEST_ID,PROGRAM_ID, andPROGRAM_APPLICATION_IDfor the batch denormalization job that populates this table. - JTF_TERR_USAGE / JTF_TERR_RESOURCES — Territory usage and resource assignments that consume denormalized rule output.
Because the denormalization process is periodic, administrators should validate freshness of this table against JTF_TERR_ALL after any territory hierarchy change.
-
Table: JTY_DENORM_DEA_RULES_ALL
12.1.1
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTY_DENORM_DEA_RULES_ALL, object_name:JTY_DENORM_DEA_RULES_ALL, status:VALID, product: JTF - CRM Foundation , description: This table stores denormalized territories for date effectivity assignment. , implementation_dba_data: JTF.JTY_DENORM_DEA_RULES_ALL ,
-
Table: JTY_DENORM_DEA_RULES_ALL
12.2.2
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTY_DENORM_DEA_RULES_ALL, object_name:JTY_DENORM_DEA_RULES_ALL, status:VALID, product: JTF - CRM Foundation , description: This table stores denormalized territories for date effectivity assignment. , implementation_dba_data: JTF.JTY_DENORM_DEA_RULES_ALL ,
-
VIEW: JTF.JTY_DENORM_DEA_RULES_ALL#
12.2.2
owner:JTF, object_type:VIEW, object_name:JTY_DENORM_DEA_RULES_ALL#, status:VALID,
-
SYNONYM: APPS.JTY_DENORM_DEA_RULES_ALL
12.1.1
owner:APPS, object_type:SYNONYM, object_name:JTY_DENORM_DEA_RULES_ALL, status:VALID,
-
SYNONYM: APPS.JTY_DENORM_DEA_RULES_ALL
12.2.2
owner:APPS, object_type:SYNONYM, object_name:JTY_DENORM_DEA_RULES_ALL, status:VALID,
-
VIEW: JTF.JTY_DENORM_DEA_RULES_ALL#
12.2.2
-
TABLE: JTF.JTY_DENORM_DEA_RULES_ALL
12.2.2
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTY_DENORM_DEA_RULES_ALL, object_name:JTY_DENORM_DEA_RULES_ALL, status:VALID,
-
TABLE: JTF.JTY_DENORM_DEA_RULES_ALL
12.1.1
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTY_DENORM_DEA_RULES_ALL, object_name:JTY_DENORM_DEA_RULES_ALL, status:VALID,
-
PACKAGE BODY: APPS.JTY_TERR_ENGINE_GEN2_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:JTY_TERR_ENGINE_GEN2_PVT, status:VALID,
-
PACKAGE BODY: APPS.JTY_TERR_ENGINE_GEN2_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:JTY_TERR_ENGINE_GEN2_PVT, status:VALID,
-
PACKAGE BODY: APPS.JTY_TAE_INDEX_CREATION_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:JTY_TAE_INDEX_CREATION_PVT, status:VALID,
-
PACKAGE BODY: APPS.JTY_TERR_ENGINE_GEN_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:JTY_TERR_ENGINE_GEN_PVT, status:VALID,
-
PACKAGE BODY: APPS.JTY_TERR_DENORM_RULES_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:JTY_TERR_DENORM_RULES_PVT, status:VALID,
-
PACKAGE BODY: APPS.JTY_TAE_INDEX_CREATION_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:JTY_TAE_INDEX_CREATION_PVT, status:VALID,
-
PACKAGE BODY: APPS.JTY_TERR_DENORM_RULES_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:JTY_TERR_DENORM_RULES_PVT, status:VALID,
-
PACKAGE BODY: APPS.JTY_TERR_ENGINE_GEN_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:JTY_TERR_ENGINE_GEN_PVT, status:VALID,
-
APPS.JTY_TERR_DENORM_RULES_PVT SQL Statements
12.2.2
-
APPS.JTY_TERR_DENORM_RULES_PVT SQL Statements
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 FND Design Data
12.2.2
-
12.1.1 FND Design Data
12.1.1
-
PACKAGE BODY: APPS.JTY_TERR_DENORM_RULES_PVT
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.JTY_TAE_INDEX_CREATION_PVT dependencies on JTY_DENORM_DEA_RULES_ALL
12.1.1
-
APPS.JTY_TERR_DENORM_RULES_PVT dependencies on JTY_DENORM_DEA_RULES_ALL
12.1.1
-
APPS.JTY_TERR_ENGINE_GEN_PVT dependencies on JTY_DENORM_DEA_RULES_ALL
12.1.1
-
APPS.JTY_TERR_ENGINE_GEN2_PVT dependencies on JTY_DENORM_DEA_RULES_ALL
12.1.1
-
APPS.JTY_TERR_ENGINE_GEN_PVT dependencies on JTY_DENORM_DEA_RULES_ALL
12.2.2
-
PACKAGE BODY: APPS.JTY_TERR_DENORM_RULES_PVT
12.1.1
-
APPS.JTY_TERR_ENGINE_GEN_PVT SQL Statements
12.1.1
-
APPS.JTY_TERR_DENORM_RULES_PVT dependencies on JTY_DENORM_DEA_RULES_ALL
12.2.2
-
APPS.JTY_TERR_ENGINE_GEN2_PVT dependencies on JTY_DENORM_DEA_RULES_ALL
12.2.2
-
APPS.JTY_TAE_INDEX_CREATION_PVT dependencies on JTY_DENORM_DEA_RULES_ALL
12.2.2
-
APPS.JTY_TAE_INDEX_CREATION_PVT SQL Statements
12.1.1
-
APPS.JTY_TAE_INDEX_CREATION_PVT SQL Statements
12.2.2
-
APPS.JTY_TAE_GEN_PVT SQL Statements
12.2.2
-
APPS.JTY_TAE_GEN_PVT SQL Statements
12.1.1
-
APPS.JTY_TERR_ENGINE_GEN2_PVT SQL Statements
12.1.1
-
APPS.JTY_TERR_ENGINE_GEN2_PVT SQL Statements
12.2.2
-
APPS.JTY_TERR_ENGINE_GEN_PVT SQL Statements
12.2.2
-
APPS.JTY_TERR_DENORM_RULES_PVT dependencies on JTF_TERR_QUAL_ALL
12.1.1
-
APPS.JTY_TERR_DENORM_RULES_PVT dependencies on JTF_TERR_QUAL_ALL
12.2.2
-
APPS.JTY_TAE_INDEX_CREATION_PVT dependencies on JTF_TERR_QTYPE_USGS_ALL
12.1.1
-
APPS.JTY_TAE_INDEX_CREATION_PVT dependencies on JTF_TERR_QTYPE_USGS_ALL
12.2.2
-
APPS.JTY_TERR_DENORM_RULES_PVT dependencies on JTF_QUAL_TYPE_USGS_ALL
12.1.1
-
APPS.JTY_TERR_DENORM_RULES_PVT dependencies on JTF_QUAL_TYPE_USGS
12.1.1
-
APPS.JTY_TERR_DENORM_RULES_PVT dependencies on JTF_QUAL_TYPE_USGS_ALL
12.2.2
-
APPS.JTY_TERR_DENORM_RULES_PVT dependencies on JTF_QUAL_TYPE_USGS
12.2.2
-
APPS.JTY_TAE_INDEX_CREATION_PVT dependencies on JTY_DEA_ATTR_PROD_FACTORS
12.1.1