Search Results obj_type_map_id




Overview
Explore in AI Chat

Overview

JTF.JTF_PERZ_OBJ_TYPE_MAP is a mapping table within the Oracle E-Business Suite 12c (12.1.1 and 12.2.2) JTF schema that stores the relationship between look-and-feel object types and their associated object attributes. It forms part of the personalization framework, enabling the application to associate specific attributes with defined object types so that user interface personalization rules can be resolved against the correct object metadata at runtime. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes are created in APPS_TS_TX_IDX.

From a data modeling perspective, the heuristic Data Vault classification for this object is satellite-leaning. This classification arises because the table carries descriptive attributes (the mapping between object types and attributes) and depends on foreign key relationships to parent hub-like entities such as JTF_PERZ_LF_OBJECT_TYPE and JTF_PERZ_LF_ATTRIB, rather than acting as an independent hub or a pure link resolving many-to-many relationships across distinct hubs. The documented ETRM metadata confirms the object status as VALID and designates FND Design Data as JTF.JTF_PERZ_OBJ_TYPE_MAP.

Key Information Stored

The table contains nine documented columns. The most significant are described below.

Two unique indexes are documented. JTF_PERZ_OBJ_TYPE_MAP_U1 (OBJ_TYPE_MAP_ID, ZD_EDITION_NAME) enforces uniqueness on the surrogate key within an edition. JTF_PERZ_OBJ_TYPE_MAP_U2 (OBJ_TYPE_MAP_ID, OBJECT_TYPE_ID, ATTRIBUTE_ID, ZD_EDITION_NAME) provides a broader business-key candidate that guarantees a single mapping row per object type, attribute, and edition.

Common Use Cases and Queries

This table is typically queried when resolving which attributes belong to a given look-and-feel object type, or when auditing personalization mappings. A common pattern joins the mapping to its parent attribute and object type tables:

  • Retrieve all attributes mapped to a specific object type by filtering on OBJECT_TYPE_ID and joining to JTF_PERZ_LF_ATTRIB.
  • Validate mapping completeness by comparing the count of rows per OBJECT_TYPE_ID against expected attribute sets.
  • Audit recently modified mappings using LAST_UPDATE_DATE and LAST_UPDATED_BY.
  • In hosted or multi-tenant deployments, filter by SECURITY_GROUP_ID to isolate a tenant's mappings.
  • For EBR-aware queries, include ZD_EDITION_NAME in the WHERE clause to target a specific edition.

A representative query is:

SELECT m.OBJ_TYPE_MAP_ID, m.OBJECT_TYPE_ID, m.ATTRIBUTE_ID, m.LAST_UPDATE_DATE FROM JTF.JTF_PERZ_OBJ_TYPE_MAP m WHERE m.OBJECT_TYPE_ID = :object_type_id AND m.ZD_EDITION_NAME = :edition_name;

Related Objects

The following objects are most significant to JTF_PERZ_OBJ_TYPE_MAP based on the documented FK relationships and dependencies.

  • JTF_PERZ_LF_OBJECT_TYPE — Referenced via OBJECT_TYPE_ID; provides object type metadata.
  • JTF_PERZ_LF_ATTRIB — Referenced via ATTRIBUTE_ID; provides attribute metadata.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for hosted environments.
  • JTF_PERZ_OBJ_MAP — References this table through MAP_ID, extending the mapping chain.
  • JTF_PERZ_OBJ_TYPE_MAP# — The editioning or shadow variant associated with this table.
  • FND_USER — Referenced by CREATED_BY and LAST_UPDATED_BY.
  • FND_LOGINS — Referenced by LAST_UPDATE_LOGIN.