Search Results per_images




Overview
Explore in AI Chat

Overview

The PER_IMAGES table, owned by the HR schema, is a component of the Oracle E-Business Suite Human Resources (PER) product family. Its documented purpose is to store images associated with a designated row in a designated table, providing a generic, reusable image-attachment mechanism rather than a purpose-built entity for a single business object. This generic design allows any PER-module entity that requires an image — such as an employee photograph or a graphical element tied to a person or assignment record — to persist the binary content through a single consolidated table.

The table is documented as VALID and carries a physical schema of four columns in ETRM 12.2.2, consistent with its presence in 12.1.1 and 12.2.2 environments. The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning no outgoing foreign-key dependencies were detected in the metadata. In modeling terms, this suggests treating PER_IMAGES as a satellite-like construct whose parent relationship is implied by the loose polymorphic key (TABLE_NAME plus PARENT_ID) rather than enforced by a database constraint.

Key Information Stored

The documented physical schema consists of four columns: IMAGE_ID, PARENT_ID, TABLE_NAME, and IMAGE. The essential attributes are:

  • IMAGE_ID — The surrogate primary key, enforcing the PER_IMAGES_PK unique index. It uniquely identifies each stored image record and is the column downstream objects would use to reference a specific image.
  • PARENT_ID — The identifier of the parent row to which the image belongs. Together with TABLE_NAME it forms the business-key candidate PER_IMAGES_UK2, ensuring a given parent row carries a uniquely identifiable image record.
  • TABLE_NAME — The name of the target table that holds the parent row identified by PARENT_ID. This column makes the relationship polymorphic: PER_IMAGES can serve multiple source tables without dedicated foreign keys.
  • IMAGE — The stored image payload. It is the data-bearing column of the table, and the metadata shows an associated LOB segment (SYS_IL0000043902C00004$$), indicating IMAGE is implemented as a large object (LOB) to accommodate binary image content.

The distinction between the surrogate key and the business key is important: PER_IMAGES_PK guarantees row uniqueness at the technical level, while PER_IMAGES_UK2 captures the natural identity of an image as "the image for this row in this table." Because no foreign keys are declared, referential integrity to the parent row is maintained by application logic rather than the database.

Common Use Cases and Queries

The principal use case is retrieving the image associated with a given parent record. A typical query pattern joins on the polymorphic key:

  • Retrieve an image: SELECT IMAGE FROM PER_IMAGES WHERE TABLE_NAME = :p_table AND PARENT_ID = :p_parent_id;
  • Confirm existence without fetching the LOB: SELECT IMAGE_ID FROM PER_IMAGES WHERE TABLE_NAME = :p_table AND PARENT_ID = :p_parent_id;
  • Aggregate image coverage by source table: SELECT TABLE_NAME, COUNT(*) FROM PER_IMAGES GROUP BY TABLE_NAME;

Reporting scenarios include auditing which parent entities have associated images, identifying orphaned image rows where the parent no longer exists, and measuring storage consumption by source table. Because the IMAGE column is a LOB, queries used for reporting should avoid selecting it unless the binary content is genuinely required, as full-table LOB retrieval is expensive.

Related Objects

PER_IMAGES references its parent entities logically rather than through declared foreign keys. The significant related objects are therefore:

  • PER_ALL_PEOPLE_F — The primary employee/person entity, a common value for TABLE_NAME with PARENT_ID matching PERSON_ID or a related surrogate.
  • PER_ALL_ASSIGNMENTS_F — Assignment records that may be designated parents for stored images.
  • HR.PER_IMAGES_PK and PER_IMAGES_UK2 — The unique indexes that enforce row and business-key uniqueness and are consulted by every lookup.
  • SYS_IL0000043902C00004$$ — The LOB index associated with the IMAGE column, required for efficient LOB access.
  • Any PER-module entity whose TABLE_NAME appears as a distinct value in PER_IMAGES, since the polymorphic design permits multiple source tables to share this image store.