Search Results oe_transaction_types_all

Overview

The OE_TRANSACTION_TYPES_ALL table is a core master data table within the Oracle E-Business Suite (EBS) Order Management (ONT) module, specifically in releases 12.1.1 and 12.2.2. It serves as the central repository for defining and storing all order and line transaction types used across the enterprise. These transaction types, often referred to as order types or line types, are critical templates that control the business rules, workflows, and defaulting behavior for sales orders, returns, and internal orders. The table supports multi-organization architecture, as indicated by the "_ALL" suffix, meaning it stores definitions that can be shared or specific to different operating units. It acts as a primary driver for order processing logic, linking order headers and lines to associated configurations in pricing, invoicing, shipping, and accounting.

Key Information Stored

The table's primary key is the TRANSACTION_TYPE_ID, a unique identifier for each transaction type definition. While the full column list is not exhaustively detailed in the provided metadata, the foreign key relationships reveal several critical columns that define a transaction type's behavior. These include TRANSACTION_TYPE_ID for self-referential relationships (e.g., default line types), NAME and DESCRIPTION for identification, and TYPE_CATEGORY to classify the transaction (e.g., ORDER, RETURN). Crucially, the table stores foreign keys to other master data entities, such as CURRENCY_CODE for the default currency, PRICE_LIST_ID for the default price list from QP_LIST_HEADERS_B, and CUST_TRX_TYPE_ID linking to the Receivables transaction type in RA_CUST_TRX_TYPES_ALL. It also holds references to rule IDs for accounting (ACCOUNTING_RULE_ID), invoicing (INVOICING_RULE_ID), and credit checks at entry and shipping phases, fundamentally shaping the order-to-cash lifecycle.

Common Use Cases and Queries

This table is central to setup, reporting, and data validation. A common use case is identifying the default configurations for a specific order type to troubleshoot pricing or invoicing issues. For reporting, analysts often join this table to order headers (OE_ORDER_HEADERS_ALL) or lines (OE_ORDER_LINES_ALL) to categorize and analyze order volumes by type. Implementation teams query it to audit setup consistency across operating units. A fundamental query pattern retrieves active transaction types with their key defaults:

• SELECT ott.name, ott.description, qpl.name default_price_list, rctt.name invoice_type
• FROM ont.oe_transaction_types_all ott,
• qp.qp_list_headers_b qpl,
• ar.ra_cust_trx_types_all rctt
• WHERE ott.price_list_id = qpl.list_header_id(+)
• AND ott.cust_trx_type_id = rctt.cust_trx_type_id(+)
• AND ott.org_id = :p_org_id;

Another critical use is tracing the lineage between an order line and its governing line type definition for debugging workflow or credit check rule execution.

Related Objects

OE_TRANSACTION_TYPES_ALL has extensive relationships with other EBS entities, as documented by its foreign keys. It is a parent table to core transactional tables: OE_ORDER_HEADERS_ALL (on ORDER_TYPE_ID) and OE_ORDER_LINES_ALL (on LINE_TYPE_ID). It references master data in other modules: RA_RULES (accounting/invoicing rules), RA_BATCH_SOURCES_ALL (invoice sources), QP_LIST_HEADERS_B (pricing), FND_CURRENCIES, and HR_ALL_ORGANIZATION_UNITS (warehouse). It also defines credit check rules via OE_CREDIT_CHECK_RULES and self-references to define default inbound and outbound line types. Furthermore, it integrates with localized solutions, as shown by references from Indian localization tables JAI_CMN_ST_FORM_DTLS, JAI_OM_OE_BOND_REG_DTLS, and JAI_OM_WSH_LINES_ALL. This network of relationships underscores its role as a pivotal hub connecting Order Management to Financials, Pricing, and Shipping execution.