Search Results date_completed

Overview

IGSBV_AS_DOCUMENT_ORDERS is a read-only reporting view within the Oracle E-Business Suite Student System (IGS) module, which is classified as obsolete in release 12.1.1 and 12.2.2. The view presents order-level information for academic documents requested by or on behalf of students, specifically transcripts and enrollment certificates. Its purpose is to consolidate order header data with requester contact details, fee amounts, delivery information, and lookup-decoded status values into a single denormalized result set suitable for operational reporting, inquiry screens, or downstream integration.

The view is defined with a WITH READ ONLY clause, meaning no DML operations are permitted against it. It draws all of its data from the IGS_AS_ORDER_HDR table and performs no joins in its documented definition. Lookup values for order status and request type are not resolved through SQL joins but are instead expressed using Oracle Forms-style bind references (the "_LA:" prefix), which indicates the view was originally designed for consumption by an Oracle Forms or OA Framework-based user interface rather than purely for SQL*Plus or BI Publisher use.

Underlying Base Objects

The view is constructed exclusively over the base table IGS_AS_ORDER_HDR, which stores order header records for academic document requests. No other base tables, views, or synonyms are documented as referenced objects. Because the definition contains no joins, the view is a straightforward projection: every row in IGS_AS_ORDER_HDR maps to one row in the view, subject to the column list and any row-level restrictions implicit in the underlying table.

The ETRM metadata notes that the object is "Not implemented in this database," which is consistent with the obsolete status of the IGS Student System module. Organizations running 12.1.1 or 12.2.2 should not assume this view exists in their instance unless the legacy Student System product was explicitly installed and the relevant patch level applied.

Key Columns

• ORDER_NUMBER / ORDER_DESCRIPTION — Identifiers and free-text description of the document order; ORDER_DESCRIPTION is the column most often searched in an attempt to identify a specific request or its purpose.
• _LA:ORDER_STATUS — A decoded reference to IGS_LOOKUP_VALUES for lookup type IGS_AS_ORDER_STATUS, returning the MEANING of the status code.
• _LA:REQUEST_TYPE — A decoded reference to IGS_LOOKUP_VALUES for lookup type IGS_AS_DOC_REQTYPE, distinguishing transcript versus enrollment certificate requests.
• DATE_COMPLETED, SUBMIT_METHOD, ORDER_PLACED_BY — Processing and submission attributes of the order.
• ADDR_LINE_1 through POSTAL_CODE — The requester or delivery address block.
• EMAIL_ADDRESS, PHONE_* , FAX_* — Contact details for the requester or designated recipient.
• DELIVERY_FEE, ORDER_FEE, INVOICE_ID — Financial attributes linking the order to charges and its AR invoice.
• PERSON_ID — The person (student or requester) associated with the order.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns.

Common Use Cases and Queries

Typical usage centers on order tracking and reconciliation. A user searching for a particular "order_description" would query the view to locate matching transcript or enrollment certificate orders and inspect their status, fees, and delivery details:

• Locating orders by description: SELECT order_number, order_description, order_status, date_completed FROM igsbv_as_document_orders WHERE UPPER(order_description) LIKE UPPER('%&keyword%');
• Listing outstanding orders: SELECT order_number, order_placed_by, order_status FROM igsbv_as_document_orders WHERE date_completed IS NULL;
• Fee analysis by request type: SELECT request_type, COUNT(*), SUM(order_fee + delivery_fee) FROM igsbv_as_document_orders GROUP BY request_type;
• Invoicing reconciliation: SELECT order_number, invoice_id, order_fee FROM igsbv_as_document_orders WHERE invoice_id IS NOT NULL;

Because the view is read-only and appears to be intended for Forms-based rendering of bind variables, BI Publisher or SQL-only environments may need to substitute explicit joins to FND_LOOKUP_VALUES (or IGS_LOOKUP_VALUES) for the "_LA:" pseudo-columns.