Search Results igs_rc_i_status_v
Overview
The view IGS_RC_I_STATUS_V belongs to the Oracle E-Business Suite IGS — Student System product family, a module now classified as obsolete in the ETRM reference for EBS 12.1.1 and 12.2.2. Its documented purpose is to present Inquiry Status information derived from the seed data dictionary view AS_STATUSES_VL. The view acts as a curated, inquiry-specific projection of the general status entity, joining the status value list against lookup values that are governed by the lookup type ENQUIRY_STATUS.
In an EBS reporting and integration context, this view would have served as a read-only interface for enquiry (prospective applicant) status reporting — for example, exposing whether an enquiry had been acknowledged, completed, or registered. Because the object is documented as not implemented in this database, it is best treated as a historical or reference-only artifact. Installations on 12.1.1 or 12.2.2 should not expect it to exist in their schema; the metadata is retained for upgrade and impact analysis.
Underlying Base Objects
The ETRM entry lists no owner and no referenced base objects, and explicitly states the view is not implemented. The documented view text nonetheless reveals the effective data lineage:
AS_STATUSES_VL— aliasedES; supplies the core status rows, includingROW_ID,MEANING,DESCRIPTION,STATUS_CODE,ENABLED_FLAG, and the standard WHO audit columns.IGS_LOOKUP_VALUES— aliasedLKUP; supplies the display meaning and closed indicator for the lookup typeENQUIRY_STATUS.
The two sources are joined on LKUP.LOOKUP_TYPE = 'ENQUIRY_STATUS', LKUP.LOOKUP_CODE = ES.STATUS_CODE, with an additional restrictive predicate limiting LOOKUP_CODE to OSS_ACKNOWLEGE, OSS_COMPLETE, and OSS_REGISTERED. This three-value filter is what narrows the generic status list to the enquiry lifecycle subset.
Key Columns
ROW_ID— unique row identifier inherited from the status entity.ENQUIRY_STATUS— the descriptive meaning of the status, surfaced fromAS_STATUSES_VL.MEANING.DESCRIPTION— longer explanatory text for the status.S_ENQUIRY_STATUS— the underlying status code; this is the key referenced by the search term s_enquiry_status, and it corresponds to the restrictedOSS_*lookup codes.ENABLED_FLAG— indicates whether the status is active and selectable.MEANING— display meaning sourced fromIGS_LOOKUP_VALUES, allowing a lookup-specific label distinct from the base status meaning.DSP_CLOSED_IND— closed indicator from the lookup, used to determine whether an enquiry status represents a terminal or closed state.- Standard WHO audit columns —
CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE,LAST_UPDATE_LOGIN.
Common Use Cases and Queries
Typical usage would have been to populate enquiry status list-of-values, drive status display in enquiry forms, or feed downstream reporting. A representative query resolves the status code to its display meaning:
SELECT s_enquiry_status, enquiry_status, meaning, dsp_closed_ind FROM igs_rc_i_status_v WHERE enabled_flag = 'Y' ORDER BY meaning;
Because the view is documented as not implemented, code should defend against its absence, for example by checking ALL_VIEWS before referencing it, and by falling back to AS_STATUSES_VL joined to IGS_LOOKUP_VALUES where the object is unavailable.
-
View: IGS_RC_I_STATUS_V
12.2.2
product: IGS - Student System (Obsolete) , description: Inquiry Status, based on AS_STATUSES_VL , implementation_dba_data: Not implemented in this database ,
-
View: IGS_RC_I_STATUS_V
12.1.1
product: IGS - Student System , description: Inquiry Status, based on AS_STATUSES_VL , implementation_dba_data: Not implemented in this database ,
-
View: IGS_RC_I_APPL_V
12.1.1
product: IGS - Student System , description: This view will be based on OMO public view AS_SALES_LEADS_V and IGS_RC_I_APPL_ALL junction table. , implementation_dba_data: Not implemented in this database ,
-
View: IGS_RC_I_APPL_V
12.2.2
product: IGS - Student System (Obsolete) , description: This view will be based on OMO public view AS_SALES_LEADS_V and IGS_RC_I_APPL_ALL junction table. , implementation_dba_data: Not implemented in this database ,
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 FND Design Data
12.2.2