Results for “oe_transaction_types_vl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OE_TRANSACTION_TYPES_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema in Oracle E-Business Suite. It belongs to the ONT (Order Management) product family and is documented in ETRM for releases 12.1.1 and 12.2.2. The view presents order transaction types for an operating unit (organization), joining translatable descriptive attributes with the transactional definition of each transaction type. Its name carries the "VL" suffix, the standard EBS convention indicating that the view returns the translation appropriate to the session's language, resolved at runtime through the USERENV('LANG') function. In practice, OE_TRANSACTION_TYPES_VL is the primary reference for order entry, fulfillment, and pricing logic that must display or evaluate a transaction type in the user's own language, and it is widely used in reports, concurrent programs, and integration extracts that need a human-readable transaction type name alongside its operational settings.

Underlying Base Objects

The ETRM metadata records two referenced base objects, both exposed to APPS as synonyms: OE_TRANSACTION_TYPES_SYN and OE_TRANSACTION_TYPES_TL. The view text confirms the join relationship. OE_TRANSACTION_TYPES_TL supplies the translatable columns — NAME and DESCRIPTION — and is joined to the transactional table on TRANSACTION_TYPE_ID, filtered by the condition T.LANGUAGE = USERENV('LANG'). OE_TRANSACTION_TYPES_SYN supplies the non-translatable, single-row-per-transaction-type definition, including identifiers, order category, date ranges, financial defaults, credit check rules, fulfillment defaults, and the DFF context and attribute columns. Because the join is on the transaction type identifier and the TL table is language-filtered, the view returns exactly one row per transaction type per session language, combining the operational record with its localized text.

Key Columns

• TRANSACTION_TYPE_ID / TRANSACTION_TYPE_CODE — Surrogate and user-facing identifiers for the transaction type; the former is the join key to the TL table.
• NAME / DESCRIPTION — Localized values sourced from OE_TRANSACTION_TYPES_TL, resolved to the session language.
• ORDER_CATEGORY_CODE — Classifies the transaction type, for example ORDER or RETURN, driving downstream order flow behavior.
• ORG_ID — Operating unit that owns the transaction type, central to multi-org reporting filters.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating used to restrict queries to currently active transaction types.
• Currency, pricing, and credit columns — CURRENCY_CODE, CONVERSION_TYPE_CODE, PRICE_LIST_ID, ENFORCE_LINE_PRICES_FLAG, and the ENTRY, SHIPPING, PICKING, and PACKING credit check rule identifiers.
• Fulfillment and shipping defaults — WAREHOUSE_ID, SHIPPING_METHOD_CODE, FREIGHT_TERMS_CODE, FOB_POINT_CODE, DEMAND_CLASS_CODE, and SHIP_SOURCE_TYPE_CODE.
• Invoicing and accounting defaults — INVOICING_RULE_ID, ACCOUNTING_RULE_ID, INVOICE_SOURCE_ID, CUST_TRX_TYPE_ID, and COST_OF_GOODS_SOLD_ACCOUNT.
• ATTRIBUTE1–ATTRIBUTE15 / CONTEXT — Descriptive flexfield segments carried through for extensibility.

Common Use Cases and Queries

Typical applications include order management reports that must print localized transaction type names, LOV-style validation, and integrations extracting order defaults such as warehouse, price list, and credit check rules. A standard query retrieves active transaction types for an operating unit:

SELECT transaction_type_id, transaction_type_code, name, order_category_code, start_date_active, end_date_active FROM oe_transaction_types_vl WHERE org_id = :p_org_id AND (end_date_active IS NULL OR end_date_active > SYSDATE) ORDER BY name;

The view can be joined to OE_ORDER_HEADERS_ALL on TRANSACTION_TYPE_ID to label existing orders, or to fulfillment and pricing setups to audit default derivation. Because the language filter is embedded in the view definition, no additional translation join is required; querying the view directly yields the correct localized NAME and DESCRIPTION for the connected user's session language.