Results for “dsp_closed_ind”

25 results




Overview
Explore in AI Chat

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

Overview

IGR_I_STATUS_V is a database view belonging to the Oracle E-Business Suite product family designated IGS — Student System, an obsolete module retained for backward compatibility within EBS 12.1.1 and 12.2.2 environments. The view presents inquiry status information, exposing a filtered and joined set of inquiry (enquiry) status definitions suitable for reporting on the state of prospective-student enquiries. Its definition derives from the AS_STATUSES_VL base view and the IGS_LOOKUP_VALUES lookup table, joined on the lookup type IGR_ENQUIRY_STATUS. The result is a denormalised list of enquiry statuses, each accompanied by its translatable meaning, closed indicator, and standard Oracle audit columns.

Because the object is documented as "Not implemented in this database" in the supplied ETRM metadata, IGR_I_STATUS_V should be treated as a documented view whose physical instantiation depends on the specific environment. Where the IGS schema is present, it serves as a read-only reporting surface rather than a transactional object.

Underlying Base Objects

The view text joins two documented objects:

  • AS_STATUSES_VL — aliased ES. This is the source of the core status attributes: STATUS_CODE, MEANING, DESCRIPTION, and ENABLED_FLAG, together with the audit columns. The _VL suffix indicates a view whose translated columns are resolved according to the session language.
  • IGS_LOOKUP_VALUES — aliased LKUP. This supplies the lookup-level MEANING and the CLOSED_IND flag, and drives the filtering of permitted statuses.

The join is defined as LKUP.LOOKUP_TYPE = 'IGR_ENQUIRY_STATUS' AND LKUP.LOOKUP_CODE = ES.STATUS_CODE. The metadata records no additional "referenced base objects", so all lineage traces to these two sources.

Key Columns

  • ROW_ID — the unique row identifier of the underlying status record, used for row-level addressing and join keys.
  • ENQUIRY_STATUS — the translated meaning of the enquiry status (from ES.MEANING).
  • DESCRIPTION — the descriptive text for the status.
  • S_ENQUIRY_STATUS — the short status code (ES.STATUS_CODE), the primary business key.
  • ENABLED_FLAG — indicates whether the status is currently active.
  • MEANING — the lookup-level meaning (from LKUP.MEANING).
  • DSP_CLOSED_IND — the lookup CLOSED_IND, indicating whether the enquiry status is treated as closed.
  • CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard who-columns for audit and concurrency analysis.

Common Use Cases and Queries

The WHERE clause restricts output to three lookup codes: OSS_ACKNOWLEGE, OSS_COMPLETE, and OSS_REGISTERED. Consequently the view returns a narrow, predefined set of enquiry lifecycle states, making it well suited to tracking acknowledgement, completion, and registration milestones of prospective-student enquiries.

A typical retrieval of all active enquiry statuses:

  • SELECT S_ENQUIRY_STATUS, ENQUIRY_STATUS, DESCRIPTION, DSP_CLOSED_IND FROM IGR_I_STATUS_V WHERE ENABLED_FLAG = 'Y' ORDER BY S_ENQUIRY_STATUS;

To distinguish closed from open statuses for reporting:

  • SELECT ENQUIRY_STATUS, DSP_CLOSED_IND, COUNT(*) FROM IGR_I_STATUS_V GROUP BY ENQUIRY_STATUS, DSP_CLOSED_IND;

The view is commonly joined to enquiry or applicant fact tables on S_ENQUIRY_STATUS to decorate transactional records with human-readable status labels and closed-flags for dashboards, extracts, and integration feeds. Implementers should verify existence at runtime, since the metadata notes it is not implemented in every EBS database.