Results for “oe_transaction_types_all”

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

Overview

OE_TRANSACTION_TYPES_ALL is a core Order Management (ONT) setup and reference table in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the ONT schema and stores the definition of every order and line transaction type available to Order Management. Each row represents an order type (for example, a standard sales order, a return, or a mixed order) or a line type (for example, a standard line, a return line, or a service line). Transaction types are the linchpin of order entry, since OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL both reference this table to determine how an order or line behaves throughout its lifecycle — pricing, credit checking, shipping, invoicing, and accounting.

Transaction types drive Oracle Order Management defaulting rules. They dictate order category (order versus line), order routing through workflow, default warehouse and shipping attributes, invoicing and accounting rules, price lists, and whether constraints such as credit checks, purchase order requirements, and scheduling are enforced. The table additionally holds key descriptive flexfield context columns and the standard WHO audit columns.

From a Data Vault modeling perspective, the ETRM relationship metadata classifies this object as satellite-leaning. In practical terms, it functions as a reference or "type" entity that would typically be modeled as a hub (or reference table) keyed on TRANSACTION_TYPE_ID, with descriptive behavior attributes attached as satellite content. Because the table already includes self-referencing foreign keys and denormalized order-level defaults, it is best treated as a central reference dimension from which transactional satellites (orders and lines) draw their type context.

Key Information Stored

The table contains 73 documented columns. The most consequential are listed below. The surrogate primary key is TRANSACTION_TYPE_ID (backed by OE_TRANSACTION_TYPES_ALL_PK and the unique index OE_TRANSACTION_TYPES_ALL_U1). Business-key candidates include TRANSACTION_TYPE_CODE, which uniquely identifies a type within its category, and ORDER_CATEGORY_CODE, which distinguishes an order type from a line type.

• TRANSACTION_TYPE_ID — surrogate primary key and the value referenced by all order and line records.
• TRANSACTION_TYPE_CODE — user-facing short code for the type (a documented unique business key).
• ORDER_CATEGORY_CODE — determines whether the record describes an order type or a line type.
• START_DATE_ACTIVE / END_DATE_ACTIVE — active date range controlling when a type is available for entry.
• CURRENCY_CODE — default transaction currency (FK to FND_CURRENCIES).
• CUST_TRX_TYPE_ID — default receivables transaction type (FK to RA_CUST_TRX_TYPES_ALL).
• INVOICING_RULE_ID / ACCOUNTING_RULE_ID — rules determining invoice and revenue recognition timing (FK to RA_RULES).
• INVOICE_SOURCE_ID / NON_DELIVERY_INVOICE_SOURCE_ID — AutoInvoice sources (FK to RA_BATCH_SOURCES_ALL).
• ENTRY_CREDIT_CHECK_RULE_ID / SHIPPING_CREDIT_CHECK_RULE_ID — credit checking rules at order entry and shipping (FK to OE_CREDIT_CHECK_RULES).
• PRICE_LIST_ID — default price list (FK to QP_LIST_HEADERS_B).
• WAREHOUSE_ID — default shipping warehouse (FK to HR_ALL_ORGANIZATION_UNITS).
• DEFAULT_OUTBOUND_LINE_TYPE_ID / DEFAULT_INBOUND_LINE_TYPE_ID — self-referencing defaults for outbound and inbound lines.
• SHIPPING_METHOD_CODE, FREIGHT_TERMS_CODE, FOB_POINT_CODE, DEMAND_CLASS_CODE, SHIPMENT_PRIORITY_CODE — shipping and demand defaults.
• INSPECTION_REQUIRED_FLAG, PO_REQUIRED_FLAG, ENFORCE_LINE_PRICES_FLAG, AUTO_SCHEDULING_FLAG, AGREEMENT_REQUIRED_FLAG — behavioral control flags.
• ATTRIBUTE1–ATTRIBUTE15 / CONTEXT — descriptive flexfield segments for customer extensions.

Common Use Cases and Queries

The most frequent requirement is resolving the transaction type code or name associated with an order or line. Because the base table stores codes while OE_TRANSACTION_TYPES_TL holds the translated name, joins typically involve the TL table.

To list active order types:

• SELECT transaction_type_id, transaction_type_code, order_category_code FROM oe_transaction_types_all WHERE order_category_code = 'ORDER' AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

To report order headers with their type code and default warehouse:

• SELECT h.order_number, t.transaction_type_code, t.warehouse_id FROM oe_order_headers_all h, oe_transaction_types_all t WHERE h.order_type_id = t.transaction_type_id;

To identify line types and their default outbound line type:

• SELECT transaction_type_id, transaction_type_code, default_outbound_line_type_id FROM oe_transaction_types_all WHERE order_category_code = 'LINE';

Other use cases include auditing which invoicing and accounting rules are attached to each type, validating credit check rule configuration, and profiling order volumes by transaction type for reporting.

Related Objects

The following tables are the most significant references and dependents, using the documented join columns:

• OE_ORDER_HEADERS_ALL — references OE_TRANSACTION_TYPES_ALL via ORDER_TYPE_ID; the primary transactional dependent.
• OE_ORDER_LINES_ALL — references OE_TRANSACTION_TYPES_ALL via LINE_TYPE_ID.
• OE_TRANSACTION_TYPES_TL — translation table joined on TRANSACTION_TYPE_ID to obtain display names.
• OE_WORKFLOW_ASSIGNMENTS — maps order and line types to workflows via ORDER_TYPE_ID and LINE_TYPE_ID.
• RA_RULES — source of accounting and invoicing rules via ACCOUNTING_RULE_ID and INVOICING_RULE_ID.
• RA_BATCH_SOURCES_ALL — AutoInvoice sources via INVOICE_SOURCE_ID and NON_DELIVERY_INVOICE_SOURCE_ID.
• RA_CUST_TRX_TYPES_ALL — receivables transaction types via CUST_TRX_TYPE_ID.
• OE_CREDIT_CHECK_RULES — credit check rules via ENTRY_CREDIT_CHECK_RULE_ID and SHIPPING_CREDIT_CHECK_RULE_ID.
• QP_LIST_HEADERS_B and HR_ALL_ORGANIZATION_UNITS — default price list and warehouse references.

This table is maintained through the Order Management setup UI and is generally not populated by public APIs; it is queried extensively by the Order Management APIs and concurrent programs that process orders.