Results for “per_jp_school_lookups_pk”

14 results




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

Overview

HR.PER_JP_SCHOOL_LOOKUPS is a reference lookup table within the Oracle E-Business Suite HR (Human Resources) schema. As documented in the ETRM metadata, it holds information provided by external vendors on Japanese educational institutions. This information is referenced when validating entries into PER_ANALYSIS_CRITERIA, and the table is used exclusively in the JP-HRMS (Japanese localization of Oracle HRMS) module. The object carries a status of VALID and is registered under FND Design Data as PER.PER_JP_SCHOOL_LOOKUPS.

Because the table functions purely as a controlled vocabulary of schools and majors validated against employee analysis criteria, it exhibits no outward foreign-key dependencies on other database objects; the dependency section confirms that HR.PER_JP_SCHOOL_LOOKUPS does not reference any database object directly. Conversely, it is referenced by external dependent objects, including a synonym or view form documented as PER_JP_SCHOOL_LOOKUPS#. From a Data Vault modeling perspective, the heuristic classification for this object is standalone, meaning it is best treated as an independent reference or lookup hub rather than a link or satellite, since it participates as a parent dimension in relationships but depends on no upstream entity itself. Storage resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and the unique index is created in APPS_TS_TX_IDX.

Key Information Stored

The table documents ten columns. The single most important is the primary key column SCHOOL_ID (VARCHAR2, length 11, mandatory), which is enforced through the unique index PER_JP_SCHOOL_LOOKUPS_PK. In keeping with surrogate-versus-business-key conventions, SCHOOL_ID serves both as the documented primary key and as the sole unique index candidate, so it functions simultaneously as the surrogate identifier and the de facto business key for the vendor-supplied school record.

The descriptive attributes provide bilingual Japanese educational data:

  • SCHOOL_NAME (VARCHAR2, 80) — the school name rendered in Kanji characters.
  • SCHOOL_NAME_KANA (VARCHAR2, 300) — the school name rendered in Kana characters.
  • MAJOR (VARCHAR2, 50) — the major or field of study in Kanji characters.
  • MAJOR_KANA (VARCHAR2, 180) — the major in Kana characters.

The remaining five columns are the standard Who columns maintained automatically by the Oracle Applications framework: CREATED_BY (NUMBER, 15), CREATION_DATE (DATE), LAST_UPDATED_BY (NUMBER, 15), LAST_UPDATE_DATE (DATE), and LAST_UPDATE_LOGIN (NUMBER, 15). These support audit tracing and concurrent-program accountability.

Common Use Cases and Queries

The primary functional use case is validation: when users enter educational background data into PER_ANALYSIS_CRITERIA, the entered school and major values are checked against this lookup table to ensure consistency and standardization across the JP-HRMS implementation. Reporting scenarios typically join the lookup to dependent tables using SCHOOL_ID to translate stored identifiers into readable Kanji or Kana school and major names.

A basic lookup query follows the documented pattern:

  • SELECT SCHOOL_ID, SCHOOL_NAME, SCHOOL_NAME_KANA, MAJOR, MAJOR_KANA FROM HR.PER_JP_SCHOOL_LOOKUPS WHERE SCHOOL_ID = :p_school_id;
  • SELECT SCHOOL_ID, SCHOOL_NAME FROM HR.PER_JP_SCHOOL_LOOKUPS ORDER BY SCHOOL_NAME_KANA; for Kana-ordered reporting of all institutions.
  • Joining to a dependent disbursement or loan setup table on SCHOOL_ID to enrich records with school and major descriptions, for example aggregating learner records per institution.

Because the table is vendor-supplied and localized, maintenance activities generally involve bulk loading or periodic refresh rather than day-to-day entry, and the standard Who columns should be preserved for audit purposes.

Related Objects

Although the table itself references nothing, it is referenced by several dependent objects, all of which join through the SCHOOL_ID column:

These IGF-family tables belong to the Oracle Student Financial Aid / Loans domain and link the school lookup into disbursement and loan-response processing. Any change to a SCHOOL_ID value would therefore ripple into these referencing tables, reinforcing that SCHOOL_ID must remain stable once established.