Search Results so_order_sources

Overview

The view SO_HEADERS_RMA_V is an Oracle Order Entry (OE) object that exposes the header-level attributes of return merchandise authorization (RMA) sales orders within Oracle E-Business Suite. It is a denormalized read-only projection over the order headers entity, presenting the columns that define an RMA order's identity, status, customer, shipping, pricing, and descriptive-flexfield context in a single queryable structure. The object is documented in ETRM for both 12.1.1 and 12.2.2, which indicates that it is a stable part of the Order Management data model across these releases.

In EBS 12.1.1 and 12.2.2, RMA headers are stored physically in the OE_ORDER_HEADERS_ALL table and its associated interface and translated tables. This view provides a presentation or interface layer that surfaces the RMA-relevant subset of those columns, allowing reports, concurrent programs, and integration extracts to read RMA headers without joining across the full order header schema. Its role is therefore primarily reporting and inbound/outbound integration: it is a projection, not a transaction table, and should be treated as read-only in custom development.

Underlying Base Objects

The ETRM metadata for this view documents no referenced base objects and explicitly records the implementation status as "Not implemented in this database." This status means the view is shipped as part of the Oracle EBS schema but may not be instantiated in every environment, or is intended for reference only in the documented release. The view text, however, is a SELECT statement over a header table alias H, from which all columns are projected. In standard EBS architecture that alias corresponds to OE_ORDER_HEADERS_ALL, the master table for order and RMA headers. Because the metadata lists no base objects, the exact underlying object should be verified in each deployed instance by querying ALL_VIEWS and ALL_DEPENDENCIES for the view name before relying on it in custom code.

Key Columns

The view projects the full header column set, with several categories of particular importance:

• Identity and status: HEADER_ID, ORDER_NUMBER, ORDER_CATEGORY, ORIGINAL_SYSTEM_SOURCE_CODE, ORIGINAL_SYSTEM_REFERENCE, SOURCE_HEADER_ID, ORDER_TYPE_ID, CYCLE_ID, OPEN_FLAG, CANCELLED_FLAG.
• Customer and contacts: CUSTOMER_ID, ORDERED_BY_CONTACT_ID, SHIP_TO_SITE_USE_ID, SHIP_TO_CONTACT_ID, INVOICE_TO_SITE_USE_ID, INVOICE_TO_CONTACT_ID.
• Dates and priority: DATE_ORDERED, DATE_REQUESTED_CURRENT, SHIPMENT_PRIORITY_CODE.
• Shipping and logistics: SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, FOB_CODE, WAREHOUSE_ID, SHIPPING_INSTRUCTIONS, PACKING_INSTRUCTIONS.
• Commercial terms: FREIGHT_TERMS_CODE is the column most relevant to the user's search term "freight_terms_name." That descriptive name is not stored on the header; it is resolved by joining FREIGHT_TERMS_CODE to the FND lookup values (lookup type FREIGHT_TERMS) or to the freight terms reference. Similarly, TERMS_ID, PRICE_LIST_ID, CURRENCY_CODE, CONVERSION_TYPE_CODE, CONVERSION_RATE, and SALES_CHANNEL_CODE carry the commercial context.
• Flexfield and audit columns: the pervasive _SVRID columns (DATE_SVRID, ENTRY_STATUS_SVRID, CUSTOMER_SVRID, FREIGHT_TERMS_SVRID, etc.) support descriptive flexfield and seed/versioning logic, and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) provide auditability.

Common Use Cases and Queries

Typical usage includes RMA reporting, order-status dashboards, and integration extracts to external systems. Because freight terms are stored as a code, resolving the name requires a lookup join. A sample query illustrating the freight terms resolution follows:

• SELECT h.order_number, h.freight_terms_code, fv.meaning AS freight_terms_name, h.date_ordered, h.open_flag FROM so_headers_rma_v h, fnd_lookup_values_vl fv WHERE fv.lookup_type = 'FREIGHT_TERMS' AND fv.lookup_code = h.freight_terms_code AND fv.language = USERENV('LANG');
• To list open RMAs by customer: SELECT order_number, customer_id, order_category, date_ordered FROM so_headers_rma_v WHERE open_flag = 'Y' AND cancelled_flag = 'N';
• To join RMAs to their lines for detail reporting, relate HEADER_ID to the order line table's HEADER_ID.

Because the view is documented as not implemented in the reference database, developers should confirm its presence and column list in the target instance, and prefer direct access to OE_ORDER_HEADERS_ALL when guaranteed availability is required.