Search Results igs_as_document_type

Overview

APPS.IGS_AS_DOC_DETAILS_V is a reporting and integration view within the Oracle E-Business Suite Student System (IGS) schema. It exposes the fee, recipient, and document-configuration attributes that govern the production and dispatch of student documents — transcripts, award certificates, confirmation letters, and similar outputs — generated through the Academic Document Production functionality. In EBS 12.1.1 and 12.2.2 the IGS product family supports academic records, and this view is the principal denormalised access point for document detail lines associated with a plan record.

The view is built over the IGS_AS_DOC_DETAILS base table and simply re-projects its columns, resolving the ROWID of the underlying row and applying NVL logic to derive effective fee values. Because the shipped DDL carries no joins, the view functions as a stable, pre-agreed interface: external reports, transcript-request interfaces, and third-party fulfilment systems may query it without binding directly to the base table, insulating them from physical schema changes. Users searching on the term "igs_as_document_type" typically encounter this object because the DOCUMENT_TYPE and DOCUMENT_SUB_TYPE columns are the discriminators that identify which class of document a detail line represents.

Underlying Base Objects

The view text selects exclusively from the dtl alias, which refers to the IGS_AS_DOC_DETAILS base table. The ETRM metadata for this view records no additional referenced base objects; no joins to plan, person, or institution tables are performed in the view definition. Consequently, the view is a one-to-one projection of IGS_AS_DOC_DETAILS: each row in the base table yields exactly one row in the view.

Two columns are computed rather than passed through. The effective delivery fee is NVL(dtl.overridden_doc_delivery_fee, dtl.delivery_fee), and the effective per-copy document fee is NVL(dtl.overridden_document_fee, dtl.doc_fee_per_copy). The raw base columns deliver_fee, doc_fee_per_copy, overridden_doc_delivery_fee, and overridden_document_fee remain exposed alongside the computed values, so consumers can distinguish standard fees from manually overridden ones.

Key Columns

• plan_id — identifier of the document production plan to which the detail line belongs; the primary linkage back to the plan header.
• document_type / document_sub_type — classification of the document (transcript, certificate, letter) and its finer subtype; the columns most often searched by name.
• doc_purpose_code — the stated purpose for which the document is produced.
• item_number / item_status / date_produced — inventory-style tracking of the produced output and its status.
• num_of_copies / delivery_method_type / express_mail_type / express_mail_track_num — quantity and dispatch details, including courier tracking.
• Effective fee columns — the NVL-derived delivery and document fees described above.
• fee_overridden_by / fee_overridden_date — audit trail for manual fee changes.
• Inclusion flags — incl_department, incl_field_of_stdy, incl_attend_mode, incl_yop_acad_prd, incl_awards, incl_acad_sessions, incl_hesa_num, incl_location, incl_program_type, and related flags control which academic data elements appear on the printed document.
• Hold and release flags — hold_release_of_final_grades, hold_degree_expected, hold_for_grade_chg, blocking dispatch until conditions are satisfied.
• Recipient columns — recip_pers_name, recip_inst_cd, recip_inst_name, the four address lines, and city, postal code, state, province, county, and country, plus fax details, forming the dispatch address block.
• comments / external_comments / internal_comments / special_instr — free-text handling notes.

Common Use Cases and Queries

The view is typically used to list outstanding or produced documents by type, to audit fee overrides, and to feed mail-merge or courier interfaces with recipient addresses and tracking data.

List document details for a given plan:

SELECT document_type,
       document_sub_type,
       num_of_copies,
       date_produced,
       item_status
FROM   apps.igs_as_doc_details_v
WHERE  plan_id = :p_plan_id;

Report documents of a specific type still awaiting dispatch, using the effective fee values:

SELECT plan_id,
       document_type,
       NVL(overridden_document_fee, doc_fee_per_copy) AS effective_fee,
       delivery_method_type,
       recip_pers_name
FROM   apps.igs_as_doc_details_v
WHERE  document_type = :p_document_type
AND    item_status = 'PENDING';

Audit fee overrides for remediation and financial reconciliation:

SELECT plan_id, document_type,
       delivery_fee, overridden_doc_delivery_fee,
       doc_fee_per_copy, overridden_document_fee,
       fee_overridden_by, fee_overridden_date
FROM   apps.igs_as_doc_details_v
WHERE  fee_overridden_date IS NOT NULL
ORDER BY fee_overridden_date DESC;

Within the EBS reporting environment the view can be registered as a custom data source, joined at the report level to IGS_AS_PLANS or person tables, since no such joins are baked into its definition.