Search Results emp_cat_code




Overview
Explore in AI Chat

Overview

IGS_PS_EMP_CATS_WL_HR_V is an Oracle E-Business Suite view owned by the APPS schema and defined in the Oracle Student System (IGS) product family. It exposes employment category workload data associated with a calendar category, joined to Oracle HRMS lookup values so that the internal employment category code is presented alongside its descriptive meaning. The view acts as a reporting and integration convenience layer: consumers do not have to resolve the HR_LOOKUPS relationship or apply the enabled/date-effectiveness filters themselves. This is directly relevant to a search on emp_cat_code, because that column is one of the principal outputs of the view. In 12.1.1 and 12.2.2 the object is read-only from the perspective of the APPS consumer; it is a query surface, not a DML target.

Underlying Base Objects

The view is defined over two base objects:

  • IGS_PS_EMP_CATS_WL — the driving table (aliased ECW), holding the calendar category and the expected workload number per employment category.
  • HR_LOOKUPS — the HRMS lookup table (aliased HRLKUP), providing the descriptive meaning for each employment category code.

The ETRM metadata lists no additional referenced base objects, so the definition is a straightforward equijoin between these two tables. The join predicate is ecw.emp_cat_code = hrlkup.lookup_code, restricted by hrlkup.lookup_type = 'EMP_CAT', hrlkup.enabled_flag = 'Y', and the date-effectiveness condition SYSDATE BETWEEN NVL(hrlkup.start_date_active,SYSDATE) AND NVL(hrlkup.end_date_active,SYSDATE). The ROWID of IGS_PS_EMP_CATS_WL is surfaced as ROW_ID. Because the filters are applied inside the view, only currently enabled and currently effective EMP_CAT lookups appear in the result set.

Key Columns

Common Use Cases and Queries

Typical uses include reporting expected workload by employment category, validating that a given employment category is effective, and feeding integrations that require the descriptive category text rather than the code. A simple lookup by category is:

  • SELECT emp_cat_code, emp_cat_desc, cal_cat_code, expected_wl_num FROM apps.igs_ps_emp_cats_wl_hr_v WHERE emp_cat_code = :p_emp_cat_code;
  • SELECT cal_cat_code, emp_cat_desc, expected_wl_num FROM apps.igs_ps_emp_cats_wl_hr_v ORDER BY cal_cat_code, emp_cat_code;

Because the enabled and date-effectiveness filters are embedded, a row absent from the view may still exist in IGS_PS_EMP_CATS_WL with a disabled or expired lookup; troubleshooting should therefore query the base tables directly when a code is unexpectedly missing.