Results for “ast_perz_query_v”

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

Overview

AST_PERZ_QUERY_V is a reporting and integration view within the Oracle E-Business Suite TeleSales (AST) module. It exposes personalized query definitions that drive the TeleSales user interface, allowing agents and administrators to retrieve, display, and reuse saved query criteria against customer, contact, and opportunity data. In ETRM 12.1.1 and 12.2.2, the view is documented as a lightweight projection over the JTF_PERZ_QUERY base table, exposing the same column set without any additional joins, filters, or transformations. Its principal role is to provide a stable, read-oriented interface for concurrent programs, OA Framework pages, and external integrations that need to resolve query definitions by profile context. Because the view surfaces PROFILE_ID directly, it is the natural access point for consumers that resolve which saved queries belong to a given profile, responsibility, or user configuration.

Underlying Base Objects

The view is defined over a single base table, JTF_PERZ_QUERY, which resides in the Oracle Customer Relationship Management (CRM) foundation schema shared across TeleSales, iStore, and related modules. The view text is a straightforward SELECT of all thirteen columns from that table, with no WHERE clause, DISTINCT, aggregation, or outer join. Consequently, every row in JTF_PERZ_QUERY is visible through AST_PERZ_QUERY_V, and no row-level security, org context, or multi-org partitioning is applied at the view layer. The ETRM metadata notes that the view is not implemented in the documented database and lists no additional referenced base objects. This means DBA validation should confirm the view exists in the target instance before dependent code is deployed, and that grants on JTF_PERZ_QUERY flow appropriately to the view owner.

Key Columns

• QUERY_ID — Primary identifier for the personalized query definition; referenced by dependent query and result structures.
• PROFILE_ID — Foreign key to the profile (JTF_PERZ_PROFILES / user or responsibility-level personalization) that owns the query. This is the column users most frequently search on to scope queries to a specific profile.
• APPLICATION_ID — Identifies the application context that owns the query, enabling cross-application filtering.
• QUERY_NAME and QUERY_DESCRIPTION — Display attributes presented to TeleSales users in query pickers.
• QUERY_TYPE and QUERY_DATA_SOURCE — Classify the query and indicate the underlying data source used to resolve results.
• OBJECT_VERSION_NUMBER — Optimistic locking token for concurrent updates.
• CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

The view supports profile-driven query resolution, administrative auditing of saved queries, and data migration of personalization between environments. A typical lookup resolves all queries for a given profile:

• SELECT query_id, query_name, query_type FROM ast_perz_query_v WHERE profile_id = :profile_id ORDER BY query_name;
• SELECT q.query_name, q.application_id FROM ast_perz_query_v q WHERE q.profile_id = :profile_id AND q.query_type = :query_type;
• SELECT COUNT(*) FROM ast_perz_query_v WHERE last_update_date >= :since_date;

Because no filtering is applied, consumers should always constrain on PROFILE_ID or APPLICATION_ID to avoid full scans. For write operations, the base table JTF_PERZ_QUERY must be used directly, as the view is intended for read access only.