Search Results jtf_perz_obj_type_map




Overview
Explore in AI Chat

Overview

The JTF_PERZ_OBJ_TYPE_MAP table is a core data structure within the Oracle E-Business Suite's CRM Technology Foundation (JTF). Its primary function is to define and store the permissible mappings between object types and their associated attributes within the personalization framework. This table acts as a central metadata repository, establishing which attributes are valid for a given object type. This mapping is essential for enabling flexible and rule-based personalization, content targeting, and conditional logic across CRM applications in both EBS 12.1.1 and 12.2.2. It serves as a critical link between the definition of an object (what it is) and the specific characteristics (attributes) that can be used to describe, filter, or act upon instances of that object.

Key Information Stored

The table's structure centers on creating unique associations between object types and attributes. The primary key, OBJ_TYPE_MAP_ID, uniquely identifies each valid mapping record. The two critical foreign key columns are OBJECT_TYPE_ID and ATTRIBUTE_ID. OBJECT_TYPE_ID references the JTF_PERZ_LF_OBJECT_TYPE table, linking to a defined object within the system (e.g., a Service Request, Opportunity, or Marketing Campaign). ATTRIBUTE_ID references the JTF_PERZ_LF_ATTRIB table, linking to a specific attribute that can be applied to that object type (e.g., "Status," "Priority," "Amount"). Together, these columns enforce data integrity by ensuring that only pre-defined and sanctioned attribute-to-object relationships are established for use in personalization rules and object mapping.

Common Use Cases and Queries

This table is primarily accessed during the configuration and execution of personalization logic. A common administrative use case is to query all available attributes for a specific object type when building a new business rule. For example, to retrieve all mappable attributes for a given object type name, a query would join through the related reference tables:

SELECT oat.attribute_name, oat.description
FROM jtf_perz_obj_type_map otm,
     jtf_perz_lf_object_type oty,
     jtf_perz_lf_attrib oat
WHERE otm.object_type_id = oty.object_type_id
  AND otm.attribute_id = oat.attribute_id
  AND oty.object_type = 'SERVICE_REQUEST';

Conversely, developers might query this table to validate if a specific attribute ID is allowed for an object type before attempting to create a personalized rule or object map entry in the JTF_PERZ_OBJ_MAP table, which depends on this mapping.

Related Objects

  • JTF_PERZ_LF_OBJECT_TYPE: This table is referenced via the foreign key JTF_PERZ_OBJ_TYPE_MAP.OBJECT_TYPE_ID. It provides the master list of object types available for personalization.
  • JTF_PERZ_LF_ATTRIB: This table is referenced via the foreign key JTF_PERZ_OBJ_TYPE_MAP.ATTRIBUTE_ID. It stores the master definition of all available attributes.
  • JTF_PERZ_OBJ_MAP: This table holds the concrete instances of personalized object mappings and references JTF_PERZ_OBJ_TYPE_MAP via the foreign key JTF_PERZ_OBJ_MAP.MAP_ID. It relies on the valid combinations defined in JTF_PERZ_OBJ_TYPE_MAP.