Search Results jtf_object_lov_dtls_v
Overview
JTF_OBJECT_LOV_DTLS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, defined in the FND – Application Object Library product. It exposes the configuration details of Object LOV (List of Values) pages used by the JTF (Java Technology Framework) object relationship and mapping infrastructure. In EBS 12.1.1 and 12.2.2, this view serves as the resolution layer that translates behavioral object relationships, such as parent-child or dependency mappings, into concrete page regions, source parameters, and destination parameters that the OA Framework runtime uses when rendering and executing an LOV region. Administrators and technical consultants searching for "jtf_object_mappings" typically arrive here because JTF_OBJECT_MAPPINGS is one of the core base objects from which this view is constructed. Rather than exposing raw mapping rows, the view joins object usages, page details, parameters, and translations into a single, application- and responsibility-sensitive result set that reflects the object relationships defined as JTF_OBJECT_RELATION.
Underlying Base Objects
The view is defined over the following documented base objects: JTF_OBJECT_USAGES, JTF_OBJECT_PG_DTLS, JTF_OBJECTS_TL, JTF_OBJECT_PG_PARAMS, and JTF_OBJECT_MAPPINGS, joined with JTF_OBJECTS_B and the FND_GLOBAL package (FND_GLOBAL.RESP_APPL_ID). JTF_OBJECT_MAPPINGS links an object to its mapping rows and is filtered with OBJECT_CODE = 'JTF_OBJECT_RELATION', restricting the output to relationship-based LOV configurations. JTF_OBJECT_PG_DTLS supplies the page region path, application, and page type, and is constrained to PAGE_TYPE = 'OA_LOV'. JTF_OBJECT_PG_PARAMS provides the SOURCE_PARAM and DEST_PARAM parameter pairs. JTF_OBJECTS_TL supplies the translated object NAME, restricted to LANGUAGE = USERENV('LANG'). JTF_OBJECT_USAGES supplies OBJECT_USER_CODE. The defined SQL is a UNION of two branches: the first filters page details by JTF_GLOBAL.RESP_APPL_ID, while the second uses JTF_OBJECTS_B and excludes objects already covered for the current responsibility via a NOT EXISTS subquery, providing fallback coverage for objects without a responsibility-specific LOV page row.
Key Columns
- OBJECT_NAME – Translated friendly name from JTF_OBJECTS_TL, shown in the language of the current session.
- OBJECT_CODE – Internal identifier of the object, echoed from JTF_OBJECTS_TL and JTF_OBJECT_USAGES.
- OBJECT_USER_CODE – User-facing object identifier from JTF_OBJECT_USAGES, aligning the LOV with the object as seen by end users.
- PG_REGION_PATH – Region path of the OA_LOV page, indicating where the LOV is rendered.
- SOURCE_PARAM – Source parameter name from JTF_OBJECT_PG_PARAMS, the value passed into the LOV.
- DEST_PARAM – Destination parameter name, the target field receiving the LOV selection.
- APPLICATION_ID – Application context of the LOV page detail, resolved against the responsibility's application.
- SOURCE_OBJECT_CODE – Source object code from JTF_OBJECT_MAPPINGS, identifying the origin side of the relationship mapping.
Common Use Cases and Queries
This view is typically queried to diagnose why an LOV does not appear, returns incorrect values, or fails to populate a destination field. A basic query retrieves all relationship-based LOVs for the running responsibility's language:
SELECT object_name, object_code, object_user_code, pg_region_path, source_param, dest_param
FROM apps.jtf_object_lov_dtls_v
WHERE object_code = :p_object_code;
To trace a specific parameter mapping, filtering by SOURCE_OBJECT_CODE or DEST_PARAM isolates the affected region. Administrators comparing configurations across responsibilities may join the view to FND_APPLICATION on APPLICATION_ID to confirm the responsible application context. Because LANGUAGE is tied to USERENV('LANG') and application filtering is driven by RESP_APPL_ID, the view returns different row sets depending on the session's language and active responsibility, making it unsuitable for static data extracts without explicit session context. It remains the authoritative reference for troubleshooting OA Framework object LOV behavior in Oracle EBS 12.1.1 and 12.2.2.
-
View: JTF_OBJECT_LOV_DTLS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:FND.JTF_OBJECT_LOV_DTLS_V, object_name:JTF_OBJECT_LOV_DTLS_V, status:VALID, product: FND - Application Object Library , implementation_dba_data: APPS.JTF_OBJECT_LOV_DTLS_V ,
-
View: JTF_OBJECT_LOV_DTLS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:FND.JTF_OBJECT_LOV_DTLS_V, object_name:JTF_OBJECT_LOV_DTLS_V, status:VALID, product: FND - Application Object Library , implementation_dba_data: APPS.JTF_OBJECT_LOV_DTLS_V ,