Results for “approved_dt”

50+ results




Overview
Explore in AI Chat

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

Overview

The view IGS_EN_SPI_RCONDS_V belongs to the IGS – Student System product family within Oracle E-Business Suite (documented for 12.1.1 and 12.2.2). In the ETRM metadata it is explicitly flagged as Obsolete and is reported as Not implemented in this database, meaning it is a residue object retained for historical reference rather than a supported, currently deployed database object. Its business purpose is to present Student Intermission Return Conditions — the conditions under which a student who has taken an intermission (a formal leave or suspension of study) is permitted or required to return to their programme.

The view consolidates the transactional return-condition record for a student with descriptive lookups, the return-condition master definition, and the identifying details of the staff member who approved the record. Because the user search term is approved_by, the view is particularly relevant as a reporting surface for approval attribution: it exposes both the internal APPROVED_BY party identifier and the resolved approver party number and name.

As a reporting and integration object it is read-only in nature — a join-based query rather than a base table — and would typically have been consumed by student-system inquiry screens, extracts, or interface programs needing a flattened, human-readable intermission return-condition record.

Underlying Base Objects

The documented view text defines four referenced objects:

Note that the outer join on HZ_PARTIES means records with no recorded approver are still returned, with null approver attributes.

Key Columns

  • PERSON_ID, COURSE_CD, START_DT — identify the student, the course/programme, and the relevant start date of the intermission return.
  • RETURN_CONDITION and RETURN_CONDITION_DESC — the coded condition and its descriptive text from the master table.
  • STATUS_CODE and STATUS_DESC — the intermission return-condition status code and its decoded meaning from the lookup.
  • APPROVED_DT — the date the return condition was approved.
  • APPROVED_BY — the party identifier of the approving person; this is the column most directly associated with the "approved_by" search.
  • APPROVER_NUMBER, APPROVER_NAME — the party number and party name resolved from HZ_PARTIES, giving readable approval attribution.
  • LOGICAL_DELETE_DATE — supports logical (soft) deletion semantics rather than physical row removal.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO audit columns.
  • ROW_ID — the row identifier exposed from SRC.ROWID.

Common Use Cases and Queries

Typical uses include auditing who approved intermission return conditions, listing outstanding or approved conditions for a student, and feeding extracts with readable approver and status text. A representative query filtering or projecting the approval attributes is:

  • SELECT person_id, course_cd, return_condition_desc, status_desc, approved_dt, approved_by, approver_number, approver_name FROM igs_en_spi_rconds_v WHERE approved_by IS NOT NULL;
  • SELECT person_id, status_desc, approver_name FROM igs_en_spi_rconds_v WHERE logical_delete_date IS NULL ORDER BY approved_dt DESC;
  • SELECT approver_number, approver_name, COUNT(*) FROM igs_en_spi_rconds_v GROUP BY approver_number, approver_name;

Because the object is marked obsolete and not implemented, these patterns should be validated against the actual deployed schema before reliance in production reporting.