Results for “reason_for_leaving”

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

Overview

IGSBV_EMPLOYMENTS is a read-only view owned by the APPS schema within the IGS (Student System) product family of Oracle E-Business Suite. It presents the employment information of a person, drawing together the employment history record of a party together with the associated employment detail record. The view is defined with the WITH READ ONLY clause, so it is intended strictly for query, reporting, and integration consumption rather than for direct data manipulation. Because employment and tenure data feed student records, financial aid, and institutional reporting in the Student System, the view serves as a stable, denormalized access point that shields callers from the underlying table joins. The user search term fraction_of_employment maps directly to a projected column in this view, which is derived from the FRACTION_OF_TENURE column of the employment history table and aliased as FRACTION_OF_EMPLOYMENT.

Underlying Base Objects

The view is defined over two base tables joined on the employment history identifier:

• HZ_EMPLOYMENT_HISTORY (aliased EH) — the primary source of employment facts, including dates, employer, division, branch, military service attributes, weekly hours, and reason for leaving.
• IGS_AD_HZ_EMP_DTL (aliased HED) — the Student System employment detail table, supplying the occupational title code and the HZ_EMP_DTL_ID.

The join predicate is EH.EMPLOYMENT_HISTORY_ID = HED.EMPLOYMENT_HISTORY_ID. The ETRM 12.2.2 metadata records no separately documented base objects, but the view text itself establishes these two tables as the referenced objects. Certain descriptive attributes, such as employment type and tenure code, are not resolved at the view level; instead the view projects lookup descriptors (for example _LA:EH.EMPLOYMENT_TYPE_CODE:AR_LOOKUPS:HZ_EMPLOYMENT_TYPE:MEANING) that prompt the consuming application or report to translate the code via AR_LOOKUPS.

Key Columns

The columns most significant to reporting are:

• PARTY_ID — identifies the person to whom the employment record belongs.
• BEGIN_DATE / END_DATE — the effective period of the employment.
• EMPLOYER / DIVISION / BRANCH — the employing organization hierarchy.
• FRACTION_OF_EMPLOYMENT — aliased from FRACTION_OF_TENURE; expresses the proportion of full-time employment, matching the user's search term.
• _LA:TYPE_OF_EMPLOYMENT and _LA:TENURE_OF_EMPLOYMENT — descriptor columns exposing lookup codes (HZ_EMPLOYMENT_TYPE and HZ_TENURE_CODE) for resolution against AR_LOOKUPS.
• OCCUPATIONAL_TITLE_CODE, WEEKLY_WORK_HOURS, EMPLOYED_AS_TITLE, SUPERVISOR_NAME — role and effort descriptors.
• MILITARY_RANK, SERVED, STATION — military service attributes.
• COMMENTS, REASON_FOR_LEAVING — free-text context.
• EMPLOYED_BY_PARTY_ID, HZ_EMP_DTL_ID, EMPLOYMENT_HISTORY_ID — surrogate keys linking back to source records.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Common Use Cases and Queries

Typical scenarios include verifying a student's or applicant's employment and tenure fraction, reporting on work hours for financial aid or eligibility assessment, and integrating employment data into downstream systems. Because the view is read-only, it is safe for concurrent reporting.

Retrieve employment records with a partial tenure fraction for a specific party:

• SELECT party_id, begin_date, end_date, employed_by_name_company, fraction_of_employment FROM igsbv_employments WHERE party_id = :p_party_id AND fraction_of_employment < 1 ORDER BY begin_date DESC;

Join to AR_LOOKUPS to resolve the tenure descriptor to a readable meaning:

• SELECT e.party_id, e.fraction_of_employment, al.meaning tenure_meaning FROM igsbv_employments e, ar_lookups al WHERE e."_LA:TENURE_OF_EMPLOYMENT" = al.lookup_code AND al.lookup_type = 'HZ_TENURE_CODE';

Because the projected lookup columns carry descriptor names, reports should resolve them against AR_LOOKUPS rather than expecting decoded text directly from the view. Filtering and joining on PARTY_ID and EMPLOYMENT_HISTORY_ID provides the most reliable path back to source records.