Search Results submit_method




Overview
Explore in AI Chat

Overview

IGSBV_AS_DOCUMENT_ORDERS is a read-only Oracle EBS view owned by the APPS schema that exposes order header data from the Advanced Supply / Order Management context, specifically sourced from the IGS_AS_ORDER_HDR table. The "BV" naming convention indicates a business view intended for reporting and integration consumption rather than transactional data entry, and the view is defined with the WITH READ ONLY clause, confirming it cannot be used for DML operations. The view presents a horizontally oriented, denormalized snapshot of an order's descriptive, address, contact, fee, and submission attributes, making it suitable for extraction into reporting layers, document generation engines, and integration staging areas. Because it is owned by APPS and carries no documented dependencies beyond its base table, it functions as a stable abstraction layer that shields downstream consumers from the physical column layout of IGS_AS_ORDER_HDR.

Underlying Base Objects

The ETRM metadata documents the view as selecting exclusively from IGS_AS_ORDER_HDR, filtered by no predicates and constrained only by the WITH READ ONLY directive. No other base tables are referenced, meaning the view performs a straight projection of columns with no joins. Two columns are not physical values but synthetic Lookup substitution expressions: the first, positioned after ORDER_DESCRIPTION, resolves the ORDER_STATUS through the lookup type IGS_AS_ORDER_STATUS, and the second, positioned before SUBMIT_METHOD, resolves REQUEST_TYPE through IGS_AS_DOC_REQTYPE. These embedded lookup strings follow the EBS descriptive-flexfield-style substitution convention, meaning the raw stored code is translated to its human-readable MEANING at query time. The absence of documented referencing objects indicates the view is a leaf consumer of IGS_AS_ORDER_HDR rather than a dependency for other database objects.

Key Columns

Common Use Cases and Queries

Typical usage centers on order reporting, submission-channel analysis, and document generation. Because SUBMIT_METHOD is exposed directly, one frequent pattern groups orders by submission channel and status.

SELECT ORDER_NUMBER, SUBMIT_METHOD, ORDER_STATUS, REQUEST_TYPE, DATE_COMPLETED
FROM APPS.IGSBV_AS_DOCUMENT_ORDERS
WHERE SUBMIT_METHOD = :p_submit_method;

A second pattern extracts contact and addressing data for notification or fulfillment documents, joining to PER_ALL_PEOPLE_F on PERSON_ID where person details are required. A third pattern performs financial reconciliation using ORDER_FEE, DELIVERY_FEE, and INVOICE_ID. Because the view is read-only and unjoined, queries are inexpensive; filtering predicates should be applied on ORDER_NUMBER, PERSON_ID, or ORDER_STATUS to limit result sets. Consumers should treat the lookup-derived columns as display values rather than codes, since they return MEANING text from IGS_LOOKUP_VALUES.