Search Results object_instance_name

Overview

APPS.JTF_OBJECT_MAPPINGS_V is a reporting and integration view in the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 environment. It presents a denormalized, human-readable representation of the records stored in the JTF_OBJECT_MAPPINGS base entity, which is part of the CRM Foundation (JTF) schema. Object mappings associate a source object within a given application to a target object, effectively describing how one entity in the EBS data model relates to another across applications. The view enriches the raw mapping identifiers with translated application names and object names, and it computes a derived display value, OBJECT_INSTANCE_NAME, by invoking a package function at query time. This makes the view suitable for reports, integration lookups, and diagnostic queries where raw numeric identifiers would otherwise require additional joins or PL/SQL calls. The view is owned by the APPS schema and is therefore typically accessed directly or granted to custom schemas for read-only use.

Underlying Base Objects

The view is defined over the following documented base objects:

• JTF_OBJECT_MAPPINGS (SYNONYM) — the driving table NTS, supplying the mapping records, identifiers, audit columns, attributes, and the SOURCE_OBJECT_CODE and OBJECT_CODE/OBJECT_ID pairs.
• JTF_OBJECTS_VL (VIEW) — joined as OBJ on OBJ.OBJECT_CODE = NTS.SOURCE_OBJECT_CODE to obtain the translated NAME for the source object.
• FND_APPLICATION_VL (VIEW) — outer-joined as FAL on NTS.APPLICATION_ID = FAL.APPLICATION_ID(+) to obtain the APPLICATION_NAME; the outer join allows mappings without a resolvable application to remain visible.
• JTF_OBJECTS_PVT (PACKAGE) — a PL/SQL package whose GET_OBJECT_INSTANCE_NAME function is called in the SELECT list to derive OBJECT_INSTANCE_NAME from OBJECT_CODE and OBJECT_ID.

The only inner joins are between the mapping table and JTF_OBJECTS_VL; all other sources are either outer-joined or invoked as functions, so the view generally preserves one row per mapping record.

Key Columns

• ROW_ID — the ROWID of the underlying JTF_OBJECT_MAPPINGS row, useful as a unique handle.
• MAPPING_ID — the primary identifier of the mapping record.
• APPLICATION_ID and APPLICATION_NAME — the owning application and its translated name.
• SOURCE_OBJECT_CODE and OBJECT_NAME — the source object code and its translated name from JTF_OBJECTS_VL.
• OBJECT_CODE and OBJECT_ID — the target object type and its instance identifier.
• OBJECT_INSTANCE_NAME — a derived display name produced by JTF_OBJECTS_PVT.GET_OBJECT_INSTANCE_NAME; this matches the user search term "object_instance_name" and is the most frequently queried derived column.
• END_DATE and SEEDED_FLAG — effective-dating and Oracle-seeded indicators used to filter active or customer-defined mappings.
• OBJECT_VERSION_NUMBER — optimistic locking column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield support columns.

Common Use Cases and Queries

The view is commonly used to report which objects are mapped to which applications, to resolve an object instance to a readable name, and to troubleshoot integration flows that depend on object mappings. Because OBJECT_INSTANCE_NAME is computed per row, queries filtering on it should expect function invocation cost.

SELECT MAPPING_ID,
       APPLICATION_NAME,
       SOURCE_OBJECT_CODE,
       OBJECT_NAME,
       OBJECT_CODE,
       OBJECT_INSTANCE_NAME
FROM   APPS.JTF_OBJECT_MAPPINGS_V
WHERE  OBJECT_INSTANCE_NAME IS NOT NULL
AND    (END_DATE IS NULL OR END_DATE > SYSDATE)
ORDER BY APPLICATION_NAME, OBJECT_NAME;

A typical diagnostic query searches for a specific instance by name and returns the application and source object context:

SELECT APPLICATION_NAME, SOURCE_OBJECT_CODE, OBJECT_CODE, OBJECT_ID
FROM   APPS.JTF_OBJECT_MAPPINGS_V
WHERE  UPPER(OBJECT_INSTANCE_NAME) LIKE UPPER(:p_name);

Reports requiring only seeded versus customer-defined mappings can filter on SEEDED_FLAG. The view is read-only in practice; changes to mappings must be made through the base JTF_OBJECT_MAPPINGS table or supported APIs.