Search Results jtf_perz_lf_object_type




Overview
Explore in AI Chat

Overview

JTF_PERZ_LF_OBJECT_TYPE is a CRM Foundation (JTF) metadata table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the metadata that defines a "look and feel" object type used by the Personalization (PERZ) framework, which governs how CRM applications render configurable regions, fields, and behaviors. Each row declares an object type that can participate in look-and-feel mappings, and rows are consumed by the mapping table JTF_PERZ_OBJ_TYPE_MAP to associate object types with concrete look-and-feel definitions.

The table is registered in the ETRM repository as VALID under the JTF schema and carries ten documented columns. It is protected by a single-column primary key, JTF_PERZ_LF_OBJECT_TYPE_PK, on OBJECT_TYPE_ID, and it is referenced by multiple functional areas beyond CRM Foundation, including lease/asset association types (XLE_ASSOC_OBJECT_TYPES, XLE_ASSOCIATION_TYPES), business intelligence subject model objects (BISM_OBJECT_TYPES, BISM_OBJECTS), and project accounting valid categories (PA_VALID_CATEGORIES). Under a heuristic Data Vault classification, this table is hub-leaning: the primary key is a stable identifier and most attributes are descriptive, with the edition column reflecting EBS 12.2.2 editioning support. This classification should be treated as a modeling suggestion rather than a documented fact.

Key Information Stored

The ten documented columns capture identity, descriptive text, auditing, security, and editioning metadata:

  • OBJECT_TYPE_ID — surrogate primary key and the column used by all foreign keys into this table; the business-meaningful identifier for an object type.
  • OBJECT_TYPE_NAME — human-readable name of the look-and-feel object type; part of both unique business-key candidates.
  • OBJECT_TYPE_DESC — free-text description clarifying the intended use of the object type.
  • OBJECT_VERSION_NUMBER — optimistic locking/versioning counter used by the ORM layer to detect concurrent updates.
  • CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns recording creation and last modification audit information.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, scoping rows to a security group; unused/zero values indicate rows outside the security group model.
  • ZD_EDITION_NAME — editioning column present in 12.2.2, part of both unique indexes; in 12.1.1 this column does not exist.

The business-key candidates are documented as unique indexes JTF_PERZ_LF_OBJECT_TYPE_U1 (OBJECT_TYPE_ID, OBJECT_TYPE_NAME, ZD_EDITION_NAME) and JTF_PERZ_LF_OBJECT_TYPE_U2 (OBJECT_TYPE_ID, ZD_EDITION_NAME). Note that OBJECT_TYPE_ID alone is the primary key, so these indexes primarily enforce edition-scoped uniqueness in 12.2.x.

Common Use Cases and Queries

Typical uses include personalization administration, diagnostics, and reporting on configured object types. A representative lookup by name:

  • SELECT object_type_id, object_type_name, object_type_desc FROM jtf.jtf_perz_lf_object_type WHERE upper(object_type_name) = upper(:p_name);
  • Resolving mappings to concrete look-and-feel definitions: SELECT m.* FROM jtf.jtf_perz_obj_type_map m JOIN jtf.jtf_perz_lf_object_type t ON m.object_type_id = t.object_type_id;
  • Auditing recently changed metadata: SELECT object_type_name, last_updated_by, last_update_date FROM jtf.jtf_perz_lf_object_type WHERE last_update_date >= :p_since ORDER BY last_update_date DESC;
  • Security group scoping: SELECT * FROM jtf.jtf_perz_lf_object_type WHERE security_group_id = :p_group;
  • Cross-module impact analysis, exercising the inbound foreign keys from XLE_ASSOC_OBJECT_TYPES, BISM_OBJECT_TYPES, and PA_VALID_CATEGORIES to determine which consumers reference a given object type before changing or deactivating it.

These queries are read-only in nature; the table should be populated through supported Personalization configuration flows rather than direct DML.

Related Objects

The most significant related objects, based on the documented foreign-key relationships, are:

  • FND_SECURITY_GROUPS — referenced via JTF_PERZ_LF_OBJECT_TYPE.SECURITY_GROUP_ID.
  • JTF_PERZ_OBJ_TYPE_MAP — references this table via OBJECT_TYPE_ID; the primary consumer linking object types to look-and-feel definitions.
  • XLE_ASSOC_OBJECT_TYPES — references OBJECT_TYPE_ID; lease/asset association type definitions.
  • XLE_ASSOCIATION_TYPES — references OBJECT_TYPE_ID.
  • BISM_OBJECT_TYPES — references OBJECT_TYPE_ID; subject-model object type registry.
  • BISM_OBJECTS — references OBJECT_TYPE_ID; subject-model object instances.
  • PA_VALID_CATEGORIES — references OBJECT_TYPE_ID; project accounting valid category configuration.

JOIN paths for all dependents use the OBJECT_TYPE_ID column, making it the single integration key across these modules. Administrators should treat this table as a master reference when governing CRM personalization and related cross-module object type registrations.