Search Results appl_sequence_number




Overview
Explore in AI Chat

Overview

The IGS_CO_PREV_REQS table belongs to the IGS (Student System) product family within Oracle E-Business Suite. It is documented as obsolete in ETRM for both release 12.1.1 and 12.2.2, and the ETRM implementation notes explicitly state "Not implemented in this database," reflecting the retirement of the legacy IGS Student System modules in favor of successor Oracle products. Despite its obsolete status, the object remains cataloged because historical EBS instances and archived schemas may still contain the underlying segments, and because it participates in foreign-key relationships that persist in documentation.

The table's purpose, as described in the metadata, is to maintain the required information to hold a correspondence request for preview and later distribution. Each row therefore represents a single correspondence item — a letter, email, or other communication — staged for review before it is dispatched to a recipient such as a student, applicant, or third party. The documented physical schema under owner IGS comprises 40 columns and one unique index, IGS_CO_PREV_REQS_PK, which serves as the primary key.

Applying the heuristic Data Vault classification supplied in the metadata, this object is satellite-leaning. It records descriptive, state-bearing attributes about a correspondence request and carries foreign-key dependencies outward to descriptive parent tables, rather than acting as a pure hub of business keys or a link resolving many-to-many relationships. Analysts modeling this data for a warehouse should treat it as a satellite attached to a correspondence-request hub, with its business keys supplying the hub identity.

Key Information Stored

The composite primary key, IGS_CO_PREV_REQS_PK, is defined over CONCURRENT_REQUEST_ID and FF_REQUEST_HIST_ID. This composite key is the only documented unique index and therefore the strongest business-key candidate; the two columns together identify the correspondence request and its associated fulfillment request history record.

Common Use Cases and Queries

Historically, this table supported correspondence preview, pending approval, and subsequent distribution reporting. A typical query retrieves the current letter content and status for a given concurrent request:

  • SELECT CONCURRENT_REQUEST_ID, PERSON_ID, LETTER_TYPE_CODE, REQUEST_STATUS_CODE, EMAIL_SUBJECT FROM IGS_CO_PREV_REQS WHERE REQUEST_STATUS_CODE = :status;
  • Joining to IGS_CO_MAPPING on SYS_LTR_CODE to resolve the letter mapping definition.
  • Aggregating AWARD_YEAR and AWARD_PRD_CD to report correspondence volume by award period.
  • Comparing ORIGINAL_CONTENT_XML with CURRENT_CONTENT_XML to identify edits introduced during preview.

Because the object is documented as obsolete and not implemented, these patterns apply principally to archival or migration analysis rather than live transactional processing.

Related Objects

  • IGS_CO_MAPPING — referenced by IGS_CO_PREV_REQS.SYS_LTR_CODE through the documented foreign key; supplies the correspondence mapping definition.
  • IGS_CO_PREV_REQS_PK — the unique index enforcing the composite primary key.
  • Concurrent request infrastructure — CONCURRENT_REQUEST_ID references the standard concurrent request identifier, linking the row to request scheduling and output.
  • Fulfillment request history — FF_REQUEST_HIST_ID links the correspondence to the fulfillment history record.
  • Person and application objects — PERSON_ID, ADM_APPL_NUMBER, and APPL_SEQUENCE_NUMBER associate the row with person and admission application entities maintained elsewhere in the IGS schema.