Results for “jtf_terr_qtype_usgs”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
JTF_TERR_QTYPE_USGS is a CRM Foundation (JTF) view shipped within the Oracle E-Business Suite 12.1.1 and 12.2.2 technology stacks. It exposes the same column set as the underlying JTF_TERR_QTYPE_USGS_ALL table and exists primarily to provide a multi-organization (org-secured) access layer over territory qualification-type usage data. The view is defined as a simple projection of JTF_TERR_QTYPE_USGS_ALL, selecting TERR_QTYPE_USG_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, TERR_ID, QUAL_TYPE_USG_ID, and ORG_ID.
Within the ETRM functional model, territory qualification types describe how a territory qualifies or categorizes leads, customers, or resources. The JTF_TERR_QTYPE_USGS view therefore supports reporting and integration around the association between a territory (TERR_ID) and a qualification type usage (QUAL_TYPE_USG_ID). Because it includes ORG_ID, it participates in the standard EBS multi-org security model, whereas the _ALL table is the base repository used for convergent, cross-organization processing.
Note that the ETRM metadata records this view as "Not implemented in this database," meaning it may not be instantiated in every environment. Developers must verify existence before referencing it in custom code.
Underlying Base Objects
The only documented base object is JTF_TERR_QTYPE_USGS_ALL. The view performs no joins, filtering, or aggregation; it is a one-to-one, row-for-row projection:
- JTF_TERR_QTYPE_USGS_ALL — the physical table storing territory qualification-type usage records. The view selects directly from this table without a WHERE clause on the view definition itself.
Because org security filtering is not embedded in the view SQL, any multi-org restriction is applied through the application layer or via a custom predicate on ORG_ID. No other documented base objects are referenced, and ETRM lists no additional dependencies.
Key Columns
- TERR_QTYPE_USG_ID — Primary key for the qualification-type-usage record.
- TERR_ID — Foreign key to the territory (JTF_TERRITORIES) being associated.
- QUAL_TYPE_USG_ID — Identifier of the qualification type usage being linked to the territory.
- ORG_ID — Operating unit / organization identifier enabling multi-org partitioning.
- CREATED_BY, CREATION_DATE — Standard audit columns recording who created the row and when.
- LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the last modification user, timestamp, and login session.
Common Use Cases and Queries
Typical scenarios include territory modeling reports, integration extracts feeding downstream CRM or analytics systems, and troubleshooting qualification-type assignments. A basic query limited to a specific operating unit:
- SELECT q.TERR_QTYPE_USG_ID, q.TERR_ID, q.QUAL_TYPE_USG_ID, q.ORG_ID, q.LAST_UPDATE_DATE FROM JTF_TERR_QTYPE_USGS q WHERE q.ORG_ID = :p_org_id;
- Joining to territory and qualification usage definitions to resolve names: SELECT t.NAME territory_name, u.NAME usage_name FROM JTF_TERR_QTYPE_USGS q, JTF_TERRITORIES t, JTF_QUAL_TYPE_USGS u WHERE q.TERR_ID = t.TERR_ID AND q.QUAL_TYPE_USG_ID = u.QUAL_TYPE_USG_ID;
- Auditing recent changes: SELECT * FROM JTF_TERR_QTYPE_USGS WHERE LAST_UPDATE_DATE >= SYSDATE - 7;
Because the view is documented as not implemented in all databases, developers should confirm its presence via ALL_VIEWS or query the _ALL table directly when the view is unavailable. When used, it provides a straightforward, org-aware read interface consistent with CRM Foundations territory data.
-
View: JTF_TERR_QTYPE_USGS 12.2.2
Same as JTF_TERR_QTYPE_USGS_ALL table.
Not implemented in this database·Explore JTF module →
-
View: JTF_TERR_QTYPE_USGS 12.1.1
Same as JTF_TERR_QTYPE_USGS_ALL table.
Not implemented in this database·Explore JTF module →
-
VIEW: APPS.AS_TERRITORIES_V 12.2.2
-
VIEW: APPS.AS_TERRITORIES_V 12.1.1
-
This view shows the transactions that are assigned to a territory.
APPS.JTF_TERR_TRANSACTIONS_V·↳ JTF_QUAL_TYPES·↳ JTF_QUAL_TYPE_USGS·↳ JTF_TERR_QTYPE_USGS·Explore JTF module →
-
This view shows the transactions that are assigned to a territory.
APPS.JTF_TERR_TRANSACTIONS_V·↳ JTF_QUAL_TYPES·↳ JTF_QUAL_TYPE_USGS·↳ JTF_TERR_QTYPE_USGS·Explore JTF module →
-
View: AS_TERRITORIES_V 12.2.2
Territories view
APPS.AS_TERRITORIES_V·↳ JTF_QUAL_TYPES·↳ JTF_QUAL_TYPE_USGS·↳ JTF_TERR·Explore AS module →
-
View: AS_TERRITORIES_V 12.1.1
Territories view
APPS.AS_TERRITORIES_V·↳ JTF_QUAL_TYPES·↳ JTF_QUAL_TYPE_USGS·↳ JTF_TERR·Explore AS module →
-
This shows the denormalised territory transactions horizontally.
APPS.JTF_TERR_TRANS_DENORM_V·↳ JTF_QUAL_TYPE_USGS·↳ JTF_TERR·↳ JTF_TERR_QTYPE_USGS·Explore JTF module →
-
This shows the denormalised territory transactions horizontally.
APPS.JTF_TERR_TRANS_DENORM_V·↳ JTF_QUAL_TYPE_USGS·↳ JTF_TERR·↳ JTF_TERR_QTYPE_USGS·Explore JTF module →
-
VIEW: APPS.AS_TERRITORIES_V 12.2.2
-
VIEW: APPS.AS_TERRITORIES_V 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2