Search Results igs_as_order_hdr_v




Overview
Explore in AI Chat

Overview

IGS_AS_ORDER_HDR_V is a PL/SQL view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It presents document order header information used by the Academic Systems (AS) sub-module for ordering official documents such as transcripts, enrollment verification letters, and certification statements. The view consolidates header-level order attributes — student address, order status, payment and fee information, and delivery method — into a single denormalized result set suitable for forms, concurrent programs, and reporting tools.

The view is described as storing document order information: student address, order status, payment type, and related document request data. A single order can carry multiple associated documents, so the view operates at the order header grain, with line-level detail stored elsewhere. In EBS 12.1.1 and 12.2.2 the object is registered in the ETRM with status VALID and is exposed to the language-dependent lookup framework through FND_LOOKUP_VALUES.

Underlying Base Objects

The view is defined over four documented base objects:

The view also invokes the stored function IGS_AS_SS_DOC_REQUEST.IS_ORDER_DEL_ALWD(HDR.ORDER_NUMBER) to expose a derived deletion-permission indicator. All joins are language-aware, meaning results are returned in the session's current language.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting outstanding transcript orders, reconciling document fees against invoices, and driving the Student System order inquiry form. A simple status report:

  • SELECT order_number, order_status_desc, person_id, city, country_desc, order_fee FROM igs_as_order_hdr_v WHERE order_status = 'PENDING';
  • Joining to line-level tables via ORDER_NUMBER to enumerate documents within an order.
  • Filtering by INVOICE_ID to trace orders against AR transactions.

Because the view is language-sensitive and relies on FND lookups, queries should be run in an appropriately configured session; the underlying joins will otherwise return null decoded values.