Search Results pe_emp_categories




Overview
Explore in AI Chat

Overview

IGS_PE_TYP_EMP_CAT_V is an Oracle EBS seeded database view owned by the APPS schema. It belongs to the Student Systems / People Enterprise (IGS) product family and, more specifically, to the person type and employment category area used by Oracle Student System and related HR-integrated modules. The view exposes a flattened, user-friendly projection of person employment category assignments, resolving raw lookup codes into their descriptive meanings.

Its role in reporting and integration is to provide a convenient, denormalized source for querying which persons hold a Faculty or Staff type and what their employment category is. Because it joins the transactional person type instance data to the system type and to the lookup values in a single definition, report writers, concurrent programs, and integration interfaces can retrieve decoded results without repeatedly reconstructing the three-table join themselves. The user search term "pe_emp_categories" corresponds to the lookup type PE_EMP_CATEGORIES that this view consumes, confirming the object's purpose as the reporting vehicle for employment categories associated with person types.

Underlying Base Objects

The view is defined over three base objects, all referenced in the view text:

The ETRM metadata lists no separately documented referenced base objects for this view, so the relationships above are derived directly from the documented view text. Joins are performed on PERSON_TYPE_CODE between the instance and person type tables, and on LOOKUP_CODE equal to EMPLMNT_CATEGORY_CODE for the decode.

Key Columns

  • ROW_ID — the ROWID of the underlying IGS_PE_TYP_INSTANCES_ALL row, useful for uniquely identifying a record.
  • PERSON_ID — the party/person identifier for the individual holding the type and category.
  • EMPLMNT_CATEGORY_CODE — the employment category lookup code assigned to the person.
  • EMP_CATEGORY_MEANING — the decoded, human-readable meaning from IGS_LOOKUP_VALUES for the category code.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle WHO audit columns, sourced from the instance table.

Common Use Cases and Queries

Typical uses include faculty/staff employment category reporting, downstream integration extracts, and validation queries. Note that results are restricted to SYSTEM_TYPE in ('FACULTY','STAFF') and to currently effective rows where SYSDATE falls between START_DATE and NVL(END_DATE, SYSDATE).

  • List employment categories for a given person:
    • SELECT person_id, emplmnt_category_code, emp_category_meaning FROM apps.igs_pe_typ_emp_cat_v WHERE person_id = :p_person_id;
  • Produce a distribution of employment categories:
    • SELECT emplmnt_category_code, emp_category_meaning, COUNT(*) FROM apps.igs_pe_typ_emp_cat_v GROUP BY emplmnt_category_code, emp_category_meaning;
  • Join to a person/party table to obtain names for an extract:
    • SELECT v.person_id, v.emp_category_meaning FROM apps.igs_pe_typ_emp_cat_v v ORDER BY v.person_id;

Because the view enforces the SYSDATE-based effective dating and the Faculty/Staff system type restriction internally, consumers should not expect historical or non-faculty/staff categories from this object; use the base tables directly when that scope is required.