Search Results oe_transaction_types_all




The OE_TRANSACTION_TYPES_ALL table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical repository for defining and managing order transaction types within the Order Management (OM) module. It serves as a foundational data structure that governs the behavior, validation rules, and processing logic for various sales order and return transactions. This table is part of the multi-organization architecture (Multi-Org) in Oracle EBS, enabling transaction type definitions to be shared or restricted across operating units based on business requirements.

Key Attributes and Structure

The OE_TRANSACTION_TYPES_ALL table contains several key columns that define transaction type properties:
  • TRANSACTION_TYPE_ID: Primary key identifier for the transaction type.
  • NAME: User-defined name for the transaction type (e.g., "Standard Sales Order", "Return").
  • DESCRIPTION: Detailed explanation of the transaction type's purpose.
  • ORG_ID: Operating unit identifier for Multi-Org segregation.
  • TYPE_CLASS_CODE: Categorizes the transaction (e.g., "ORDER", "RETURN", "QUOTE").
  • FLOW_CONTROL_CODE: Determines the order lifecycle workflow (e.g., "STANDARD", "BOOK_ONLY").
  • CREDIT_CHECK_RULE_ID: Links to credit validation rules.
  • PRICING_EVENT: Specifies when pricing calculations occur.
  • SHIP_CONFIRMATION_FLAG: Controls whether shipping confirmation is required.
  • INVOICING_RULE_ID: Associates revenue recognition rules.

Functional Significance

Transaction types defined in this table influence:
  1. Order Processing Workflows: The FLOW_CONTROL_CODE dictates whether orders undergo full fulfillment cycles or bypass certain steps like shipping.
  2. Pricing and Validation: Rules for price calculations, credit checks, and order entry validations are triggered based on transaction type configurations.
  3. Integration Points: Transaction types determine how orders interface with modules like Accounts Receivable (AR), Inventory (INV), and Shipping (WSH).
  4. Reporting and Analytics: Serves as a dimension for classifying order data in operational reports and BI systems.

Technical Implementation

In Oracle EBS 12.x, this table is populated via:
  • Seeded data during installation (e.g., "Standard Order", "Internal Order")
  • Custom entries created through the Order Management Super User responsibility (Navigation: Order Management > Setup > Transactions > Transaction Types)
The table has foreign key relationships with:
  • OE_HEADERS_ALL (via ORDER_TYPE_ID)
  • OE_CREDIT_CHECK_RULES
  • RA_RULES for invoicing rules

Version-Specific Considerations

Between 12.1.1 and 12.2.2:
  • 12.2.2 introduces enhanced validation hooks through Oracle Fusion Middleware integration
  • Web services in 12.2.2 may expose transaction type attributes via SOAP APIs
  • Both versions maintain backward compatibility with transaction type definitions

Customization Guidelines

When extending this table:
  1. Always clone seeded transaction types rather than modifying them directly
  2. Maintain Multi-Org context through proper ORG_ID population
  3. Register custom transaction types in FND_LOOKUP_VALUES for UI consistency
  4. Test workflow impacts using Oracle's Order Simulation capability