Search Results jtf_perz_obj_map




Overview
Explore in AI Chat

Overview

JTF_PERZ_OBJ_MAP is a table owned by the JTF schema within the CRM Foundation product of Oracle E-Business Suite. It stores the mapping between the look and feel (personalization) object instance and the actual values for the attributes associated with that instance. In practical terms, the table serves as the associative bridge that binds a personalized object instance to the type-level metadata that describes it, and it acts as the parent of the attribute value records held in JTF_PERZ_LF_VALUE.

The object carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. Under the 12.2.2 documented physical schema it contains nine columns, and it participates in the Online Patching (ADOP) model through the presence of the ZD_EDITION_NAME column. The ETRM relationship data classifies this table, on a heuristic basis mined from its foreign key structure, as satellite-leaning. This classification is a modeling suggestion only: the table's role as a dependent, descriptive extension of a parent object type and object instance aligns it with satellite semantics rather than with hub or link semantics. Treat the classification as guidance for downstream modeling, not as a shipped EBS constraint.

Key Information Stored

Two unique indexes are documented as business-key candidates. JTF_PERZ_OBJ_MAP_U1 covers (OBJ_MAP_ID, OBJECT_ID, MAP_ID, ZD_EDITION_NAME). JTF_PERZ_OBJ_MAP_U2 covers (OBJ_MAP_ID, ZD_EDITION_NAME). The distinction between the surrogate OBJ_MAP_ID primary key and these composite unique constraints is important when reasoning about row identity versus edition-scoped uniqueness.

Common Use Cases and Queries

The primary use case is resolving the attribute values applied to a personalized CRM object instance. A reporting query joining the mapping to its value child typically resembles the following pattern:

  • Join JTF_PERZ_OBJ_MAP m to JTF_PERZ_LF_VALUE v on v.OBJ_MAP_ID = m.OBJ_MAP_ID to retrieve the actual attribute values associated with a mapping.
  • Join m.OBJECT_ID to JTF_PERZ_LF_OBJECT to resolve the object instance, and m.MAP_ID to JTF_PERZ_OBJ_TYPE_MAP to resolve the type-level definition.
  • Filter by SECURITY_GROUP_ID where data isolation across security groups is required.
  • Filter by ZD_EDITION_NAME, or exclude non-run editions, when querying under a 12.2 patched environment.

Typical scenarios include auditing which personalization values are attached to a given object, diagnosing why a personalized page or region behaves unexpectedly, and extracting configuration mappings for migration or comparison between environments. Because the table is satellite-leaning, reporting queries generally drive from the parent object or type and use this table as the descriptive detail.

Related Objects

  • JTF_PERZ_OBJ_TYPE_MAP — referenced by JTF_PERZ_OBJ_MAP.MAP_ID; holds the object type-level mapping definition.
  • JTF_PERZ_LF_OBJECT — referenced by JTF_PERZ_OBJ_MAP.OBJECT_ID; the look and feel object instance.
  • JTF_PERZ_LF_VALUE — references this table via OBJ_MAP_ID; stores the individual attribute values for each mapping.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for data isolation.
  • JTF_PERZ_OBJ_MAP_PK / JTF_PERZ_OBJ_MAP_U1 / JTF_PERZ_OBJ_MAP_U2 — the primary key and unique index constraints that define row identity and business-key uniqueness.