Results for “jtf_am_screen_setups_vl”

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

Overview

JTF_AM_SCREEN_SETUPS_VL is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the JTF – CRM Foundation product family. It exposes the configuration metadata that governs how the Assignment Manager user interface is rendered for a given document type. Assignment Manager drives the rules-based routing and assignment of CRM entities such as leads, opportunities, service requests, and territories, and the screen setup records determine which assignment modes, informational panels, and workspace characteristics are presented to the end user.

The view serves a reporting and integration role rather than a transactional one. Because the underlying descriptive text is stored in a translated table, the VL view resolves the language-specific row using the session language through USERENV('LANG'). This allows forms, concurrent programs, OAF pages, and custom reports to retrieve the correct localized preference name without embedding language logic in application code. The object is documented as VALID in the ETRM metadata for both 12.1.1 and 12.2.2, and its structure is consistent across those releases.

Underlying Base Objects

The view is defined over two documented base objects: JTF_AM_SCREEN_SETUPS_B (the base table holding language-independent attributes and the primary key SCREEN_SETUP_ID) and JTF_AM_SCREEN_SETUPS_TL (the translation table holding PREFERENCE_NAME per language). Both are referenced through APPS synonyms.

The join condition links B.SCREEN_SETUP_ID to T.SCREEN_SETUP_ID and restricts T.LANGUAGE to the session language. All B columns are projected, plus T.PREFERENCE_NAME. The row identity is supplied as B.ROWID aliased ROW_ID, which is a characteristic pattern for translated views that must remain updatable through the base table.

Key Columns

• ROW_ID – the ROWID of the base table row, used for direct row access.
• SCREEN_SETUP_ID – primary key identifying a screen setup definition.
• DOCUMENT_TYPE – the CRM entity or document the setup applies to.
• MODE_ASSIST / MODE_UNASSIST – flags controlling assisted and unassisted assignment modes.
• CONTRACTS / INSTALLED_BASE – flags enabling the contracts and installed base informational panels within the assignment workspace. The INSTALLED_BASE column corresponds directly to the user's search term and indicates whether installed base details are surfaced during assignment.
• TERRITORY / AVAILABILITY – flags for territory and availability panels.
• DOC_DETAILS / DOC_DTLS_USER_VALUES – control over document detail display and user-defined detail values.
• WINDOW_WIDTH, WINDOW_HEIGHT, WINDOW_X_POSITION, WINDOW_Y_POSITION – sizing and placement of the assignment window.
• SHOW_SELECTED_TIME – controls visibility of the selected time indicator.
• OBJECT_VERSION_NUMBER – optimistic locking column.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, USER_ID – standard audit and ownership columns.
• PREFERENCE_NAME – the translated display name sourced from the TL table.

Common Use Cases and Queries

Typical usage includes verifying which information panels are enabled for a document type, auditing customizations applied to screen setups, and joining setup data to assignment rules for diagnostics. A representative query lists active installed base configurations:

• SELECT screen_setup_id, document_type, preference_name, installed_base, contracts, territory FROM jtf_am_screen_setups_vl WHERE installed_base = 'Y';
• SELECT document_type, preference_name, window_width, window_height FROM jtf_am_screen_setups_vl ORDER BY document_type;
• SELECT s.screen_setup_id, s.preference_name, s.installed_base FROM jtf_am_screen_setups_vl s WHERE s.last_update_date > SYSDATE - 30;

Because the view resolves language automatically, these queries return localized preference names for the connected user's session, making them suitable for both ad hoc DBA verification and embedded reporting logic.