Search Results jtf_object_mappings_v




Overview
Explore in AI Chat

Overview

The JTF_OBJECT_MAPPINGS_V view is a CRM Foundation (JTF) reporting and integration object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to map a source object name to an object identifier, and to expose the list of object identifiers available for selection by a user, typically as a dropdown (LOV) source. The view is registered as STATUS: VALID in the ETRM metadata and is defined without an associated package or entity handler, making it a read-only query structure over the underlying mapping table plus supplementary lookup joins.

In practice, the view consolidates mapping rows from JTF_OBJECT_MAPPINGS and enriches each row with human-readable descriptive data: the application name from FND_APPLICATION_VL, the source object's translated name from JTF_OBJECTS_VL, and a dynamically resolved object instance name obtained through the JTF_OBJECTS_PVT package. This combination makes the view suitable both for ad hoc reporting and for UI lookups where a user must resolve a technical object code and identifier pair into a recognizable business name.

Underlying Base Objects

The view text defines three joined sources, with the ETRM documentation recording four referenced base objects in total due to the additional procedural call:

  • JTF_OBJECT_MAPPINGS (synonym, aliased NTS) — the primary mapping table that stores MAPPING_ID, SOURCE_OBJECT_CODE, OBJECT_CODE, OBJECT_ID, APPLICATION_ID, END_DATE, SEEDED_FLAG, the WHO audit columns, and the fifteen generic ATTRIBUTE columns. The view exposes its ROWID as ROW_ID.
  • JTF_OBJECTS_VL (view, aliased OBJ) — joined on OBJ.OBJECT_CODE = NTS.SOURCE_OBJECT_CODE to supply the translated SOURCE_OBJECT_NAME. Its NAME column is aliased in the view text as OBJECT_NAME.
  • FND_APPLICATION_VL (view, aliased FAL) — an outer join (APPLICATION_ID = FAL.APPLICATION_ID(+)) that resolves APPLICATION_NAME. Because it is an outer join, mapping rows whose APPLICATION_ID has no matching application still return, with a null application name.
  • JTF_OBJECTS_PVT (package) — invoked as JTF_OBJECTS_PVT.GET_OBJECT_INSTANCE_NAME(NTS.OBJECT_CODE, NTS.OBJECT_ID) to compute OBJECT_INSTANCE_NAME at query time rather than storing it.

Key Columns

  • ROW_ID — the ROWID of the underlying JTF_OBJECT_MAPPINGS row; useful for identifying the exact physical record.
  • MAPPING_ID — the primary key of the mapping definition.
  • APPLICATION_ID / APPLICATION_NAME — the owning application of the mapping and its translated name.
  • SOURCE_OBJECT_CODE / SOURCE_OBJECT_NAME — the source entity code and its descriptive name from JTF_OBJECTS_VL.
  • OBJECT_CODE / OBJECT_ID — the mapped target object type and its identifier; OBJECT_ID is the value typically offered in a selection list.
  • OBJECT_INSTANCE_NAME — the resolved instance label returned by JTF_OBJECTS_PVT; the most user-facing column in the view.
  • END_DATE — effective end of the mapping; a null value generally denotes an active row.
  • SEEDED_FLAG — indicates whether the mapping was delivered as seed data or created by a user.
  • OBJECT_VERSION_NUMBER — optimistic locking version for the underlying row.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns carried through from the base table.

Common Use Cases and Queries

The view is most frequently used to populate LOVs and to report on which business objects are mapped to which application. A typical query resolving all mappings for a given source object is:

  • SELECT mapping_id, application_name, source_object_code, source_object_name, object_code, object_id, object_instance_name FROM jtf_object_mappings_v WHERE source_object_code = :p_source_code AND end_date IS NULL ORDER BY object_instance_name;
  • To filter seed versus customer-defined entries: ... WHERE seeded_flag = 'N'.
  • To list mappings by application: SELECT application_name, object_code, COUNT(*) FROM jtf_object_mappings_v GROUP BY application_name, object_code;
  • For integration lookups, retrieve the OBJECT_ID for a known code: SELECT object_id FROM jtf_object_mappings_v WHERE object_code = :p_object_code AND source_object_code = :p_source_code;

Because OBJECT_INSTANCE_NAME is computed by the JTF_OBJECTS_PVT package, queries returning large row sets may incur additional PL/SQL overhead; restricting by SOURCE_OBJECT_CODE or APPLICATION_ID is recommended for performance.