Search Results order_category_code




Overview
Explore in AI Chat

Overview

The OE_ORDER_TYPES_115 view is a compatibility object owned by the APPS schema within the Oracle Order Management (ONT) module. Its documented status is VALID, and it is explicitly described in the Oracle E-Business Suite data dictionary as "No longer used." The view exists primarily to preserve backward compatibility with customizations, reports, and integration interfaces that were originally authored against an earlier release of the Order Management data model, specifically the 11.5.x lineage from which the "_115" suffix derives.

Functionally, the view presents a vertically restricted projection of order transaction type definitions. Rather than exposing the full attribute set maintained by the Order Management transaction type setup, it deliberately returns NULL for the majority of columns and populates only a curated subset, including NAME, PRICE_LIST_ID, ACCOUNTING_RULE_ID, COST_OF_GOODS_SOLD_ACCOUNT, and ENTRY_CREDIT_CHECK_RULE_ID. This design reflects the evolutionary divergence of the OE_ORDER_TYPES and OE_TRANSACTION_TYPES data models; the view acts as a stabilizing shim so that legacy SQL referencing the old column list continues to compile and return a result set without modification. Reporting and integration logic that depends on this view should be regarded as technically obsolete and a candidate for migration to OE_TRANSACTION_TYPES_VL or its associated _B and _TL tables.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: OE_TRANSACTION_TYPES_VL, itself a view in the APPS schema. This identifies OE_ORDER_TYPES_115 as a level-two derivation — a view defined over another view rather than directly over physical base tables.

OE_TRANSACTION_TYPES_VL is the translated (VL) layer of the transaction types entity and, in the standard multi-language architecture, resolves joins between OE_TRANSACTION_TYPES_B (the base, language-independent table) and OE_TRANSACTION_TYPES_TL (the translation table storing language-specific NAME and DESCRIPTION values). Selecting through OE_ORDER_TYPES_115 therefore traverses three layers: the 115 compatibility view, the VL translation view, and the underlying _B and _TL physical tables.

The projection applies a DECODE on ORDER_CATEGORY_CODE, translating source values of 'ORDER' to 'R', 'RETURN' to 'RMA', and 'MIXED' to NULL, while passing ORG_ID through unmodified. Because the view suppresses creation and audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID, and others) by hardcoding TO_DATE(NULL) or NULL, it cannot support audit-trail analysis, concurrent program lineage, or change-history reporting. It is strictly a read projection for value lookup.

Key Columns

  • TRANSACTION_TYPE_ID — Surfaced with an inline comment aliasing it as ORDER_TYPE_ID, preserving the legacy column name expected by pre-existing code. This is the primary identifier and the natural join key to OE_TRANSACTION_TYPES_VL.
  • NAME — The user-defined transaction type name, sourced from the translation layer and therefore subject to the session language.
  • ENTRY_CREDIT_CHECK_RULE_ID — The credit check rule applied at order entry, the column of principal interest given the originating search. It references the credit checking rule configuration used to evaluate customer exposure when an order is booked.
  • ACCOUNTING_RULE_ID — Identifies the accounting rule governing revenue recognition for the transaction type.
  • PRICE_LIST_ID — The default price list associated with the transaction type.
  • COST_OF_GOODS_SOLD_ACCOUNT — The general ledger account used for cost of goods sold postings.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — The effective date range for the transaction type.
  • ORDER_CATEGORY_CODE — Transformed via DECODE to the legacy domain of 'R', 'RMA', or NULL.
  • ORG_ID — The operating unit identifier, supporting multi-org filtered queries.

Notably, SHIPPING_CREDIT_CHECK_RULE_ID is present in the view text but returns NULL, so credit rule analysis restricted to this view covers entry-level checking only.

Common Use Cases and Queries

The dominant use case is resolving the credit check rule bound to a transaction type, typically to audit or reproduce order-entry credit behavior. A representative query is:

  • SELECT transaction_type_id, name, entry_credit_check_rule_id FROM oe_order_types_115 WHERE org_id = :org_id;
  • SELECT t.name, t.entry_credit_check_rule_id, t.accounting_rule_id FROM oe_order_types_115 t WHERE t.transaction_type_id = :type_id;
  • SELECT transaction_type_id, name, order_category_code FROM oe_order_types_115 WHERE order_category_code = 'RMA' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

These patterns appear in custom concurrent programs, Oracle Reports, and interface staging queries inherited from 11.5.x implementations. Because the view is documented as no longer used, new development should query OE_TRANSACTION_TYPES_VL directly, joining to OE_CREDIT_CHECK_RULES on ENTRY_CREDIT_CHECK_RULE_ID, to obtain current data with full column and audit coverage.