Search Results oe_transaction_types_syn




Overview
Explore in AI Chat

Overview

APPS.OEBV_SALES_ORDER_TYPES is a read-only reporting view shipped with Oracle E-Business Suite Release 12.1.1 and 12.2.2 as part of the Order Management (ONT) module. It exposes the master definition of sales order transaction types — the configurable categories such as "Mixed Order," "Standard Order," or "Return with Credit" — that govern how order lines behave throughout the order-to-cash lifecycle. Each row represents one order type for a specific operating unit (ORG_ID), combining the translatable descriptive attributes with the control flags, pricing defaults, and accounting options defined for that type.

The view is primarily consumed by reporting, integration, and localization layers. The Oracle ETRM metadata shows that many columns are not raw values but seeded lookup resolution expressions (the "_LA:" prefixed entries), where coded values are translated into their display meanings from OE_LOOKUPS, AR_LOOKUPS, or QP_LOOKUPS. This makes the view particularly useful for external extracts, OBIEE / BI Publisher reports, and interfaces that require human-readable order type attributes rather than internal codes.

Underlying Base Objects

Per the documented metadata, the view is defined over two referenced base objects, both exposed through synonyms in the APPS schema:

The join is on TRANSACTION_TYPE_ID, with a language filter of T.LANGUAGE = userenv('LANG'), so only the translation matching the caller's session language is returned. This correlation to the user's search term "oe_transaction_types_syn" is direct: the view's FROM clause explicitly references OE_TRANSACTION_TYPES_SYN, making it the primary base-table synonym behind OEBV_SALES_ORDER_TYPES.

Key Columns

The exposed columns fall into three functional groups:

The '_DF:ONT:OE_ORDER_TYPES:B' entry is a descriptive flexfield marker, indicating that DFF segments defined on OE_ORDER_TYPES_B are surfaced through this view.

Common Use Cases and Queries

The view is typically used to:
• Drive LOVs or cross-reference extracts of valid sales order types per operating unit.
• Feed BI Publisher / OBIEE reports needing lookup-translated order type attributes.
• Support integration mappings between EBS and external order capture systems.

A basic query scoped to an operating unit:

  • SELECT name, description, order_category_code, currency_code, price_list_id
  • FROM apps.oebv_sales_order_types
  • WHERE org_id = :p_org_id
  • AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

Because ORG_ID is included and the view applies organization-based security ('_SEC:B.ORG_ID'), results are automatically restricted to the operating units the querying responsibility may access. The view is defined WITH READ ONLY and should never be used for DML — inserts and updates must target OE_TRANSACTION_TYPES_B and _TL directly.