Search Results empl_time

Overview

APPS.IGS_PE_NONIMG_EMPL_V is a supplementary database view owned by the APPS schema within the Oracle E-Business Suite environment. It forms part of the Student System (IGS) product family and specifically supports the People (PE) subsystem, which manages person, employee, and party-related records across higher-education and institutional deployments. The view presents information relating to non-immigrant employee records — that is, employment details tied to individuals who are not permanent residents or citizens, typically captured through an associated non-immigrant form.

Oracle classifies this as a supplementary view used to simplify forms coding. It exists primarily to serve Oracle Forms-based user interfaces rather than as a stable integration or reporting interface. The ETRM documentation carries an explicit warning: Oracle does not recommend querying or altering data using this view, and its structure may change dramatically in subsequent minor or major releases. The view is flagged as VALID, with FND Design Data registered under IGS.IGS_PE_NONIMG_EMPL_V, indicating it is a registered, seeded dictionary object.

Underlying Base Objects

The dependency information in the ETRM metadata for APPS.IGS_PE_NONIMG_EMPL_V is incomplete. The source listing indicates the view references base objects, but the documented reference list is truncated, showing only a partial line ("A") and no complete set of underlying tables. Within this Oracle EBS 12.1.1 / 12.2.2 context, the view is understood to be defined over the non-immigrant employee base table — most likely IGS_PE_NONIMG_EMPL — together with joins to supporting lookup and party tables that resolve the descriptive columns. The presence of EMPL_PARTY_ID and EMPL_PARTY_NAME strongly suggests a join to HZ_PARTIES to surface the employee's party name. Similarly, EMPL_TYPE_DESC and EMPL_TIME_DESC resolve coded values into human-readable descriptions, typically drawing on lookup tables or views. Because the documented dependency set is not complete, base-object relationships beyond this should be verified directly against the database using ALL_DEPENDENCIES before relying on them.

Key Columns

• ROW_ID — ROWID pseudocolumn, supplied for row-level identification in dependent views or forms.
• NONIMG_EMPL_ID — Primary identifier for the non-immigrant employment record.
• NONIMG_FORM_ID — Foreign key linking the employment line to its parent non-immigrant form.
• EMPL_TYPE — The employee type code, matching the search term "empl_type". This is the core classification value for the employment record.
• EMPL_TYPE_DESC — The decoded, human-readable description of EMPL_TYPE, up to 80 characters.
• RECOMMEND_EMPL — Recommended employee indicator for the record.
• RESCIND_EMPL — Indicates whether the person has met the academic requirements (per the documented comment).
• EMPL_START_DATE / EMPL_END_DATE — The employment start and end dates for the assignment.
• EMPL_TIME / EMPL_TIME_DESC — Full-or-part-time code and its description.
• COURSE_RELEVANCE — Narrative describing how the employment relates to the person's course of study.
• EMPL_PARTY_ID / EMPL_PARTY_NAME — The employee's party identifier and name, resolving to the HZ_PARTIES record.
• ACTION_CODE — Describes the action to be taken on the row, such as ADD, EDIT, or Cancel.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, used for audit and concurrency.

Common Use Cases and Queries

The most common use is retrieval of employment records filtered by employee type, which corresponds to the original "empl_type" search. The following query lists non-immigrant employees of a given type whose employment is currently active:

SELECT nonimg_empl_id, empl_party_name, empl_type, empl_type_desc, empl_time_desc, empl_start_date, empl_end_date FROM apps.igs_pe_nonimg_empl_v WHERE empl_type = :p_empl_type AND (empl_end_date IS NULL OR empl_end_date > SYSDATE);

Because the view exposes a decoded description alongside the code, it is convenient for forms LOVs and reporting where the description is displayed but the code is stored. A second typical scenario identifies full-time versus part-time employment by joining or filtering on EMPL_TIME. Users should treat results as informational only and avoid DML against the view; for production reporting, querying the base tables directly is recommended.