Search Results rs_supplier

Overview

APPS.JTF_TERR_RESOURCES_V is a reporting view in the Oracle E-Business Suite Territory Management (ETRM) module that exposes the resources assigned to territories along with their descriptive attributes. It joins the territory resource assignment table to object definition and role lookup views to produce a denormalized, human-readable result set. The view resolves internal identifiers — resource IDs, resource types, group IDs, and role codes — into descriptive names through calls to the JTF_TERRITORY_RESOURCE_PVT package and lookup joins. It is available in both EBS 12.1.1 and 12.2.2 and is owned by the APPS schema.

This view is a principal access point for reporting and integration logic that needs to enumerate which resources (employees, organizations, or supplier contacts) belong to a given territory, when those assignments are active, and what role each assignment plays. Because it hides the raw coded identifiers behind descriptive columns, it is well suited to ad hoc queries, BI Publisher data models, and integration extracts that must present territory membership in business terms.

Underlying Base Objects

The view is defined over the following documented base objects:

• JTF_TERR_RSC (synonym, aliased JTRA) — the central territory resource assignment table. Each row represents one resource-to-territory association, carrying the resource identifier, resource type, territory identifier, group, role, primary contact flag, full access flag, and active date range.
• JTF_OBJECTS_VL (view, aliased JO) — provides the translated object code and name. The join converts the RESOURCE_TYPE code into a descriptive RESOURCE_TYPE_NAME.
• JTF_RS_ROLES_VL (view, aliased JRRV) — supplies translated role names. The join is an outer join (+) on ROLE = ROLE_CODE, so assignments with no matching role definition are still returned with a null role name.
• JTF_TERRITORY_RESOURCE_PVT (package) — a PL/SQL package used inline to resolve the group name and the resource name, and referenced by the view's core logic for supplier handling.

A significant detail in the definition is the DECODE on RESOURCE_TYPE: the code 'RS_SUPPLIER' is remapped to 'RS_SUPPLIER_CONTACT' both for the join to JTF_OBJECTS_VL and for the call to GET_RESOURCE_NAME. This remapping ensures supplier resources are treated as supplier contacts for lookup and name resolution.

Key Columns

• TERR_RSC_ID — unique identifier of the territory resource assignment row.
• TERR_ID — the territory to which the resource is assigned.
• RESOURCE_ID and RESOURCE_TYPE — the resource identifier and its type code; RESOURCE_TYPE_NAME provides the descriptive equivalent from JTF_OBJECTS_VL.
• RESOURCE_NAME — the resolved descriptive name of the resource, derived via JTF_TERRITORY_RESOURCE_PVT.GET_RESOURCE_NAME.
• GROUP_ID and GROUP_NAME — the resource group identifier and its resolved name.
• ROLE and ROLE_NAME — the role code assigned to the resource and its translated description.
• PRIMARY_CONTACT_FLAG and FULL_ACCESS_FLAG — flags indicating whether the resource is the primary contact and whether it holds full access.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range of the assignment.
• ORG_ID — the operating unit context of the assignment.
• PERSON_ID — the associated person identifier where applicable.

Common Use Cases and Queries

A frequent requirement is to list all resources for a territory with descriptive names and active dates:

• SELECT TERR_ID, RESOURCE_NAME, RESOURCE_TYPE_NAME, ROLE_NAME, START_DATE_ACTIVE, END_DATE_ACTIVE FROM APPS.JTF_TERR_RESOURCES_V WHERE TERR_ID = :p_terr_id;

Because the user search term was rs_supplier, a common scenario is isolating supplier resources. Note that the view stores the code as RS_SUPPLIER, while name resolution internally maps it to RS_SUPPLIER_CONTACT. A practical query is:

• SELECT TERR_ID, RESOURCE_ID, RESOURCE_NAME, RESOURCE_TYPE, ROLE_NAME FROM APPS.JTF_TERR_RESOURCES_V WHERE RESOURCE_TYPE = 'RS_SUPPLIER' AND ORG_ID = :p_org_id;

Other typical uses include identifying primary contacts for a territory, auditing active assignments within a date window, and extracting territory membership for downstream CRM or order management integrations. When filtering, always constrain by ORG_ID to respect operating unit security, and leverage the pre-resolved name columns rather than the raw IDs to avoid additional lookups.