Search Results pay_range_from

Overview

The view IGFBV_STUDENT_EMPLOYMENT_JOBS is an Oracle E-Business Suite database object owned by the APPS schema and registered under the Financial Aid (IGF) product family. Its documented purpose is to serve as the base view for the entity that holds the Student Employment Job listing within the Oracle Student System and Financial Aid modules. In Oracle EBS 12.1.1 and 12.2.2, views of this naming convention (prefixed with IGFBV_) are typically exposed as the queryable layer for an underlying business entity, often surfaced through OAF-based maintenance pages, the Integrated SOA Gateway, or Business Event integration points.

Because the entity pertains to student employment — the on-campus and off-campus work-study positions or federal work-study job postings available to a student population — the view is expected to present a single row per listed job with attributes covering the employer, location, pay range, supervisor contact, and eligibility indicators. Reporting consumers use it to enumerate available positions, drive eligibility checks during packaging, and feed downstream integration or third-party job-board extracts.

Note that the documented view text is a placeholder stub: SELECT NULL, NULL, ... , NULL FROM DUAL WITH READ ONLY. This indicates that in the supplied ETRM 12.2.2 metadata, no runtime SELECT statement is resolved; the column list is documented but no base object binding is recorded. Any use of this view in a live environment should therefore be validated against the actual database definition.

Underlying Base Objects

The ETRM 12.2.2 documentation records no referenced base objects and no owner other than APPS, which is unusual for an IGFBV view. In a functioning EBS instance, the corresponding entity is normally maintained against a base table such as IGF_STUDENT_EMPLOYMENT_JOBS (or an equivalently named IGF_ translation table), with the IGFBV_ view acting as a read-only projection used by the OAF view object and by SQL-based reporting. Common accompanying objects include a _TL translations table if descriptions are multi-lingual, and lookup views resolving WORK_LOCATION, CLOSED_INDICATOR, and HELP_AMERICA_READ_POSITION codes via FND_LOOKUPS.

The WITH READ ONLY clause in the documented text confirms the intended contract: this object is for reading only and cannot be the target of DML. Inserts, updates, and deletes must be routed through the owning entity's API or OAF transaction layer.

Key Columns

• ORGANIZATIONAL_UNIT_CODE – Identifies the institution or organizational unit owning the job listing; typical join key for org-based security.
• JOB_CODE – The employment job code, key to the position classification.
• JOB_DESCRIPTION – The narrative description of the job, the column most commonly targeted by keyword searches.
• JOB_PURPOSE, JOB_SKILLS, CAREER_OBJECTIVE – Qualitative attributes describing the position's purpose, required skills, and career alignment.
• WORK_LOCATION and WORK_LOCACTION_DEV – The physical or descriptive work location; note the documented typographic variant "LOCACTION."
• OFF_CAMPUS_EMPLOYER – Employer name when the position is off campus.
• SUPERVISOR_CONTACT, TELEPHONE_NUMBER – Contact details for the hiring supervisor.
• PAY_RANGE_FROM, PAY_RANGE_TO – The compensation band for the position.
• WORK_START_DATE – Expected start date for the placement.
• CLOSED_INDICATOR – Flags whether the listing is open or closed to applicants.
• HELP_AMERICA_READ_POSITION, COMMUNITY_SERVICE_POSITION – Federal work-study program flags identifying qualifying service positions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – Standard EBS WHO columns for audit and incremental extracts.

Common Use Cases and Queries

Typical reporting scenarios include publishing open student employment listings, reconciling work-study eligibility, and extracting job data for external job boards. A simple listing query is:

SELECT job_code, job_description, work_location,
       pay_range_from, pay_range_to, work_start_date
  FROM apps.igfbv_student_employment_jobs
 WHERE closed_indicator = 'N'
   AND organizational_unit_code = :org_code
 ORDER BY job_code;

A keyword search on description, matching the "job_description" search that motivated this summary, would take the form:

SELECT job_code, job_description, off_campus_employer
  FROM apps.igfbv_student_employment_jobs
 WHERE UPPER(job_description) LIKE '%' || UPPER(:keyword) || '%';

Incremental replication for a data warehouse should filter on LAST_UPDATE_DATE. Because the documented view text is a stub, confirm the deployed definition in your instance before relying on these queries in production.