Search Results jtf_perz_obj_type_map_pk

Overview

JTF_PERZ_OBJ_TYPE_MAP is a CRM Foundation (JTF) table in the Oracle EBS 12.1.1 and 12.2.2 file systems. It stores the mapping between an object type and the object attributes that belong to that type. In practical terms, the table defines which personalization attributes are legal or available for a given personalization object type, forming the associative layer between the object type registry and the attribute registry.

The table is owned by the JTF schema and holds a VALID status in the ETRM registry. Its documented structure contains nine columns and two unique indexes. The primary key is JTF_PERZ_OBJ_TYPE_MAP_PK, defined on OBJ_TYPE_MAP_ID. A second unique index, JTF_PERZ_OBJ_TYPE_MAP_U2, is defined on the combination OBJ_TYPE_MAP_ID, OBJECT_TYPE_ID, ATTRIBUTE_ID, and ZD_EDITION_NAME. A parallel unique index, JTF_PERZ_OBJ_TYPE_MAP_U1, includes OBJ_TYPE_MAP_ID and ZD_EDITION_NAME.

Applying Data Vault modeling heuristics to the documented foreign-key structure, this object is classified as satellite-leaning. The classification is a modeling suggestion rather than a documented Oracle designation. The table's function is associative: it links an object type to specific attributes, and the surrounding design supports a hub-link-satellite pattern where the object type and attribute registries act as reference hubs.

Key Information Stored

The most important columns in JTF_PERZ_OBJ_TYPE_MAP are:

• OBJ_TYPE_MAP_ID — The surrogate primary key. Every row is uniquely identified by this identifier, and it is the anchor of the JTF_PERZ_OBJ_TYPE_MAP_PK constraint. It also participates in both documented unique indexes.
• OBJECT_TYPE_ID — The foreign key to JTF_PERZ_LF_OBJECT_TYPE. It identifies the personalization object type to which the attribute mapping applies. Together with ATTRIBUTE_ID it forms the core business-key candidate in JTF_PERZ_OBJ_TYPE_MAP_U2.
• ATTRIBUTE_ID — The foreign key to JTF_PERZ_LF_ATTRIB. It identifies the specific personalization attribute being associated with the object type. The OBJECT_TYPE_ID and ATTRIBUTE_ID pairing is the meaningful business identifier for a mapping row.
• CREATED_BY — Standard EBS who-column recording the application user who inserted the row.
• LAST_UPDATE_DATE — Standard EBS who-column recording the most recent modification timestamp.
• LAST_UPDATED_BY — Standard EBS who-column recording the application user responsible for the most recent modification.
• LAST_UPDATE_LOGIN — Standard EBS who-column recording the login context of the last update.
• SECURITY_GROUP_ID — The foreign key to FND_SECURITY_GROUPS, supporting multi-organization or security-group scoping of personalization metadata.
• ZD_EDITION_NAME — The editioning column used in the EBS 12.2 online patching architecture and included in both unique indexes.

The surrogate OBJ_TYPE_MAP_ID should be distinguished from the business-key candidate formed by OBJECT_TYPE_ID, ATTRIBUTE_ID, and ZD_EDITION_NAME, which enforces uniqueness of each type-attribute pairing per edition.

Common Use Cases and Queries

Typical uses center on personalization metadata resolution: determining which attributes are available for a personalization object type, driving attribute-driven UI configuration, and validating that a requested object-attribute combination is registered.

A representative query joining the table to its reference objects resolves mapping rows to descriptive names:

• SELECT m.obj_type_map_id, t.object_type, a.attribute_name FROM jtf.jtf_perz_obj_type_map m, jtf.jtf_perz_lf_object_type t, jtf.jtf_perz_lf_attrib a WHERE m.object_type_id = t.object_type_id AND m.attribute_id = a.attribute_id;
• Filter by a specific type using WHERE m.object_type_id = :object_type_id to enumerate the attributes defined for that type.
• Join to JTF_PERZ_OBJ_MAP via MAP_ID to establish the broader object mapping context in which a type-attribute mapping participates.
• Count attributes per object type for registration completeness or configuration auditing reports.

Because SECURITY_GROUP_ID participates in row ownership, reporting queries should apply the appropriate security-group predicate to avoid exposing metadata outside the caller's security scope.

Related Objects

The following objects are most significant to JTF_PERZ_OBJ_TYPE_MAP based on documented relationships:

• JTF_PERZ_LF_OBJECT_TYPE — Referenced through JTF_PERZ_OBJ_TYPE_MAP.OBJECT_TYPE_ID; supplies the object type definition. This is the primary lookup parent on the type side.
• JTF_PERZ_LF_ATTRIB — Referenced through JTF_PERZ_OBJ_TYPE_MAP.ATTRIBUTE_ID; supplies the attribute definition. This is the primary lookup parent on the attribute side.
• JTF_PERZ_OBJ_MAP — A child table referencing JTF_PERZ_OBJ_TYPE_MAP through JTF_PERZ_OBJ_MAP.MAP_ID. It stores object mapping rows that depend on the type-attribute mapping.
• FND_SECURITY_GROUPS — Referenced through JTF_PERZ_OBJ_TYPE_MAP.SECURITY_GROUP_ID; governs security-group scoping of the mapping rows.
• JTF_PERZ_OBJ_TYPE_MAP_PK — The primary key constraint on OBJ_TYPE_MAP_ID.
• JTF_PERZ_OBJ_TYPE_MAP_U1 and JTF_PERZ_OBJ_TYPE_MAP_U2 — The unique indexes that enforce surrogate and business-key uniqueness, including the ZD_EDITION_NAME editioning column.

Together these objects position JTF_PERZ_OBJ_TYPE_MAP as the associative metadata layer that binds CRM Foundation personalization object types to their attributes.