Search Results jtf_perz_lf_object




Overview

JTF_PERZ_LF_OBJECT is a table owned by the JTF schema (CRM Foundation) within Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores instances of "look and feel" (LF) objects that are generated at runtime from the metadata definitions held in JTF_PERZ_LF_OBJECT_TYPE and JTF_PERZ_LF_ATTRIB. In practical terms, the personalization framework allows administrators to define LF object types and their attributes declaratively, and JTF_PERZ_LF_OBJECT records each concrete instance created from that metadata, together with its parent-child hierarchy and application context.

Under a heuristic Data Vault classification mined from the foreign-key structure, this table exhibits hub-leaning characteristics: it carries a surrogate primary key and a small number of outbound references, with dependent mapping tables pointing back to it. This is offered as a modeling suggestion rather than a normative classification. The table is the anchor point of the personalization LF object graph, and downstream mapping structures — most notably JTF_PERZ_OBJ_MAP — reference its OBJECT_ID to associate instances with other framework entities.

Key Information Stored

The physical schema documents 13 columns for the JTF owner in 12.2.2. The most significant are:

  • OBJECT_ID — the surrogate primary key, enforced by JTF_PERZ_LF_OBJECT_PK. It is the definitive identifier for an LF object instance and is the column referenced by dependent tables.
  • PARENT_ID — self-referencing parent pointer that models the LF object hierarchy, enabling nested object compositions.
  • APPLICATION_ID — identifies the owning application, scoping which EBS product created or uses the LF object.
  • OBJECT_NAME — the business-facing name of the look and feel instance; jointly forms part of the unique business keys.
  • OBJECT_DESCRIPTION — free-text description of the instance's purpose.
  • OBJECT_VERSION_NUMBER — optimistic locking / versioning column used to detect concurrent updates.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing row-level security and data partitioning by operating unit or group.
  • ZD_EDITION_NAME — the editioning column introduced in the 12.2 online patching architecture; it partitions rows by edition and appears in both unique indexes.
  • Audit columns CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS who-columns tracking row provenance.

Two unique indexes act as business-key candidates: JTF_PERZ_LF_OBJECT_U1 on (OBJECT_ID, OBJECT_NAME, APPLICATION_ID, ZD_EDITION_NAME) and JTF_PERZ_LF_OBJECT_U2 on (OBJECT_ID, ZD_EDITION_NAME). Note that the schema also lists a column literally named JTF_PERZ_LF_OBJECT_OBJECT_ID, an artifact of the generation tooling; OBJECT_ID remains the operative key.

Common Use Cases and Queries

Typical scenarios include auditing the personalized look and feel definitions instantiated for a given application, tracing parent-child composition of LF objects, and joining to the mapping table to resolve relationships with other personalization entities.

  • List LF objects for a specific application:
    SELECT OBJECT_ID, OBJECT_NAME, PARENT_ID, OBJECT_DESCRIPTION FROM JTF.JTF_PERZ_LF_OBJECT WHERE APPLICATION_ID = :app_id AND ZD_EDITION_NAME = 'ORA$BASE';
  • Rebuild the object hierarchy:
    SELECT child.OBJECT_ID, child.OBJECT_NAME, parent.OBJECT_NAME AS PARENT_NAME FROM JTF_PERZ_LF_OBJECT child LEFT JOIN JTF_PERZ_LF_OBJECT parent ON child.PARENT_ID = parent.OBJECT_ID;
  • Find dependent mappings:
    SELECT m.OBJECT_ID, o.OBJECT_NAME FROM JTF.JTF_PERZ_OBJ_MAP m JOIN JTF.JTF_PERZ_LF_OBJECT o ON m.OBJECT_ID = o.OBJECT_ID;
  • Security-scoped reporting joining FND_SECURITY_GROUPS on SECURITY_GROUP_ID to resolve security group names for a report of personalization objects.

Reports frequently filter by ZD_EDITION_NAME to isolate the active edition, and by APPLICATION_ID to restrict to the relevant product module.

Related Objects

  • JTF_PERZ_LF_OBJECT_TYPE — holds the metadata type definitions from which LF object instances are created.
  • JTF_PERZ_LF_ATTRIB — defines the attributes available to LF object types.
  • JTF_PERZ_OBJ_MAP — references JTF_PERZ_LF_OBJECT.OBJECT_ID via its OBJECT_ID column, mapping LF objects to other framework entities.
  • FND_SECURITY_GROUPS — referenced by JTF_PERZ_LF_OBJECT.SECURITY_GROUP_ID, supplying security group context.
  • JTF.JTF_PERZ_LF_OBJECT itself — self-referenced through PARENT_ID for hierarchical composition.

These relationships make JTF_PERZ_LF_OBJECT a central anchor in the CRM Foundation personalization model, connecting metadata definitions, dependent mappings, and security scoping.