Search Results oefv_sales_order_types




Overview
Explore in AI Chat

Overview

OEFV_SALES_ORDER_TYPES is an APPS-owned database view in the Oracle E-Business Suite Order Entry (OE) module. It presents a denormalized, reporting-friendly projection of the SO_ORDER_TYPES_ALL table—the transactional definition of sales order types—by joining it to the reference and master data required to render each coded attribute as a meaningful value. The view is defined with the "OEFV_" naming prefix characteristic of Oracle's Order Entry flexfield and inquiry views, and its documentation records a status of VALID and a description of "- Retrofitted," indicating it was carried forward from an earlier release lineage into the current 11i/12.x consolidated schema.

Within Oracle EBS 12.1.1 and 12.2.2, the view serves primarily as a read-only reporting and integration surface. Order management implementations, custom concurrent programs, and downstream interfaces use it to enumerate and describe the configured order types in a given operating unit without reproducing the multi-table join logic themselves. Because it resolves lookup codes and foreign keys into descriptive names, it is particularly useful for extracts, cross-reference reports, and data warehouse staging.

Underlying Base Objects

The view text is constructed over SO_ORDER_TYPES_ALL (aliased TYPE) as the driving table, joined to a set of reference and master tables. The documented metadata for the 12.2.2 release lists the referenced base objects as FND_CURRENCIES_TL, GL_CODE_COMBINATIONS, GL_DAILY_CONVERSION_TYPES, HR_ALL_ORGANIZATION_UNITS, MTL_PARAMETERS, OE_TRANSACTION_TYPES_ALL, OE_TRANSACTION_TYPES_TL, ORG_FREIGHT, QP_LIST_HEADERS_TL, and RA_RULES—all accessed through APPS synonyms. These objects supply currency names, accounting flexfield combinations, daily conversion types, organization names and codes, inventory parameters, price list headers, freight terms, and receivable rule names.

Note the historical provenance: the view text references SO_CYCLES, RA_RULES (joined twice, as ACCT_RULE and INV_RULE), SO_PRICE_LISTS, and GL_DAILY_CONVERSION_TYPES, while the 12.2.2 metadata maps these to the OE_TRANSACTION_TYPES_ALL/OE_TRANSACTION_TYPES_TL, QP_LIST_HEADERS_TL, and related synonyms as the product line evolved. The joins to RA_RULES for invoicing and accounting rules are outer joins, so order types without assigned rules are retained.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all active order types for an operating unit, verifying that invoicing and accounting rules are assigned, and reconciling order type definitions across environments. The query below retrieves the core descriptive and rule information:

  • SELECT order_type_id, name, description, order_category_code, inv_rule.name invoicing_rule, acct_rule.name accounting_rule FROM apps.oefv_sales_order_types;
  • To isolate a single order type by identifier: SELECT * FROM apps.oefv_sales_order_types WHERE order_type_id = :p_order_type_id;
  • For extract/reconciliation by organization: SELECT org_id, name, currency_code, price_list_id FROM apps.oefv_sales_order_types WHERE org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

Because it exposes resolved names rather than codes, the view is well suited to ad-hoc inquiry, BI Publisher data sources, and interface staging where human-readable values are required.