Search Results comp_name_range




Overview
Explore in AI Chat

Overview

APPS.JTF_TASK_TERRITORY_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It exposes task records from the CRM Task Manager (JTF_TASKS_VL) joined to customer party, location, and contact point data, presenting a flattened result set intended for downstream reporting, territory assignment, and integration consumption. The view derives from the Territory Management (JTF/ETRM) object family and is owned by the APPS schema. Its principal function is to supply a denormalized projection of a task together with its associated customer, address, and geographic attributes, so that consumers do not have to manually join the underlying HZ tables.

Underlying Base Objects

The view is defined over the following documented objects, all referenced via APPS synonyms:

Key Columns

  • TASK_ID — unique identifier of the task record.
  • PARTY_ID — the customer identifier, aliased from TASK.CUSTOMER_ID.
  • ADDRESS_ID — the party site identifier associated with the task.
  • COUNTRY, CITY, STATE, POSTAL_CODE, COUNTY, PROVINCE — geographic attributes sourced from HZ_LOCATIONS.
  • AREA_CODE — phone area code from HZ_CONTACT_POINTS.
  • COMP_NAME_RANGE — customer name returned by JTF_TASK_UTL.get_customer_name.
  • TASK_TYPE_ID, TASK_STATUS_ID, TASK_PRIORITY_ID — task classification identifiers.
  • NUM_OF_EMPLOYEES — defined as a literal NULL in the view text, retained as a placeholder column for compatibility with callers that expect the territory attribute set.

Common Use Cases and Queries

The view is typically used where a task must be reviewed in the context of its customer's location and contact information, and where the standard territory column set (including the NUM_OF_EMPLOYEES placeholder) is required by the calling application or report template.

  • Territory and task reporting — listing tasks with their customer's city, state, and country for regional analysis.
  • Contact extraction — retrieving area codes alongside task and customer identifiers.
  • Integration feeds — supplying a stable column contract to external systems, including the placeholder NUM_OF_EMPLOYEES column.

A representative query filters by task status and selects the geographic and customer attributes:

SELECT task_id, party_id, comp_name_range, city, state, country, area_code
FROM apps.jtf_task_territory_v
WHERE task_status_id = :p_status;

Because NUM_OF_EMPLOYEES is a literal NULL, a query such as SELECT num_of_employees FROM apps.jtf_task_territory_v succeeds structurally but always returns no value, which is an important consideration for report designers and integrators expecting a populated headcount attribute.