Search Results jtf_perz_obj_map_u2

Overview

JTF.JTF_PERZ_OBJ_MAP is a transactional mapping table in the Oracle E-Business Suite JTF (Applications Technology) schema that stores the relationship between a look-and-feel object instance and the concrete attribute values assigned to it. In practice, it acts as the bridge between the personalized UI object definitions held in JTF_PERZ_OBJ_TYPE_MAP and JTF_PERZ_LF_OBJECT and the individual values resolved for those objects, which are persisted in JTF_PERZ_LF_VALUE. The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10 and is classified with a VALID status in ETRM for both 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the heuristic classification is satellite-leaning. The single-column primary key OBJ_MAP_ID, the descriptive who-columns, and the tight dependency on parent mapping tables suggest this object behaves as a satellite hanging off the object-type and object hubs, rather than as an independent hub or a many-to-many link.

Key Information Stored

The table contains nine documented columns. The most significant are:

• OBJ_MAP_ID — Surrogate primary key (JTF_PERZ_OBJ_MAP_PK) and the unique identifier of the look-and-feel object map row.
• MAP_ID — Foreign key to JTF_PERZ_OBJ_TYPE_MAP, identifying the object type map that governs the attribute set.
• OBJECT_ID — Foreign key to JTF_PERZ_LF_OBJECT, identifying the specific look-and-feel object instance being mapped.
• CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns referencing FND_USER and FND_LOGINS.
• LAST_UPDATE_DATE — Timestamp of the most recent modification.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, used in hosted and multi-tenant deployments.
• ZD_EDITION_NAME — Editioning column supporting Edition-Based Redefinition in 12.2.x.

Two unique indexes are documented as business-key candidates. JTF_PERZ_OBJ_MAP_U1 covers OBJ_MAP_ID, OBJECT_ID, MAP_ID, and ZD_EDITION_NAME; JTF_PERZ_OBJ_MAP_U2 (the index referenced in the search term "jtf_perz_obj_map_u2") covers OBJ_MAP_ID and ZD_EDITION_NAME. U2 therefore guarantees uniqueness of the surrogate key within an edition.

Common Use Cases and Queries

Typical usage centers on personalization and look-and-feel diagnostics: resolving which attribute values apply to a given object instance, auditing who customized a page, and joining map rows to their resolved values.

To retrieve the mapping for a specific object:

• SELECT m.OBJ_MAP_ID, m.MAP_ID, m.OBJECT_ID FROM JTF.JTF_PERZ_OBJ_MAP m WHERE m.OBJECT_ID = :object_id;
• SELECT v.* FROM JTF.JTF_PERZ_LF_VALUE v WHERE v.OBJ_MAP_ID = :obj_map_id;

For reporting, joining to JTF_PERZ_OBJ_TYPE_MAP and JTF_PERZ_LF_OBJECT produces a complete view of object-type, object, and assigned values. Auditing queries filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace personalization changes over time.

Related Objects

• JTF.JTF_PERZ_OBJ_TYPE_MAP — joined on MAP_ID; defines the attribute set for the mapped object.
• JTF.JTF_PERZ_LF_OBJECT — joined on OBJECT_ID; the look-and-feel object instance.
• JTF.JTF_PERZ_LF_VALUE — references OBJ_MAP_ID; holds the resolved attribute values for each map row.
• FND.FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for hosted environments.
• FND.FND_USER — joined on CREATED_BY and LAST_UPDATED_BY for WHO-column resolution.
• FND.FND_LOGINS — joined on LAST_UPDATE_LOGIN for session tracing.
• APPS.JTF_PERZ_OBJ_MAP — the APPS synonym used by application code and concurrent programs.