Search Results invoice_description

Overview

IGSFV_AS_DOCUMENT_ORDERS is a read-only view owned by the APPS schema within the Oracle E-Business Suite IGS (Student System) product family. It exposes the orders that have been placed for student-facing documents, specifically transcripts and enrollment certificates. In the EBS 12.1.1 and 12.2.2 architectures, this view serves as a reporting and integration surface that consolidates order header information, party identification data, and the associated receivable invoice details into a single flattened record set. Rather than requiring report authors, concurrent programs, or downstream interfaces to join the order base table against the party and invoice tables independently, the view performs those joins centrally, reducing the risk of inconsistent join logic across consuming components.

The object carries a status of VALID in the ETRM repository. It is defined with a WITH READ ONLY clause, confirming that it is intended strictly for query access and cannot be used as a DML target.

Underlying Base Objects

According to the documented view text, IGSFV_AS_DOCUMENT_ORDERS is constructed from four base objects joined in a single SELECT statement:

• IGS_AS_ORDER_HDR (alias OHDR) — the driving table, holding the order header for transcript and enrollment certificate requests. All outer-joined references originate from this alias.
• HZ_PARTIES (alias HP1) — joined on OHDR.PERSON_ID = HP1.PARTY_ID to resolve the person for whom the document order was placed.
• HZ_PARTIES (alias HP2) — an outer join on OHDR.ORDER_PLACED_BY = HP2.PARTY_ID (+) to resolve the party who placed the order, when that differs from the subject person.
• IGS_FI_INV_INT_ALL (alias INVI) — an outer join on OHDR.INVOICE_ID = INVI.INVOICE_ID (+), supplying the invoice number and description tied to the order's fees.

The two outer joins ensure that orders without a designated placing party, or without a generated invoice, are still returned rather than being filtered out.

Key Columns

The view exposes several logical columns created through descriptive flexfield lookup translation, indicated by the "_LA:" prefix naming convention:

• "_LA:ORDER_STATUS" — decoded from IGS_LOOKUP_VALUES using the IGS_AS_ORDER_STATUS lookup type, returning the MEANING of the order status.
• "_LA:REQUEST_TYPE" — decoded from the IGS_AS_DOC_REQTYPE lookup type, indicating whether the order concerns a transcript or an enrollment certificate.
• ORDER_NUMBER, ORDER_DESCRIPTION, DATE_COMPLETED — core order identity and lifecycle attributes.
• DELIVERY_FEE, ORDER_FEE — the monetary amounts associated with fulfillment and the order itself.
• PERSON_NAME, PERSON_NUMBER — the party receiving the document, sourced from HP1.
• ORDER_PLACED_BY_NAME, ORDER_PLACED_BY_NUMBER — the party placing the order, sourced from HP2 where available.
• INVOICE_NUMBER, INVOICE_DESCRIPTION — pulled from IGS_FI_INV_INT_ALL, directly relevant when reporting on the invoice narrative associated with a document order.
• Address and contact columns — ADDR_LINE_1 through POSTAL_CODE, plus email, phone, and fax components, supplying delivery information.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

The most frequent usage is reporting on transcript and certificate order volumes, fees collected, and their linkage to invoices. Because the view joins invoice data directly, it is the natural source for reconciliation queries between document orders and receivables.

To list orders with their invoice descriptions:

SELECT order_number, order_description, request_type,
       invoice_number, invoice_description, order_fee
FROM   apps.igsfv_as_document_orders
WHERE  invoice_description IS NOT NULL;

To summarize fee totals by request type and status:

SELECT request_type, order_status,
       SUM(order_fee) AS total_fee, COUNT(*) AS order_count
FROM   apps.igsfv_as_document_orders
GROUP  BY request_type, order_status;

To identify orders placed on behalf of a person by a third party:

SELECT order_number, person_name, order_placed_by_name,
       date_completed
FROM   apps.igsfv_as_document_orders
WHERE  person_id <> order_placed_by;

All queries execute with the read-only semantics defined by the view, making it safe for use in concurrent programs, BI Publisher data templates, and ad hoc reporting.