Results for “jtf_terr_usgs”

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

Overview

JTF_TERR_USGS is a CRM Foundation (JTF) database view shipped within the Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. According to the ETRM metadata, the view performs a straightforward projection over the JTF_TERR_USGS_ALL table, presenting the same column set without the Multi-Org security filtering that the underlying "_ALL" table typically supports. In the JTF schema, objects prefixed with JTF relate to CRM Foundation components, and the TERR_ prefix denotes territory management structures. The USGS suffix refers to territory usages, that is, the assignments or usages of a territory within a given organizational or source context.

Because the view exposes organization-specific rows, it plays a role in reporting and integration where consumers need territory usage data scoped to the current operating unit or where the querying session has already applied organizational context through other means. It is commonly referenced by territory management concurrent programs, CRM reporting extracts, and custom integrations that resolve territory membership for leads, opportunities, and other CRM entities.

Underlying Base Objects

The documented view text is a single SELECT from one base object:

• JTF_TERR_USGS_ALL — the base table holding territory usage assignments, including the operating unit discriminator (ORG_ID).

The ETRM metadata explicitly states that the view returns "same as JTF_TERR_USGS_ALL table," and no additional joins, filters, or aggregations are documented. The view layer is therefore a logical alias rather than a transformation; it does not add security predicates within its own definition. ETRM notes that the object is "not implemented in this database" for the documented environment, which is a common notation when a view exists in the file system but is not deployed in a particular instance. The metadata records no owner and no further referenced base objects, reinforcing the single-table dependency.

Key Columns

The view exposes nine columns derived directly from the base table:

• TERR_USG_ID — primary key identifying each territory usage record.
• TERR_ID — foreign key to the territory (JTF_TERRITORIES) to which the usage applies.
• SOURCE_ID — identifies the source entity or object associated with the usage, enabling polymorphic linkage to CRM entities such as resources, customers, or leads.
• ORG_ID — the operating unit discriminator supporting Multi-Org access control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording the most recent modification.
• CREATION_DATE, CREATED_BY — standard WHO columns capturing record creation.

Common Use Cases and Queries

Typical scenarios include resolving which territories a source record belongs to, auditing territory assignments by operating unit, and feeding territory data into CRM reports or downstream integrations.

Retrieve all usages for a given territory:

• SELECT TERR_USG_ID, TERR_ID, SOURCE_ID, ORG_ID FROM JTF_TERR_USGS WHERE TERR_ID = :terr_id;

List recent assignments for an operating unit:

• SELECT TERR_USG_ID, SOURCE_ID, CREATION_DATE FROM JTF_TERR_USGS WHERE ORG_ID = :org_id ORDER BY CREATION_DATE DESC;

Audit recently modified usages:

• SELECT TERR_USG_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM JTF_TERR_USGS WHERE LAST_UPDATE_DATE > SYSDATE - 30;

Because the view does not embed organizational security predicates, queries should apply the appropriate ORG_ID filter or rely on Multi-Org initialization to enforce data isolation. Where the view is not deployed, the equivalent query can be issued against JTF_TERR_USGS_ALL directly.