Search Results csf_plan_terrs_u1

Overview

CSF.CSF_PLAN_TERRS is a persistent table in the Oracle E-Business Suite Control Tower / Field Service foundation schema (CSF). Its documented purpose is to map territories to resource groups, thereby designating a resource group as a planner group for the associated territories. This mapping is consumed primarily for user interface purposes: it constrains the number of resources that appear as selectable in the Control Tower planning screens, filtering the resource population presented to a planner to those belonging to the groups mapped to the active territory.

The object is registered in FND Design Data as CSF.CSF_PLAN_TERRS, carries VALID status, and resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10. In the documented 12.2.2 physical schema the table contains 10 columns. Based on the foreign key structure mined from the schema, the heuristic Data Vault classification for this object is a link table. It does not hold descriptive attributes about a business entity in its own right; instead it materializes a many-to-many association between territories and resource groups, with the surrogate key existing only to satisfy relational integrity and ORM requirements. Modelers working with a Data Vault or dimensional representation should treat CSF_PLAN_TERRS as an intersection/link construct rather than a hub or satellite.

Key Information Stored

The table's column set combines a surrogate primary key, two foreign keys, the standard Oracle EBS WHO audit columns, and an object versioning column.

• PLAN_TERR_ID (NUMBER) — the surrogate primary key, backed by CSF_PLAN_TERRS_PK. It is a system-generated unique identifier with no business meaning.
• TERR_ID (NUMBER) — foreign key to JTF_TERR_ALL, identifying the territory being mapped.
• GROUP_ID (NUMBER) — foreign key to JTF_RS_GROUPS_B, identifying the resource group that acts as a planner group for that territory.
• TERR_ID, GROUP_ID — together these form the unique index CSF_PLAN_TERRS_U1, a NORMAL UNIQUE index in APPS_TS_TX_IDX. This is the business-key candidate: the pairing of territory and group must be unique, so no resource group can be mapped twice to the same territory.
• SECURITY_GROUP_ID (NUMBER) — foreign key to FND_SECURITY_GROUPS, the identifier used when the application runs in hosted (multi-tenant) mode.
• OBJECT_VERSION_NUMBER (NUMBER) — sequential number used for database locking control, incremented on each update of a row by the ORM layer.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording who created and last modified each row and through which login session.

Notably, the table stores no effective dates, no start/end flags, and no descriptive text: the association is binary and current-state only.

Common Use Cases and Queries

The most common access pattern is resolving which resource groups are treated as planner groups for a given territory, and conversely which territories a given group is enabled for. Both are satisfied by the unique index CSF_PLAN_TERRS_U1 and by targeted lookups on either foreign key. A typical query joins the table to the territory and group definitions:

• SELECT p.plan_terr_id, p.terr_id, p.group_id FROM csf.csf_plan_terrs p WHERE p.terr_id = :territory_id;
• SELECT p.terr_id, g.group_name FROM csf.csf_plan_terrs p, jtf_rs_groups_b g WHERE p.group_id = g.group_id AND p.terr_id = :territory_id;
• Reporting that lists all territory-to-planner-group mappings for setup review, joined to JTF_TERR_ALL for territory names.

Because the mapping drives UI filtering in the Control Tower, it is also used diagnostically when a planner reports that expected resources are missing from a selection list; verifying the presence of the appropriate GROUP_ID row for the operative TERR_ID usually resolves such issues. Queries should generally filter on SECURITY_GROUP_ID when the installation runs in hosted mode.

Related Objects

The most significant objects related to CSF_PLAN_TERRS are its foreign key parents and the dependent objects declared in the design data:

• JTF_TERR_ALL — territory definitions; joined on JTF_TERR_ALL.TERR_ID = CSF_PLAN_TERRS.TERR_ID.
• JTF_RS_GROUPS_B — resource group (planner group) definitions; joined on JTF_RS_GROUPS_B.GROUP_ID = CSF_PLAN_TERRS.GROUP_ID.
• FND_SECURITY_GROUPS — security group definitions used in hosted mode; joined on FND_SECURITY_GROUPS.SECURITY_GROUP_ID = CSF_PLAN_TERRS.SECURITY_GROUP_ID.
• CSF_PLAN_TERRS# — the policy/editioning view over the base table; it is the only documented object referencing CSF.CSF_PLAN_TERRS.

Territory assignments for individual resources are modeled separately in JTF territory-assignment tables, so reporting that requires resource-level detail typically joins across both the group mapping in CSF_PLAN_TERRS and the underlying assignment tables. The table declares no dependencies on other database objects beyond these referential relationships.