Results for “owner_type_code”

50+ results




Overview
Explore in AI Chat

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

Overview

The view APPS.IEU_UWQ_ESC_MYOWN_V is a component of the Oracle E-Business Suite Universal Work Queue (UWQ), a module within the Interaction & Escalation (IEU) product family. Its documented purpose is to serve as a data source for the UWQ selector SpreadTable, which presents escalations to agents in a tabular work queue format. The view exposes a business-user-oriented projection of escalation records combined with the object-function metadata required by the UWQ runtime to render and route work items correctly.

In Oracle EBS 12.1.1 and 12.2.2 the object resides in the APPS schema with a status of VALID. Because it presents a denormalised, display-ready row set, it is typically consumed by UWQ selector configuration rather than by direct end-user reporting. Users searching for cust_account_number encounter this view because it projects the CUST_ACCOUNT_NUMBER column, linking each escalation to the customer account associated with the underlying business object. This makes the view a natural retrieval point for escalation-to-customer traceability in service and collections scenarios.

Underlying Base Objects

The documented definition joins JTF_ESC_UWQ_V (alias A) to JTF_OBJECTS_B (alias B), restricted by B.OBJECT_CODE = 'ESC'. JTF_ESC_UWQ_V is itself a UWQ-specific escalation view that supplies the escalation attributes, while JTF_OBJECTS_B supplies the object-function and object-parameter metadata used by the UWQ framework. Both are accessed through synonyms in the APPS schema. The documented base-object lineage also references FND_GLOBAL and JTF_EC_UTIL and JTF_TASK_UTL packages, which support security context and task/escalation utility processing beneath the view stack. Because JTF_ESC_UWQ_V carries the substantive escalation data, the effective row grain of IEU_UWQ_ESC_MYOWN_V is one row per escalation, enriched with object metadata from JTF_OBJECTS_B.

Key Columns

Common Use Cases and Queries

Typical usage includes locating an escalation by customer account, producing work-queue extracts for an owning resource, and monitoring open escalations against target dates. The following sample retrieves open escalations for a specific customer account:

  • SELECT escalation_number, escalation_name, cust_account_number, owner, target_date FROM apps.ieu_uwq_esc_myown_v WHERE cust_account_number = :p_account AND escalation_status = 'OPEN' ORDER BY target_date;
  • SELECT escalation_id, escalation_name, cust_account_number, escalation_level_name, owner FROM apps.ieu_uwq_esc_myown_v WHERE owner_id = :p_resource_id;
  • Ageing extract: SELECT cust_account_number, TRUNC(SYSDATE) - TRUNC(open_date) age_days, escalation_status FROM apps.ieu_uwq_esc_myown_v WHERE escalation_status NOT IN ('CLOSED','CANCELLED');

Because the view is subject to UWQ security and join semantics rather than being a pure reporting object, it should be queried with appropriate bind filters and, where volume is significant, restricted by owner or status to avoid full scans against the underlying escalation views.