Search Results igs_as_order_status




Overview
Explore in AI Chat

Overview

The view APPS.IGS_AS_ORDER_HDR_V is a reporting and inquiry construct within the Oracle E-Business Suite Student Information / Student Systems (IGS) product family. It exposes the header-level content of document or service orders captured by the IGS Administrative Services (AS) module, presenting the stored order record in a denormalized, display-ready form. Rather than forcing a report, concurrent program, or integration routine to join transactional tables with lookup, territory, and party tables on every execution, the view resolves the descriptive meaning values at query time. It is therefore most frequently consumed by Oracle Reports, OAF pages, BI Publisher data templates, and custom SQL used for order tracking and operational monitoring.

The presence of the ROWID of the underlying header table as the first selected column indicates the view is key-preserved with respect to IGS_AS_ORDER_HDR, so it may also be used as the target of DML and as a base for further updatable views.

Underlying Base Objects

The view is defined over five documented objects: IGS_AS_ORDER_HDR, FND_TERRITORIES_TL, FND_LOOKUP_VALUES (joined twice), and HZ_PARTIES.

  • IGS_AS_ORDER_HDR is the driving table and supplies the order number, status code, address, contact, fee, and audit columns.
  • FND_TERRITORIES_TL supplies the translated territory short name, joined on country = territory_code filtered by the session language.
  • FND_LOOKUP_VALUES is joined twice: lk resolves the order status meaning from lookup type IGS_AS_ORDER_STATUS, answering the user's search for igs_as_order_status; lk2 resolves the request type meaning from IGS_AS_DOC_REQTYPE via an outer join.
  • HZ_PARTIES provides the ordered-by party name through an outer join on order_placed_by = party_id.
  • The view also invokes the packaged function IGS_AS_SS_DOC_REQUEST.IS_ORDER_DEL_ALWD(order_number) to derive the is_order_del_alwd indicator.

Key Columns

  • order_number, order_status, and meaning — the order identifier and its decoded status description.
  • date_completed, creation_date, and audit columns (created_by, last_updated_by, last_update_date, program_id, request_id) — lifecycle and traceability information.
  • Address block (addr_line_1–addr_line_4, city, state, province, county, country, postal_code, territory_short_name) — delivery location details.
  • Contact block (person_id, email_address, phone_*, fax_*) — recipient communication data.
  • delivery_fee, order_fee, request_type with its decoded meaning, and submit_method — commercial and routing attributes.
  • order_placed_by, party_name, order_description, is_order_del_alwd — requester identification and operational control flags.

Common Use Cases and Queries

Typical consumers include customer service inquiries, fulfillment backlog reporting, and status dashboards. A representative query filters on the decoded status meaning and sorts by completion date:

  • SELECT order_number, meaning, date_completed, party_name FROM apps.igs_as_order_hdr_v WHERE meaning = 'Completed' ORDER BY date_completed DESC;
  • SELECT order_number, request_type, is_order_del_alwd FROM apps.igs_as_order_hdr_v WHERE order_status = 'NEW';
  • SELECT party_name, COUNT(*) FROM apps.igs_as_order_hdr_v GROUP BY party_name;

Because the view is key-preserved, it can also support updates to order header attributes where security and business rules permit.