Results for “imc_three_sixty_query_vl”

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

Overview

IMC_THREE_SIXTY_QUERY_VL is a database view owned by the APPS schema in Oracle E-Business Suite, registered under the IMC – Customers Online product module. Its documented purpose is to expose the query definitions used by the "Three Sixty" (360-degree) customer query framework, which drives configurable, product-specific search and display panels within the Customers Online application. The view is a "VL" (view language) construct: it joins the base transactional table with its translation table so that descriptive text is returned in the language of the current session, resolved through USERENV('LANG').

In both release 12.1.1 and 12.2.2 the object is reported as VALID and is not end-dated. It functions as a reporting and integration surface over the underlying query metadata, allowing external programs, concurrent reports, and personalizations to read query configuration without touching the base tables directly.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• IMC_THREE_SIXTY_QUERY_B – the base table holding query definitions, application context, filter and display counts, product query fragments, sequence numbers, security function, product URL, and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus OBJECT_VERSION_NUMBER, BE_CODE, CATEGORY_CODE, and OPERATING_UNIT_FLAG.
• IMC_THREE_SIXTY_QUERY_TL – the translation table supplying language-dependent text, including TRANSACTION_NAME and HEADER_TEXT.

The join condition is B.QUERY_ID = T.QUERY_ID AND T.LANGUAGE = USERENV('LANG'), so exactly one translated row is returned per query for the session language. The view also projects B.ROWID as ROW_ID, providing a row identifier that downstream consumers can use for reference or update routing.

Key Columns

• QUERY_ID / APPLICATION_ID – primary identifier of the query definition and the owning application.
• TRANSACTION_NAME – the translated name of the 360-degree transaction or query; this is the column users most commonly search for when locating a query definition by name.
• HEADER_TEXT – the translated header displayed for the query result region.
• QUERY_TYPE_FLAG, FILTER_COUNT, DISPLAY_COLUMN_COUNT – classify the query and describe its filter and display structure.
• PRODUCT_QUERY1 .. PRODUCT_QUERY5 – product-specific SQL fragments associated with the query.
• SEQUENCE_NO, DISPLAY_FLAG – control ordering and whether the query is presented to users.
• SECURITY_FUNCTION, PRODUCT_URL – the function securing access and the target URL invoked by the query.
• BE_CODE, CATEGORY_CODE, OPERATING_UNIT_FLAG – business entity, category, and operating-unit scoping attributes.
• ROW_ID, OBJECT_VERSION_NUMBER, WHO columns – row identity, optimistic locking, and audit information.

Common Use Cases and Queries

Typical uses include auditing configured 360-degree queries, driving custom reports or OAF personalizations, and mapping query definitions to security functions. To locate a query by its translated transaction name:

• SELECT query_id, application_id, transaction_name, header_text FROM apps.imc_three_sixty_query_vl WHERE transaction_name LIKE '%ORDER%';
• SELECT query_id, display_flag, sequence_no, product_url FROM apps.imc_three_sixty_query_vl WHERE display_flag = 'Y' ORDER BY sequence_no;
• SELECT query_id, security_function, be_code, category_code FROM apps.imc_three_sixty_query_vl WHERE operating_unit_flag = 'Y';

Because the view is language-aware, results follow the session's NLS language setting; users requiring a specific translation must set NLS_LANG or the user language environment accordingly. All queries should be issued with the APPS schema or an appropriate synonym grant, as the view resides in APPS and references synonym-based base objects.