Search Results oa_lov

Overview

APPS.JTF_OBJECT_LOV_DTLS_V is a Customer Relationship Management (CRM) Foundation view shipped in the Oracle E-Business Suite 12.1.1 and 12.2.2 technology stacks. It exposes the configuration metadata that drives List of Values (LOV) behavior on OA Framework pages for a specific object relationship context. The view is defined around the object code JTF_OBJECT_RELATION, which is the seed mapping used by the CRM Foundation to register object relationships and surface the correct LOV region paths, parameters, and page details at runtime. Because the user searched for "jtf_object_relation", this view is the primary documented entry point that ties JTF_OBJECT_MAPPINGS records for JTF_OBJECT_RELATION to the underlying LOV page definitions and parameter mappings used by the OA Framework page rendering engine.

The view returns one row per object usage / page detail / page parameter combination filtered by the current language and the current responsibility's application ID, making it a runtime-sensitive metadata source rather than a static listing.

Underlying Base Objects

The view is defined as a UNION of two SELECT statements that differ only in how the application context is resolved. Both branches join the same core CRM Foundation tables, with the second branch adding JTF_OBJECTS_B for a fallback application resolution when no responsibility-specific page detail exists.

• JTF_OBJECTS_TL — provides the translatable name (NAME) and OBJECT_CODE for the object, filtered by USERENV('LANG').
• JTF_OBJECT_USAGES — supplies the OBJECT_USER_CODE and links to JTF_OBJECTS_TL on OBJECT_CODE.
• JTF_OBJECT_PG_DTLS — holds the PG_REGION_PATH and APPLICATION_ID, filtered to PAGE_TYPE = 'OA_LOV'.
• JTF_OBJECT_PG_PARAMS — supplies SOURCE_PARAM and DEST_PARAM, joined through OBJECT_DTLS_ID.
• JTF_OBJECT_MAPPINGS — constrains the result to the JTF_OBJECT_RELATION object code and exposes SOURCE_OBJECT_CODE.
• JTF_OBJECTS_B — used in the second UNION branch to resolve APPLICATION_ID when no responsibility-specific page detail row exists.
• FND_GLOBAL — the package supplying resp_appl_id, used to filter JOLD.APPLICATION_ID to the current responsibility's application.

Key Columns

• OBJECT_NAME — the translatable display name of the object from JTF_OBJECTS_TL.NAME.
• OBJECT_CODE — the internal code identifying the object; for this view the driving mapping is JTF_OBJECT_RELATION.
• OBJECT_USER_CODE — the user-facing code from JTF_OBJECT_USAGES.
• PG_REGION_PATH — the OA Framework region path that renders the LOV for the object.
• SOURCE_PARAM and DEST_PARAM — the parameter mapping pairs passed from the source page to the destination LOV page.
• APPLICATION_ID — the application context under which the LOV page detail is registered.
• SOURCE_OBJECT_CODE — the originating object code from JTF_OBJECT_MAPPINGS, tying the relationship back to its source object.

Common Use Cases and Queries

This view is commonly queried during CRM Foundation diagnostics to confirm which LOV region and parameters apply to the JTF_OBJECT_RELATION object for a given responsibility and language.

• Verifying LOV parameter mapping between a source object and its relationship LOV.
• Auditing which applications have responsibility-specific OA_LOV page details versus those falling back to JTF_OBJECTS_B.
• Investigating missing or misconfigured LOVs by checking for absent PG_REGION_PATH rows.

A representative query:

SELECT object_name, object_code, object_user_code,
       pg_region_path, source_param, dest_param,
       application_id, source_object_code
FROM   apps.jtf_object_lov_dtls_v
WHERE  object_code = 'JTF_OBJECT_RELATION';

Because results are filtered by USERENV('LANG') and FND_GLOBAL.RESP_APPL_ID, queries should always be executed under the target responsibility and language session to obtain accurate metadata.