Results for “oe_order_types_115_all”

20 results




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

Overview

OE_ORDER_TYPES_115_ALL is a compatibility view owned by the APPS schema in Oracle E-Business Suite, defined within the Order Management (ONT) product family. Its defining purpose is the preservation of backward compatibility with the Oracle EBS 11.5.x data model, in which order types were stored in a single, wide table (OE_ORDER_TYPES_ALL). Beginning with Release 12, order types and order lines were separated into distinct transaction type entities, and the legacy table was reorganized into OE_TRANSACTION_TYPES_ALL and its translation table. The view name itself carries the "115" suffix to denote its origin as an 11.5-compatible interface.

The ETRM documentation explicitly states that this view is "No longer used." It exposes only a small subset of the legacy columns as live data; the remaining attributes are projected as literal NULLs. Because the legacy structure was never intended to carry shipping-related credit checking logic at the order type level, the SHIPPING_CREDIT_CHECK_RULE_ID column is defined as NULL. Consequently, users searching for shipping_credit_check_rule_id through this view will not retrieve meaningful values. The view remains valid for syntax compatibility but is not a supported source for reporting or integration in 12.1.1 or 12.2.2.

Underlying Base Objects

According to the documented view metadata, OE_ORDER_TYPES_115_ALL is defined over two referenced base objects, both exposed as synonyms in the APPS schema:

  • OE_TRANSACTION_TYPES_ALL — the master (non-translated) transaction type definition table, aliased here as A and joined on TRANSACTION_TYPE_ID.
  • OE_TRANSACTION_TYPES_TL — the translation table, aliased as T, supplying the language-specific NAME and DESCRIPTION columns.

The view text performs an inner join between A.TRANSACTION_TYPE_ID and T.TRANSACTION_TYPE_ID, meaning a row is returned only where a translation record exists. The legacy identifier ORDER_TYPE_ID is mapped from A.TRANSACTION_TYPE_ID, and the ORDER_CATEGORY_CODE is derived through a DECODE that converts internal category codes to the legacy values 'R' (Order), 'RMA' (Return), and NULL for MIXED or unmapped categories. All audit columns, flags, context fields, and attribute columns from the original 11.5 structure are projected as NULL placeholders, confirming that the view is a structural shell rather than a functional data source.

Key Columns

The columns that actually carry data in this view are limited to the following:

  • TRANSACTION_TYPE_ID / ORDER_TYPE_ID — the unique identifier of the transaction type, sourced from OE_TRANSACTION_TYPES_ALL.
  • NAME and DESCRIPTION — the translated display name and description of the order type.
  • PRICE_LIST_ID — the default price list associated with the order type.
  • ACCOUNTING_RULE_ID and COST_OF_GOODS_SOLD_ACCOUNT — the accounting rule and COGS account reference.
  • ENTRY_CREDIT_CHECK_RULE_ID — the credit check rule applied at order entry.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the active date range of the order type.
  • ORDER_CATEGORY_CODE — derived legacy category ('R', 'RMA', or NULL).
  • ORG_ID — the operating unit identifier for multi-org filtering.

Notably, SHIPPING_CREDIT_CHECK_RULE_ID is explicitly hard-coded as NULL in the view definition. Any query filtering or selecting this column returns no usable data, and credit check rules for shipping are not maintained at the order type level in this view.

Common Use Cases and Queries

Given its deprecated status, this view is generally encountered only in legacy SQL that has not been migrated to the R12 transaction type model. A typical compatibility query retrieves order type names and categories for an operating unit:

  • SELECT order_type_id, name, order_category_code FROM oe_order_types_115_all WHERE org_id = :p_org_id AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE+1);
  • Validating whether a legacy credit check rule reference exists — this will always return NULL for shipping_credit_check_rule_id, confirming that migration to OE_TRANSACTION_TYPES_ALL or the Order Management transaction type setup is required.

For current development and reporting, Oracle recommends querying OE_TRANSACTION_TYPES_ALL and OE_TRANSACTION_TYPES_TL directly. The 115_ALL view should be treated strictly as a compatibility artifact and excluded from new customizations.