Search Results source_order_number

Overview

OEFV_SALES_ORDERS is a retrofitted Oracle Order Entry (OE) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents a flattened, user-readable projection of sales order header information. The "OEFV" prefix denotes an Order Entry Foundation View, and the "_FV" convention indicates this object was originally built for the Oracle EBS Forms-based (10g/Java) user interface rather than for direct use in reports or interfaces. In practice, the view is used as a descriptive reference for sales order headers, exposing denormalized lookup meanings and joined descriptive fields that would otherwise require extensive joins across the SO_HEADERS, SO_LOOKUPS, and contact-related tables.

Because the view carries the label "Retrofitted," it is important to understand that its definition has been adapted for the newer EBS release. The ETRM record for this object states "Not implemented in this database," meaning that in the specific environment catalogued, no physical instantiation of OEFV_SALES_ORDERS exists at runtime; the definition is retained for documentation and migration purposes. The user search term "source_order_number" corresponds directly to the column SRC_HEADER.ORDER_NUMBER, which the view exposes as a source order reference—typically used to link internal orders to externally sourced or referenced orders.

Underlying Base Objects

The documented ETRM metadata lists no explicitly named base objects for OEFV_SALES_ORDERS. However, the view text reveals its effective dependency set. The primary driving table is the order header table, aliased HEADER (OE_ORDER_HEADERS_ALL), which provides the bulk of the columns. Descriptive joins are made to:

• ORDER_TYPE (OE_ORDER_TYPES) for the order type name
• ORDER_CYCLE (OE_ORDER_CYCLES) for the cycle name
• SALESREP and CUSTOMER for salesperson and customer names
• AGREEMENT for agreement names
• ORD_BY_CONTACT, INV_TO_CONTACT, SHIP_TO_CONTACT and the INV_TO_SITE, SHIP_TO_SITE location records for contact and address information
• INV_ORG, INV_RULE, ACCNT_RULE, PAYTERMS, PRICE_LIST, and CURRENCY for organizational, rule, and financial descriptors
• SRC_HEADER, a self-reference to the order headers table, which supplies the source order number
• GCT for conversion type, plus various lookup joins driven by the _LA (lookup attribute) and _DF (descriptive flexfield) tags embedded in the SQL

The embedded _LA tokens instruct the Forms runtime to resolve coded values into their user-facing meanings via SO_LOOKUPS, AR_LOOKUPS, and FND_COMMON_LOOKUPS. The _DF token references the SO_HEADERS descriptive flexfield context.

Key Columns

Notable columns exposed by the view include:

• ORDER_NUMBER — the sales order number (HEADER.ORDER_NUMBER)
• SRC_HEADER.ORDER_NUMBER — the source order number, relevant to the user's search
• ORIGINAL_SYSTEM_REFERENCE — reference to the originating external system
• DATE_ORDERED, DATE_REQUESTED_CURRENT — order and requested dates
• PURCHASE_ORDER_NUM — customer purchase order reference
• CONVERSION_RATE, CONVERSION_DATE, USER_CONVERSION_TYPE — currency conversion details
• Lookup-meanings for flags such as SHIP_PARTIAL_FLAG, OPEN_FLAG, CANCELLED_FLAG, TAX_EXEMPT_FLAG, ORDER_CATEGORY, DEMAND_CLASS_CODE, SHIPMENT_PRIORITY_CODE, FREIGHT_TERMS_CODE, and FOB_CODE
• Descriptive names for order type, cycle, salesrep, customer, agreement, invoice-to and ship-to contacts and locations, inventory organization, invoicing rule, accounting rule, payment terms, price list, and currency
• Foreign-key columns such as HEADER_ID, ORDER_TYPE_ID, CYCLE_ID, SALESREP_ID, CUSTOMER_ID, AGREEMENT_ID, and the various contact and site-use identifiers

Common Use Cases and Queries

Typical usage involves retrieving a readable header record for a sales order or tracing the relationship between an order and its source order number. A representative query follows:

SELECT ORDER_NUMBER, ORDER_TYPE_NAME, ORIGINAL_SYSTEM_REFERENCE, PURCHASE_ORDER_NUM, OPEN_FLAG, ORDER_CATEGORY FROM OEFV_SALES_ORDERS WHERE SRC_HEADER.ORDER_NUMBER = :p_source_order_number;

Note that since the ETRM documentation marks this view as "Not implemented in this database," integrators should verify availability before relying on it, and may instead query OE_ORDER_HEADERS_ALL joined to OE_LOOKUPS and related tables where a directly supported object is required. The view remains a useful navigational reference for understanding the header-level data model in the OE module.