Search Results terr_name




Overview
Explore in AI Chat

Overview

APPS.CSF_PLAN_TERRS_V is a seeded, VALID database view in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments, owned by the APPS schema and belonging to the CSF (Field Service) product family. The view functions as the base query for a form block within the CSFSEPLT form, and it presents planning territory assignments in a denormalized, user-readable format. Its primary purpose is to expose the technical foreign key identifiers held in the CSF_PLAN_TERRS table alongside the corresponding human-readable territory and resource group names, so that Oracle Forms, concurrent programs, and custom reports do not need to perform the joins themselves. Because it encapsulates the joins to JTF_TERR_ALL and JTF_RS_GROUPS_VL, the view also centralizes the translation of territory and group identifiers into descriptive names, which is particularly relevant to users searching on terr_name.

Underlying Base Objects

The ETRM metadata records three referenced base objects: CSF_PLAN_TERRS (SYNONYM), JTF_TERR_ALL (SYNONYM), and JTF_RS_GROUPS_VL (VIEW). The defining query is:

The driving table is CSF_PLAN_TERRS, which stores the association between a planning territory and a resource group. JTF_TERR_ALL supplies the territory definition, and JTF_RS_GROUPS_VL is a translated view over resource groups, providing the group name. Because the view uses inner joins only, a planning territory row appears only when matching records exist in both referenced objects.

Key Columns

The view exposes the following columns, as documented:

  • ROW_ID — the ROWID of the underlying CSF_PLAN_TERRS row, used by Oracle Forms for update and locking semantics.
  • PLAN_TERR_ID — the primary key of the planning territory assignment.
  • TERR_ID — the foreign key to JTF_TERR_ALL, identifying the sales or service territory.
  • TERR_NAME — the territory name (T.NAME), the column most relevant to searches on terr_name.
  • GROUP_ID — the foreign key to JTF_RS_GROUPS_VL, identifying the resource group.
  • GROUP_NAME — the descriptive name of the resource group.
  • OBJECT_VERSION_NUMBER — the optimistic locking version used by the OA framework.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include validating territory-to-group planning assignments, building Field Service reports that require readable territory and group names, and troubleshooting the CSFSEPLT form. A simple query filtered by territory name is:

  • SELECT PLAN_TERR_ID, TERR_ID, TERR_NAME, GROUP_ID, GROUP_NAME FROM APPS.CSF_PLAN_TERRS_V WHERE TERR_NAME = :terr_name;
  • SELECT TERR_NAME, GROUP_NAME FROM APPS.CSF_PLAN_TERRS_V ORDER BY TERR_NAME, GROUP_NAME;
  • SELECT P.TERR_NAME, P.GROUP_NAME, P.LAST_UPDATE_DATE FROM APPS.CSF_PLAN_TERRS_V P WHERE P.GROUP_ID = :group_id;

Because the view joins translated views, query performance depends on indexed access to JTF_TERR_ALL and JTF_RS_GROUPS_VL. Reports should filter on TERR_ID or GROUP_ID where possible, and note that any assignment lacking a matching territory or group record will not be returned.