Results for “school_name”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The PER_JP_SCHOOL_LOOKUPS table is a Human Resources (PER) reference data object that stores lookup values for Japanese educational institutions. It resides in the HR schema and carries a VALID status in Oracle E-Business Suite 12.1.1 and 12.2.2. Functionally, it supplies the controlled vocabulary of schools, universities, and equivalent academic establishments used throughout Japanese HR localization processes, particularly where an employee's educational background must be captured or where disbursement and loan-processing logic requires a validated school reference.

From a Data Vault modeling perspective, the metadata's heuristic classification identifies this object as standalone. In practical terms this suggests the table behaves as a hub-like reference set—a single, self-contained catalogue of school identifiers and descriptive attributes—rather than a transactional link or an update-audited satellite. The absence of an inbound foreign key to a parent configuration table reinforces its role as an independent lookup source.

Key Information Stored

The documented physical schema for 12.2.2 comprises ten columns. The most significant include:

  • SCHOOL_ID — The surrogate primary key, defined by the constraint PER_JP_SCHOOL_LOOKUPS_PK. This is the single unique index and therefore the only documented business-key candidate. It is the value propagated to every dependent table.
  • SCHOOL_NAME — The display name of the educational institution, typically in Japanese (Kanji) script.
  • SCHOOL_NAME_KANA — The phonetic (Kana) rendering of the school name, enabling correct pronunciation and search behavior for Japanese users.
  • MAJOR — The field or discipline of study associated with the institution.
  • MAJOR_KANA — The Kana representation of the major, mirroring the naming convention applied to the school name.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns providing audit lineage for each reference row.

The duplicate Japanese/Kana pairing is a deliberate design pattern that supports both accurate visual presentation and reliable linguistic matching, a recurring requirement in Japanese localization data models.

Common Use Cases and Queries

Typical applications include returning a school name for a stored identifier, validating user-entered institution data, and populating list-of-values (LOV) pickers in self-service HR and financial disbursement forms.

  • Retrieving a school for display: SELECT school_id, school_name, school_name_kana FROM per_jp_school_lookups WHERE school_id = :p_school_id;
  • Fuzzy search on the Kana field: SELECT school_id, school_name FROM per_jp_school_lookups WHERE school_name_kana LIKE :p_kana || '%';
  • Reference-set reporting: Join to dependent tables to produce detailed output, e.g. SELECT s.school_name, d.* FROM per_jp_school_lookups s, igf_sl_dl_setup_all d WHERE s.school_id = d.school_id;
  • Value-count auditing: A simple SELECT COUNT(*) FROM per_jp_school_lookups; verifies the reference set is fully loaded, which is a common post-migration validation step.

Related Objects

The metadata documents four tables with foreign keys referencing SCHOOL_ID. These belong to the IGF (Financial Aid / Student Loans) product family and represent the principal consumers of this lookup:

These relationships are read-only from the school lookup's perspective: PER_JP_SCHOOL_LOOKUPS is the referenced parent, and each IGF table is a dependent child. No foreign key is documented on PER_JP_SCHOOL_LOOKUPS itself. Because the object is flagged Oracle Proprietary and Confidential, external copying of its content should be avoided.