Search Results jtf_perz_lf_object_type_u1

Overview

JTF.JTF_PERZ_LF_OBJECT_TYPE is a foundational metadata table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the JTF schema. It stores the metadata that defines a "look and feel" object type within the Personalization (PERZ) framework. Effectively, each row describes a category of business object — such as a region, an item, a field, or a similar UI construct — for which personalization rules, look-and-feel definitions, and attribute mappings can be authored and applied. The table therefore acts as the reference registry that enables the broader personalization engine to associate runtime UI components with their governing metadata.

From a Data Vault modeling perspective, the heuristic classification of this object is hub-leaning. Its relatively small column set, single surrogate primary key (OBJECT_TYPE_ID), and the fact that it is referenced by several downstream tables suggest it functions as a hub of object type identities, with dependent tables supplying descriptive and associative detail.

Key Information Stored

The table is documented with 10 columns in ETRM 12.2.2. The most significant include:

• OBJECT_TYPE_ID — The surrogate primary key (JTF_PERZ_LF_OBJECT_TYPE_PK) and look-and-feel object type identifier.
• OBJECT_TYPE_NAME — A VARCHAR2(60) business-key candidate holding the human-readable type name; it participates in unique index JTF_PERZ_LF_OBJECT_TYPE_U1.
• OBJECT_TYPE_DESC — A VARCHAR2(240) description of the object type.
• OBJECT_VERSION_NUMBER — Optimistic-locking version counter.
• CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard "WHO" audit columns keyed to FND_USER.USER_ID and FND_LOGINS.LOGIN_ID.
• LAST_UPDATE_DATE — Timestamp of the most recent update.
• SECURITY_GROUP_ID — Used in hosted environments; foreign key to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — Editioning column present in 12.2.x, shown in the documented unique indexes U1 and U2.

Two unique indexes serve as business-key candidates: 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). Both reside in the APPS_TS_TX_IDX tablespace, while table data is stored in APPS_TS_TX_DATA.

Common Use Cases and Queries

Typical usage involves identifying and reporting the set of personalizable object types available in the instance, correlating them to mappings, and validating referential integrity across the personalization stack. A canonical query is:

• SELECT OBJECT_TYPE_ID, OBJECT_TYPE_NAME, OBJECT_TYPE_DESC FROM JTF.JTF_PERZ_LF_OBJECT_TYPE WHERE OBJECT_TYPE_NAME = :name;
• Joining to JTF_PERZ_OBJ_TYPE_MAP to enumerate the attribute or property mappings associated with a given object type via OBJECT_TYPE_ID.
• Reporting on audit metadata by joining CREATED_BY or LAST_UPDATED_BY to FND_USER for change-tracking purposes.
• Confirming editioning scope in 12.2.2 by including ZD_EDITION_NAME in filters.

Related Objects

JTF_PERZ_LF_OBJECT_TYPE does not reference any database object beyond its SECURITY_GROUP_ID foreign key, but it is referenced by several significant tables. The most important relationships (all via OBJECT_TYPE_ID) are:

• JTF_PERZ_OBJ_TYPE_MAP — Maps object types to personalization attributes.
• XLE_ASSOCIATION_TYPES and XLE_ASSOC_OBJECT_TYPES — Legal entity association metadata.
• BISM_OBJECT_TYPES and BISM_OBJECTS — Business intelligence / object metadata.
• PA_VALID_CATEGORIES — Project Accounting valid categories.
• FND_SECURITY_GROUPS — Provides the referenced security group context for hosted deployments.