Results for “resource_group_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AS_TERR_RESOURCES_TMP is a transient staging table owned by the OSM schema within the AS – Sales Foundation product family of Oracle E-Business Suite (documented across 12.1.1 and 12.2.2). Per the ETRM metadata, its stated purpose is to "hold territory assignment results." In practice, the table acts as an intermediate landing zone used by the Territory Assignment and Resources engine: the territory assignment batch process evaluates customer parties, party sites, and leads against defined territory rules in JTF_TERR_ALL, resolves the qualifying sales resources and resource groups, and writes the candidate rows into this temporary table before they are promoted into the permanent territory resource assignments. Because the contents are scoped to a single concurrent program run, it is an ephemeral, run-scoped structure rather than a durable master or transactional entity.
From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is link. This is consistent with the table's role: it captures relationships between parties, party sites, leads, territories, resources, and resource groups rather than storing descriptive attributes about any single business entity.
Key Information Stored
The table comprises 13 documented columns. The most significant are:
- TERR_ID – The territory identifier from JTF_TERR_ALL; identifies which territory produced the assignment result.
- RESOURCE_ID – The sales resource (from JTF_RS_RESOURCE_EXTNS) assigned by the territory.
- RESOURCE_TYPE – Qualifies whether the assignment is to an individual resource or a group.
- RESOURCE_GROUP_ID – The resource group (from JTF_RS_GROUPS_B) when the territory resolves to a group rather than an individual.
- PARTY_ID – The customer party (from HZ_PARTIES) to which the assignment applies.
- PARTY_SITE_ID – The specific party site (from HZ_PARTY_SITES) in scope.
- LEAD_ID – The lead (from AS_LEADS_ALL) being assigned when the run processes lead records.
- FULL_ACCESS_FLAG – Indicates whether the resource receives full access versus constrained access to the matched entity.
- REQUEST_ID – The concurrent request that generated the row, enabling results to be isolated per run.
- PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – Standard concurrent program audit columns recording which program produced the row and when.
- SECURITY_GROUP_ID – The multi-tenant security group (from FND_SECURITY_GROUPS) under which the row was written.
The documented unique index AS_TERR_RESOURCES_TMP_U1 spans (TERR_ID, RESOURCE_ID, RESOURCE_GROUP_ID, PARTY_ID, PARTY_SITE_ID, LEAD_ID), making this composite the business-key candidate. The metadata does not document a separate single-column surrogate primary key.
Common Use Cases and Queries
Typical uses are diagnostic and reconciliation-oriented. Administrators inspect the temporary results of a territory assignment run before or after promotion, verify that a specific party or lead was correctly matched, and troubleshoot missing or duplicate assignments.
- Review the outcome of the most recent run: SELECT * FROM AS_TERR_RESOURCES_TMP WHERE REQUEST_ID = :request_id;
- Check assignments for a given party: SELECT TERR_ID, RESOURCE_ID, RESOURCE_GROUP_ID, FULL_ACCESS_FLAG FROM AS_TERR_RESOURCES_TMP WHERE PARTY_ID = :party_id;
- Reconcile against territories by joining TERR_ID to JTF_TERR_ALL.
- Audit resource-level coverage by grouping on RESOURCE_ID and RESOURCE_GROUP_ID.
- Validate run completeness using PROGRAM_UPDATE_DATE and REQUEST_ID.
Because rows are run-scoped, queries should always filter by REQUEST_ID to avoid mixing results from concurrent executions.
Related Objects
The documented foreign keys establish these principal dependencies:
- JTF_TERR_ALL via TERR_ID – the territory definition.
- JTF_RS_RESOURCE_EXTNS via RESOURCE_ID – the assigned sales resource.
- JTF_RS_GROUPS_B via RESOURCE_GROUP_ID – the assigned resource group.
- HZ_PARTIES via PARTY_ID – the customer party.
- HZ_PARTY_SITES via PARTY_SITE_ID – the party site.
- AS_LEADS_ALL via LEAD_ID – the lead record.
- FND_SECURITY_GROUPS via SECURITY_GROUP_ID – the security group context.
Taken together, these relationships confirm AS_TERR_RESOURCES_TMP as the link table bridging territory definitions, resources, and the parties, sites, and leads they are assigned to.
-
Hold territory assignment results.
-
View: BIX_RESOURCE_LOV_V 12.1.1
APPS.BIX_RESOURCE_LOV_V·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore BIX module →
-
View: BIX_RESOURCE_BASE_V 12.1.1
APPS.BIX_RESOURCE_BASE_V·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore BIX module →
-
Table for 3rd party applications to send data to be summarized along a certain number of dimensions
-
View: AS_SALES_OPP_UWQ_V 12.1.1
This view is used for Universal Work Queue
APPS.AS_SALES_OPP_UWQ_V·↳ ASO_I_SALES_CHANNELS_V·↳ AS_ACCESSES_ALL·↳ AS_FORECAST_PROB_ALL_TL·Explore AS module →
-
This view is used for Universal Work Queue
APPS.AS_SALES_FORECAST_UWQ_V·↳ AS_INTERNAL_FORECASTS·↳ JTF_RS_RESOURCE_EXTNS·Explore AS module →
-
Summarizes BIX_INTERACTIONS to the day the dimension of time, agent group, call center, campaign and interaction classification
-
This table contains information about sales credits for the salesrep.
-
View: AST_FORECAST_UWQ_V 12.2.2
APPS.AST_FORECAST_UWQ_V·↳ AS_SALES_FORECAST_UWQ_V·↳ JTF_OBJECTS_VL·Explore AST module →
-
Base View for Budget Funds Check Results - Resource Group Level
APPS.PA_RES_GRP_FC_RESULTS_V·↳ PA_BUDGETARY_CONTROLS_PKG·↳ PA_PROJECT_BAL_V·Explore PA module →
-
Base View for Budget Funds Check Results - Resource Group Level
APPS.PA_RES_GRP_FC_RESULTS_V·↳ PA_BUDGETARY_CONTROLS_PKG·↳ PA_PROJECT_BAL_V·Explore PA module →
-
Summarizes BIX_INTERACTIONS data to the day along the dimesions of time, agent group, call center, campaign and interaction classification
-
View: AST_FORECAST_UWQ_V 12.1.1
APPS.AST_FORECAST_UWQ_V·↳ AS_SALES_FORECAST_UWQ_V·↳ JTF_OBJECTS_VL·Explore AST module →
-
Hold territory assignment results.
-
This view is used for Universal Work Queue
APPS.AS_SALES_FORECAST_UWQ_V·↳ AS_INTERNAL_FORECASTS·↳ JTF_RS_RESOURCE_EXTNS·Explore AS module →
-
View: AS_SALES_OPP_UWQ_V 12.2.2
This view is used for Universal Work Queue
APPS.AS_SALES_OPP_UWQ_V·↳ ASO_I_SALES_CHANNELS_V·↳ AS_ACCESSES_ALL·↳ AS_FORECAST_PROB_ALL_TL·Explore AS module →
-
View: AST_SALES_OPP_UWQ_V 12.1.1
APPS.AST_SALES_OPP_UWQ_V·↳ AS_ACCESSES_ALL·↳ AS_FORECAST_PROB_ALL_TL·↳ AS_LEADS_ALL·Explore AST module →
-
Table: OKI_SRM_004_MV 12.1.1
-
Summarizes BIX_INTERACTIONS data to the day along the dimensions of time, agent group, call center, campaign and interaction classification
-
View: OKX_QTE_SLS_CREDITS_V 12.1.1
Sales credits given to Sales persons
APPS.OKX_QTE_SLS_CREDITS_V·↳ ASO_SALES_CREDITS·Explore OKX module →
-
Store the parameters user entered in the Planning Detailed Reports
-
Store the parameters user entered in the Planning Detailed Reports
-
APPS.MSC_PDR_LATE_ORDER_EXC_V·↳ FND_GLOBAL·↳ MSC_EXCEPTION_DETAILS_V·↳ MSC_GET_NAME·Explore MSC module →
-
APPS.MSC_PDR_RESOURCE_DETAILS_V·↳ FND_GLOBAL·↳ MSC_DEPARTMENT_RESOURCES·↳ MSC_GET_NAME·Explore MSC module →
-
APPS.MSC_PDR_RESOURCE_DETAILS_V·↳ FND_GLOBAL·↳ MSC_DEPARTMENT_RESOURCES·↳ MSC_GET_NAME·Explore MSC module →
-
View: OKX_QTE_SLS_CREDITS_V 12.2.2
Sales credits given to Sales persons
APPS.OKX_QTE_SLS_CREDITS_V·↳ ASO_SALES_CREDITS·Explore OKX module →
-
APPS.MSC_PDR_LATE_ORDER_EXC_V·↳ FND_GLOBAL·↳ MSC_EXCEPTION_DETAILS_V·↳ MSC_GET_NAME·Explore MSC module →
-
View: AST_SALES_OPP_UWQ_V 12.2.2
APPS.AST_SALES_OPP_UWQ_V·↳ AS_ACCESSES_ALL·↳ AS_FORECAST_PROB_ALL_TL·↳ AS_LEADS_ALL·Explore AST module →
-
Table: OKI_SRM_001_MV 12.1.1
-
This table contains information about sales credits for the salesrep.
-
Repository for all interaction data that we get from UWQ (Oracle Universal Work Queue)
-
View: ASO_SALES_CREDITS_V 12.1.1
APPS.ASO_SALES_CREDITS_V·↳ ASO_SALES_CREDITS·↳ JTF_RS_GROUPS_VL·↳ JTF_RS_RESOURCE_EXTNS_VL·Explore ASO module →
-
View: MSC_PDR_MAT_RES_EXC_V 12.1.1
APPS.MSC_PDR_MAT_RES_EXC_V·↳ FND_GLOBAL·↳ MSC_EXCEPTION_DETAILS_V·↳ MSC_GET_NAME·Explore MSC module →
-
View: MSC_PDR_MAT_RES_EXC_V 12.2.2
APPS.MSC_PDR_MAT_RES_EXC_V·↳ FND_GLOBAL·↳ MSC_EXCEPTION_DETAILS_V·↳ MSC_GET_NAME·Explore MSC module →
-
View: MSC_PDR_VERT_LIST_V 12.2.2
APPS.MSC_PDR_VERT_LIST_V·↳ FND_GLOBAL·↳ MFG_LOOKUPS·↳ MSC_CALENDAR_DATES·Explore MSC module →
-
Summarizes BIX_INTERACTIONS data to the day along the dimensions of time, agent, group, call center, campaign and product group
-
View: MSC_PDR_ITEM_DETAILS_V 12.2.2
APPS.MSC_PDR_ITEM_DETAILS_V·↳ FND_GLOBAL·↳ MSC_GET_NAME·↳ MSC_ITEMS·Explore MSC module →
-
View: MSC_PDR_ITEM_DETAILS_V 12.1.1
APPS.MSC_PDR_ITEM_DETAILS_V·↳ FND_GLOBAL·↳ MSC_GET_NAME·↳ MSC_ITEMS·Explore MSC module →
-
Summarizes BIX_INTERACTIONS data to the day along the dimensions of time, agent, call center, campaign and interaction classification
-
View: ASO_SALES_CREDITS_V 12.2.2
APPS.ASO_SALES_CREDITS_V·↳ ASO_SALES_CREDITS·↳ JTF_RS_GROUPS_VL·↳ JTF_RS_RESOURCE_EXTNS_VL·Explore ASO module →
-
View: MSC_PDR_VERT_LIST_V 12.1.1
APPS.MSC_PDR_VERT_LIST_V·↳ FND_GLOBAL·↳ MFG_LOOKUPS·↳ MSC_CALENDAR_DATES·Explore MSC module →
-
APPS.MSC_PDR_PLAN_DETAILS_V1·↳ FND_GLOBAL·↳ MSC_GET_NAME·↳ MSC_PDR_PARAMETERS_NEW·Explore MSC module →
-
APPS.MSC_PDR_PLAN_DETAILS_V1·↳ FND_GLOBAL·↳ MSC_GET_NAME·↳ MSC_PDR_PARAMETERS_NEW·Explore MSC module →
-
View: PA_FP_VP_TXNCURRENCY_V 12.2.2
This view is used for the View Plans page. It retrieves user-entered budget lines
APPS.PA_FP_VP_TXNCURRENCY_V·↳ PA_FP_TXN_LINES_TMP·↳ PA_FP_VIEW_PLANS_TXN_PUB·↳ PA_PROJ_ELEMENTS_UTILS·Explore PA module →