Results for “jtf_perz_query_param_v”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view APPS.JTF_PERZ_QUERY_PARAM_V belongs to the JTF – CRM Foundation product family within Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). As documented in ETRM, the object is a VALID VIEW owned by the APPS schema and is described as a "View for personalization data party merge." This description defines its principal architectural purpose: it consolidates profile, query, and query-parameter personalization metadata into a single denormalized result set that can be consumed during party merge processing.
In the broader EBS reporting and integration context, the view provides a stable, read-only interface over the underlying JTF personalization tables. Because the base tables are joined internally, applications, concurrent programs, and custom reports can retrieve a profile's queries and their parameter definitions without re-implementing the three-way join. This reduces the risk of inconsistent joins appearing in downstream integrations, particularly when personalization records must be re-pointed from one party to another during a merge.
Underlying Base Objects
The view is defined over three documented base objects, each referenced as a SYNONYM in the APPS schema:
- JTF_PERZ_PROFILE – source of profile-level identity information (
PROFILE_ID,PROFILE_NAME). - JTF_PERZ_QUERY – source of query definitions associated with a profile (
QUERY_ID,APPLICATION_ID,QUERY_NAME,QUERY_TYPE). - JTF_PERZ_QUERY_PARAM – source of individual parameter rows belonging to a query (
QUERY_PARAM_ID,PARAMETER_NAME,PARAMETER_TYPE,PARAMETER_VALUE).
The join is expressed as A.PROFILE_ID = B.PROFILE_ID AND B.QUERY_ID = C.QUERY_ID, making the profile the top-level driving entity. One row is returned for each combination of profile, query, and query parameter. Consequently, a single personalization query with multiple parameters produces multiple rows in this view.
Key Columns
- PROFILE_ID / PROFILE_NAME – identifies and names the personalization profile to which the query belongs.
- QUERY_ID / QUERY_NAME – uniquely identifies and names the query defined under a given profile.
- APPLICATION_ID – the Oracle Application owning the query, allowing filtering by module (for example, CRM or a related application).
- QUERY_TYPE – classifies the query for personalization purposes. Since the user query was "query_type," this column is typically the primary filter for grouping or routing personalization queries by category.
- QUERY_PARAM_ID – the unique identifier for the parameter row within the query.
- PARAMETER_NAME / PARAMETER_TYPE / PARAMETER_VALUE – describe each parameter supplied to the query, including its name, its data type, and its assigned literal or token value.
Common Use Cases and Queries
The most frequent consumer of this view is personalization data migration and party merge logic, where existing profile/query structures must be re-associated with a surviving party. Reporting on personalization configuration and auditing parameter definitions are also common.
To list all parameters associated with a specific profile:
SELECT profile_name, query_name, query_type, parameter_name, parameter_type, parameter_value FROM jtf_perz_query_param_v WHERE profile_id = :p_profile_id;
To retrieve all personalization queries of a given type across applications:
SELECT application_id, query_name, parameter_name, parameter_value FROM jtf_perz_query_param_v WHERE query_type = :p_query_type ORDER BY application_id, query_name;
Because the view is read-only and denormalized, it is well suited to ad hoc discovery of how a profile is configured, but it should not be used for direct DML. Modifications must be performed against the underlying JTF_PERZ_PROFILE, JTF_PERZ_QUERY, and JTF_PERZ_QUERY_PARAM tables through supported APIs.
-
View: JTF_PERZ_QUERY_PARAM_V 12.2.2
View for personalization data party merge
APPS.JTF_PERZ_QUERY_PARAM_V·↳ JTF_PERZ_PROFILE·↳ JTF_PERZ_QUERY·↳ JTF_PERZ_QUERY_PARAM·Explore JTF module →
-
View: JTF_PERZ_QUERY_PARAM_V 12.1.1
View for personalization data party merge
APPS.JTF_PERZ_QUERY_PARAM_V·↳ JTF_PERZ_PROFILE·↳ JTF_PERZ_QUERY·↳ JTF_PERZ_QUERY_PARAM·Explore JTF module →
-
SYNONYM: APPS.JTF_PERZ_QUERY 12.1.1
-
SYNONYM: APPS.JTF_PERZ_QUERY 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - JTF Tables and Views 12.2.2
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.2.2
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel