Search Results school_code




Overview
Explore in AI Chat

Overview

APPS.PER_JP_SCHOOL_LOOKUPS_V is a supplementary database view defined in the APPS schema of Oracle E-Business Suite, documented as VALID in Release 12.1.1 and 12.2.2. It belongs to the Oracle Human Resources (PER) product family and supports the Japanese localization of Oracle HRMS, specifically the school and major qualification lookups used on employee and applicant records. Functionally, the view exposes descriptive information about Japanese educational institutions (schools) and their associated academic majors, so that Oracle Forms screens and concurrent programs can present and validate that data without embedding complex join logic in each form. It is registered in FND Design Data (PER.PER_JP_SCHOOL_LOOKUPS_V) and is explicitly described as "a supplementary view used to simplify forms coding." ETRM documentation carries a standing warning: Oracle does not recommend querying or altering data through this view, since its definition may change dramatically in subsequent minor or major releases. The user's search term, "school_code," maps directly to the SCHOOL_CODE column surfaced by this view — the short alphanumeric identifier used to distinguish one school from another within the Japanese school lookup data.

Underlying Base Objects

The view is defined over the base object PER_JP_SCHOOL_LOOKUPS, exposed through an APPS synonym. This is the single documented dependency; the view does not itself reference additional tables or views. In practice, the base lookup table stores the Japanese school and major master data (codes, names, kana-name variants), while PER_JP_SCHOOL_LOOKUPS_V presents that data in a denormalized, forms-friendly row shape. ETRM records note that PER_JP_SCHOOL_LOOKUPS_V is not referenced by any other database object, confirming it is a leaf-level read-only convenience view rather than a foundational object used elsewhere in the schema. Because the ETRM source lists only PER_JP_SCHOOL_LOOKUPS as the referenced base object, any interpretation of the derived columns (such as ROW_ID) should be treated as a view affordance rather than a true physical column on the table.

Key Columns

The view returns fourteen columns, which can be grouped as follows:

  • ROW_ID (VARCHAR2, 18) — Row identifier, used by Oracle Forms for record navigation.
  • SCHOOL_ID (VARCHAR2, 11) — Unique identifier for a school record.
  • SCHOOL_TYPE (VARCHAR2) — Classification of the school (for example, category or level).
  • SCHOOL_CODE (VARCHAR2) — The code the user searched on; the user-facing short identifier for the school.
  • SCHOOL_NAME (VARCHAR2, 80) — School name in the standard Japanese character set.
  • SCHOOL_NAME_KANA (VARCHAR2, 300) — School name in kana, used for phonetic matching and sorting.
  • MAJOR_CODE (VARCHAR2) — Code identifying the major, department, or course of study.
  • MAJOR (VARCHAR2, 50) — Major name.
  • MAJOR_KANA (VARCHAR2, 180) — Major name in kana.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN (Who columns inherited from the base record).

Common Use Cases and Queries

Typical uses include extracting school and major lists for HR or applicant reporting, validating employee education records against school codes, and building integrations or data extracts for Japanese localization requirements. A participant's SCHOOL_CODE is generally resolved against this view to obtain the descriptive SCHOOL_NAME and SCHOOL_NAME_KANA. A representative query is:

  • SELECT school_id, school_code, school_name, school_name_kana, major_code, major, major_kana FROM apps.per_jp_school_lookups_v WHERE school_code = :school_code;
  • SELECT school_code, school_name FROM apps.per_jp_school_lookups_v ORDER BY school_name_kana;

Because ETRM classifies this as a forms-support view, direct querying is discouraged for production interfaces; where stability is required, the underlying PER_JP_SCHOOL_LOOKUPS table or a controlled custom view should be used instead.