Search Results per_special_info_types_v




Overview
Explore in AI Chat

Overview

PER_SPECIAL_INFO_TYPES_V is an APPS-owned database view in the Oracle E-Business Suite Human Resources (PER) product family. Its documented purpose is to support the user interface, and in practice it exposes special information type definitions alongside the descriptive flexfield structure name that qualifies them. Special information types are the configurable categories of personal, assignment, or other HR-related data that Oracle HRMS captures through its Special Information Types setup and the associated "PEA" descriptive flexfield.

The view is defined as a join between PER_SPECIAL_INFO_TYPES and FND_ID_FLEX_STRUCTURES_VL, filtered to the People/Assignment flexfield code 'PEA'. Rather than forcing a caller to resolve the descriptive flexfield title separately, the view resolves the structure name into the NAME column, giving a denormalized, report-friendly result set. It is therefore relevant to both reporting and integration work: it is a stable, query-safe surface for the enabled/disabled state, comments, ownership context, and descriptive flexfield linkage of each special information type, shielded from the raw composition of the underlying transactional table.

Underlying Base Objects

ETRM documents two referenced base objects:

  • PER_SPECIAL_INFO_TYPES (SYNONYM) — the primary source, aliased X. It supplies the special information type identifier, business group, flexfield number, comments, enabled flag, descriptive flexfield attributes, and WHO/audit columns. In the view text this object is addressed as a synonym, meaning the join is resolved against the APPS-level synonym rather than a schema-qualified table.
  • FND_ID_FLEX_STRUCTURES_VL (VIEW) — aliased F. It is the Application Object Library descriptive flexfield structures view and supplies ID_FLEX_STRUCTURE_NAME. The join predicate is X.ID_FLEX_NUM = F.ID_FLEX_NUM with the constant F.ID_FLEX_CODE = 'PEA', restricting output to the People flexfield.

The view also projects X.ROWID as ROW_ID and selects NULL for INFO_EXISTS. No WHERE clause beyond the join and flexfield-code predicate is present, so every row in PER_SPECIAL_INFO_TYPES whose flexfield number matches the PEA structure is returned.

Key Columns

  • SPECIAL_INFORMATION_TYPE_ID — primary identifier of the special information type; the join key to dependent setup and eligibility tables.
  • BUSINESS_GROUP_ID — the HR business group owning the definition; essential for multi-organization security and filtering.
  • ID_FLEX_NUM — the descriptive flexfield structure number linking the type to its PEA structure.
  • NAME — the descriptive flexfield structure name resolved from FND_ID_FLEX_STRUCTURES_VL, providing a human-readable label.
  • ENABLED_FLAG — indicates whether the type is active and selectable in the user interface.
  • COMMENTS — free-text description of the type.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield segment values applied to the definition.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit context.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — WHO audit columns.
  • ROW_ID — row identifier derived from the base table ROWID; INFO_EXISTS is returned as NULL.

Common Use Cases and Queries

Typical uses include validation listings of enabled special information types per business group, reconciliation of descriptive flexfield setup against PEA structures, and data extracts feeding downstream HR reporting.

List enabled types for a business group:

  • SELECT special_information_type_id, name, comments FROM per_special_info_types_v WHERE business_group_id = :p_bg_id AND enabled_flag = 'Y' ORDER BY name;

Confirm the flexfield structure behind a type:

  • SELECT special_information_type_id, id_flex_num, name FROM per_special_info_types_v WHERE special_information_type_id = :p_type_id;

Because the view contains no aggregation and passes through the base table, it supports joining directly to other PER setup objects on SPECIAL_INFORMATION_TYPE_ID without additional filtering, making it a convenient and reliable building block in custom reports and interfaces.