Search Results internal_comments

Overview

IGSBV_AS_DOCUMENT_DETAILS is a view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It exposes the attributes of documents associated with a student academic order, presenting a consolidated, reporting-friendly projection of document generation and transcript request data. The object is classified as VALID across Oracle EBS 12.1.1 and 12.2.2, and is implemented as a database view rather than a table, meaning it holds no persistent storage and derives all of its content at runtime from its defining query.

The view is primarily consumed by concurrent programs, Oracle Reports layouts, and OAF-based pages that print or display official documents such as transcripts, enrollment certifications, and degree verification letters. Its role is to join document header data — order and item identifiers — with a broad set of recipient, hold, and transcript content attributes in a single relational shape. Because the view materializes lookup meanings through embedded value-set references rather than internal codes, it is well suited to end-user reporting layers that must display translated values.

Underlying Base Objects

ETRM documentation for this object records no referenced base objects. The view text itself is expressed as a single SELECT list with no visible FROM clause in the documented fragment, which indicates that the definition either relies on an inline query, a synonym, or a supporting subquery structure that was not captured in the excerpt. In practice, the columns exposed by IGSBV_AS_DOCUMENT_DETAILS correspond to attributes of the IGS_AS_DOCUMENT and related student system entities that store order-level document requests, recipient addresses, transcript content selections, and hold indicators.

The absence of documented base objects means that impact analysis should be performed directly against the ALL_DEPENDENCIES and DBA_VIEWS dictionaries rather than relying on the ETRM entry alone. This is particularly relevant for upgrade testing between 12.1.1 and 12.2.2, where underlying IGS tables may have been patched or extended.

Key Columns

The view projects a wide column list, organized into functional groups:

• Order and item identifiers: ITEM_NUMBER and ORDER_NUMBER tie each row to a specific document request line.
• Translated lookup attributes: DOCUMENT_TYPE, DOCUMENT_SUB_TYPE, and ITEM_STATUS are exposed through IGS_LOOKUP_VALUES, resolving to MEANING values for DOCUMENT_TYPE, DOCUMENT_SUB_TYPE, and ITEM_STATUS lookups respectively.
• Recipient data: RECIP_PERS_NAME, RECIP_INST_NAME, and the address lines RECIP_ADDR_LINE_1 through RECIP_ADDR_LINE_4, along with RECIP_CITY, RECIP_STATE, RECIP_POSTAL_CODE, RECIP_COUNTY, and RECIP_COUNTRY.
• Delivery details: RECIP_FAX_AREA_CODE, RECIP_FAX_COUNTRY_CODE, RECIP_FAX_NUMBER, EXPRESS_MAIL_TYPE, and EXPRESS_MAIL_TRACK_NUM.
• Transcript content inclusion flags: INCL_GPA, INCL_CLASS_RANK, INCL_CUM_HOURS_EARNED, INCL_DEGREE_EARNED, INCL_DATE_OF_GRADUATION, INCL_MAJORS, INCL_SSN, INCL_DATE_OF_BIRTH, and numerous additional INCL_ prefixed indicators controlling which academic facts print on the document.
• Hold controls: HOLD_RELEASE_OF_FINAL_GRADES, HOLD_DEGREE_EXPECTED, and HOLD_FOR_GRADE_CHG, which govern suppression of specific transcript elements.
• Duplication tracking: DUP_REQUESTED, DUP_REQ_DATE, and DUP_SENT_DATE for reissued documents.

The user search term deghold_seq_num does not appear in the documented column list, suggesting it belongs to a companion IGS object such as IGS_AS_DEGREE_HOLD or a related degree hold table rather than this view.

Common Use Cases and Queries

Typical usage involves retrieving document requests for a given order to drive printing or auditing workflows. A representative query is:

SELECT ITEM_NUMBER, ORDER_NUMBER, DOCUMENT_TYPE, ITEM_STATUS,
       RECIP_PERS_NAME, RECIP_CITY, DATE_PRODUCED
  FROM APPS.IGSBV_AS_DOCUMENT_DETAILS
 WHERE ORDER_NUMBER = :p_order_number;

A second scenario filters on inclusion indicators to confirm which transcripts contain GPA or degree data:

SELECT ITEM_NUMBER, INCL_GPA, INCL_DEGREE_EARNED, INCL_DATE_OF_GRADUATION
  FROM APPS.IGSBV_AS_DOCUMENT_DETAILS
 WHERE DUP_REQUESTED = 'Y';

Because the view resolves lookup codes to meanings, it is commonly used directly in BI Publisher data templates for student document letters without requiring additional lookup joins. When extending reports, ensure that any custom SQL referencing this view is retested after IGS patches, since the view definition is supplied by Oracle and may be recompiled during upgrades.