Results for “emp_category_meaning”

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

Overview

IGS_PE_TYP_EMP_CAT_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product family. Its defined purpose is to expose the active employment category associated with a person record held in the person type instances table. In EBS 12.1.1 and 12.2.2 the object is delivered in VALID status and is classified under the IGS - Student System module, making it part of the standard seeded schema rather than a customer extension.

The view is principally used for reporting and integration scenarios in which downstream programs must resolve a person's employment category only for individuals whose person type qualifies as academic or administrative staff. Because the filter logic is embedded in the view definition, consumers avoid re-implementing the person-type and effective-date rules in every report, interface, or concurrent program. The view also decorates the stored code with its descriptive meaning, which simplifies extract files and BI Publisher layouts that must present a user-facing value rather than an internal lookup code.

Underlying Base Objects

The view text is defined over three sources:

• IGS_PE_TYP_INSTANCES_ALL — aliased TYP; supplies PERSON_ID, EMPLMNT_CATEGORY_CODE, and the standard WHO audit columns. Despite the _ALL suffix, the view itself applies no org-context restriction, so partitioning by operating unit is the responsibility of the calling query.
• IGS_PE_PERSON_TYPES — aliased SYSTYP; joined on PERSON_TYPE_CODE and filtered to SYSTEM_TYPE values of 'FACULTY' or 'STAFF'. This restricts output to employment-related person types and excludes student or applicant types.
• IGS_LOOKUP_VALUES — aliased LKUP1; joined where LOOKUP_TYPE equals 'PE_EMP_CATEGORIES' and LOOKUP_CODE equals EMPLMNT_CATEGORY_CODE, providing the MEANING column returned as EMP_CATEGORY_MEANING.

The effective-date predicate SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE) causes only currently active person type instance rows to qualify; rows with a future start date or a past end date are excluded. Note that the metadata lists no separately documented referenced base objects, so the view text itself is the authoritative definition.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_PE_TYP_INSTANCES_ALL row, useful for de-duplication or direct row addressing.
• PERSON_ID — the unique identifier of the person, joinable to PER_ALL_PEOPLE_F and other person-centric IGS tables.
• EMPLMNT_CATEGORY_CODE — the stored employment category code, sourced from the person type instance and validated against lookup type PE_EMP_CATEGORIES.
• EMP_CATEGORY_MEANING — the descriptive meaning of that code, suitable for display in reports and interfaces.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns reflecting the WHO information of the source instance row.

Common Use Cases and Queries

Typical scenarios include producing staff and faculty headcount extracts, validating employment category assignments during data migration, and supplying integration payloads where only active employment-category values are required. A representative query listing active employment categories for faculty and staff is:

SELECT person_id, emplmnt_category_code, emp_category_meaning
FROM apps.igs_pe_typ_emp_cat_v
WHERE emplmnt_category_code = '&p_category';

To enrich a person listing with the descriptive category:

SELECT p.person_id, p.full_name, v.emp_category_meaning
FROM apps.per_all_people_f p, apps.igs_pe_typ_emp_cat_v v
WHERE p.person_id = v.person_id
AND SYSDATE BETWEEN p.effective_start_date AND p.effective_end_date;

Because the view returns one row per qualifying person type instance, queries should be reviewed for potential duplicates where a person holds more than one active FACULTY or STAFF instance, and result sets should be constrained by PERSON_ID or ROW_ID as appropriate.