Results for “jtf_terr_rsc”

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

Overview

JTF_TERR_RSC is a reporting and integration view in the Oracle E-Business Suite CRM Foundation (JTF) module. Its documented description states that it is "same as JTF_TERR_RSC_ALL table," indicating that the view presents the full column set of the territory-resource assignment entity without applying an operating-unit or security filter. In ETRM 12.2.2 metadata the view is listed with no independently documented owner or referenced base objects, and the implementation data notes that it is "not implemented in this database." The view therefore functions as a logical, read-oriented presentation of territory resource assignments that integrations, concurrent programs, and ad hoc reports can query using a stable, well-known name rather than referencing the underlying ALL table directly.

Underlying Base Objects

The view text exposes a single base object: JTF_TERR_RSC_ALL. The SELECT list projects every documented column from that table without a WHERE clause, confirming the "same as" description in the ETRM metadata. In Oracle CRM Foundation, the _ALL suffix conventionally denotes the unrestricted storage table, while a corresponding view (here JTF_TERR_RSC) is intended to be the access point that applications query. Because the projection is unfiltered, any row-level restriction normally associated with organizational or user security must come from the calling application, a secured synonym, or a WHERE clause supplied by the query itself. The documented "Referenced base objects: none" entry reflects that ETRM did not register a formal foreign-key dependency for this view, so developers should treat JTF_TERR_RSC_ALL as the authoritative source when tracing data lineage.

Key Columns

The view returns the following columns, each carrying standard EBS audit or territory-assignment meaning:

• TERR_RSC_ID — Primary identifier for the territory-resource assignment record.
• TERR_ID — Foreign key to the territory definition that owns the assignment.
• RESOURCE_ID, RESOURCE_TYPE — The assigned resource and its category (for example, a person, group, or organization).
• PERSON_ID — The underlying person identifier when the resource is a person.
• GROUP_ID — Grouping identifier used in resource-group scenarios.
• ROLE — Role the resource plays within the territory.
• PRIMARY_CONTACT_FLAG, FULL_ACCESS_FLAG — Boolean indicators for primary contact status and full access rights.
• START_DATE_ACTIVE, END_DATE_ACTIVE — Effective-dating window for the assignment.
• ORG_ID — Operating unit that owns the record, important for multi-org reporting.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns used for change tracking and data extraction windows.

Common Use Cases and Queries

Typical uses include territory membership reporting, resource eligibility lookups for CRM routing, and incremental extracts driven by the audit columns. A basic listing by territory might read:

SELECT terr_rsc_id, terr_id, resource_id, resource_type, role, primary_contact_flag, start_date_active, end_date_active, org_id FROM jtf_terr_rsc WHERE terr_id = :p_terr_id AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));

For multi-org reporting, constrain by operating unit: SELECT ... FROM jtf_terr_rsc WHERE org_id = :p_org_id;. For incremental interfaces, filter on the audit columns, for example WHERE last_update_date >= :p_since. Because the view performs no filtering of its own, every query must supply the appropriate TERR_ID, ORG_ID, or date predicates to avoid returning the entire JTF_TERR_RSC_ALL population.