Search Results oa_web_function_parameters




Overview

JTF_OBJECTS_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema within the JTF – CRM Foundation product family. It is defined over the base table JTF_OBJECTS_B (which stores language-independent object definition data) and the translation table JTF_OBJECTS_TL (which stores translated descriptive attributes). The view joins the two by OBJECT_CODE and filters translations using USERENV('LANG'), so that queries return only the rows matching the session language. It also performs an outer join to FND_APPLICATION_VL to expose the application name associated with each object.

Functionally, JTF_OBJECTS_VL serves as the central metadata repository for CRM Foundation "objects" that drive lookups, LOV (List of Values) definitions, and navigational behavior. Columns such as SELECT_NAME, SELECT_DETAILS, FROM_TABLE, WHERE_CLAUSE, ORDER_BY_CLAUSE, LOV_WINDOW_TITLE, LOV_NAME_TITLE, and LOV_DETAILS_TITLE define how an LOV is constructed and titled at runtime. Because of this, the view is a frequent target for developers and administrators who need to diagnose, copy, or extend LOV behavior across EBS 12.1.1 and 12.2.2. The user search term "lov_details_title" corresponds directly to the LOV_DETAILS_TITLE column, which holds the translated heading displayed above the details region of a specific LOV window.

Underlying Base Objects

The documented base objects referenced by this view are:

  • JTF_OBJECTS_B (synonym) – the base table holding non-translated attributes including the object code, SQL selection fragments, URL, launch method, web function references, and audit columns.
  • JTF_OBJECTS_TL (synonym) – the translation table providing NAME, DESCRIPTION, LOV_WINDOW_TITLE, LOV_NAME_TITLE, and LOV_DETAILS_TITLE per language.
  • FND_APPLICATION_VL (view) – the Applications MLS view, outer-joined on APPLICATION_ID to resolve APPLICATION_NAME.

The join condition B.OBJECT_CODE = T.OBJECT_CODE AND T.LANGUAGE = USERENV('LANG') makes the view language-sensitive, while the outer join APPS.APPLICATION_ID (+) = B.APPLICATION_ID ensures objects without a valid application still appear. In 12.1.1 and 12.2.2 the same definition applies, though 12.2.x may expose additional OA framework columns such as OA_WEB_FUNCTION_NAME and OA_WEB_FUNCTION_PARAMETERS that support the newer web-based UI stack.

Key Columns

Among the most operationally significant columns are:

  • OBJECT_CODE / SELECT_ID – unique identifiers linking an LOV definition to its base record.
  • SELECT_NAME, SELECT_DETAILS, FROM_TABLE, WHERE_CLAUSE, INACTIVE_CLAUSE, ORDER_BY_CLAUSE – the SQL fragments that define what an LOV retrieves and how results are filtered and sorted.
  • LOV_DETAILS_TITLE, LOV_NAME_TITLE, LOV_WINDOW_TITLE – translated titles controlling the appearance of LOV windows; these are the columns most often referenced when troubleshooting user-facing LOV captions.
  • NAME, DESCRIPTION – translated labels for the object itself.
  • URL, LAUNCH_METHOD, WEB_FUNCTION_NAME, WEB_FUNCTION_PARAMETERS, OA_WEB_FUNCTION_NAME, OA_WEB_FUNCTION_PARAMETERS – navigation and invocation metadata for launching the target page or function.
  • APPLICATION_ID, APPLICATION_NAME – ownership/responsibility context resolved via FND_APPLICATION_VL.
  • START_DATE_ACTIVE, END_DATE_ACTIVE, SEEDED_FLAG – lifecycle and seed-data indicators.
  • ATTRIBUTE1–15, ATTRIBUTE_CATEGORY – descriptive flexfield storage.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard audit and concurrency columns.

Common Use Cases and Queries

Typical uses include auditing LOV definitions, comparing seeded versus custom objects, and confirming translated titles for a given language. A representative query locating a specific LOV by its details title might read:

  • SELECT object_code, name, lov_details_title, lov_window_title, application_name FROM apps.jtf_objects_vl WHERE lov_details_title LIKE '&search%';
  • SELECT object_code, select_name, from_table, where_clause FROM apps.jtf_objects_vl WHERE object_code = :object_code;
  • SELECT object_code, url, launch_method, web_function_name FROM apps.jtf_objects_vl WHERE application_id = :app_id AND launch_method = 'WEB';

Because the view honors USERENV('LANG'), results reflect the language of the connecting session. Developers extending CRM Foundation LOVs should treat JTF_OBJECTS_B as the update target for structural changes and JTF_OBJECTS_TL for translated titles; JTF_OBJECTS_VL should generally be used for read-only reporting and diagnostics to avoid the ambiguity of joining multiple base tables directly.