Search Results oe




DeepseekETRM - OE Tables and Views in Oracle EBS 12.1.1/12.2.2

Overview

The Oracle Order Management (OE) module in E-Business Suite (EBS) 12.1.1 and 12.2.2 relies on a comprehensive set of tables and views to manage order lifecycle processes. DeepseekETRM provides technical reference documentation for these database objects, detailing their structures, relationships, and functional purposes within the Order-to-Cash cycle.

Core OE Tables

  • OE_ORDER_HEADERS_ALL: Master table storing order header information including customer data, order dates, and statuses. Key columns include HEADER_ID (PK), ORDER_NUMBER, and ORG_ID.
  • OE_ORDER_LINES_ALL: Contains line-level details with columns like LINE_ID, HEADER_ID (FK to headers), INVENTORY_ITEM_ID, and ORDERED_QUANTITY.
  • OE_TRANSACTION_TYPES_TL: Defines order transaction types with NAME and DESCRIPTION columns for multilingual support.
  • OE_HOLD_SOURCES_ALL: Manages order hold reasons with HOLD_SOURCE_ID and HOLD_NAME columns.
  • OE_PRICE_ADJUSTMENTS: Stores pricing adjustments with ADJUSTMENT_ID, LINE_ID, and ADJUSTMENT_TYPE columns.

Key Supporting Tables

  • OE_SALES_CREDITS: Tracks sales credits with SALES_CREDIT_ID and PERCENTAGE columns.
  • OE_ORDER_HOLDS_ALL: Implements hold functionality with HOLD_ID and RELEASED_FLAG columns.
  • OE_HOLD_DEFINITIONS: Contains hold definition metadata including HOLD_TYPE_CODE.
  • OE_ORDER_NOTES: Stores order comments with NOTE_ID and TEXT columns.

Integration Tables

  • WSH_DELIVERY_DETAILS: Links orders to shipping with SOURCE_LINE_ID mapping to OE_LINES.
  • RA_CUSTOMER_TRX_ALL: Connects to Receivables with INTERFACE_HEADER_ATTRIBUTE1 storing OE_HEADER_ID.
  • ONT_SHIPPING_PARAMETERS: Contains shipping integration parameters.

Important Views

  • OE_ORDER_HEADERS_V: Header information view with additional joins to customer tables.
  • OE_ORDER_LINES_V: Enhanced line view including item descriptions.
  • OE_PRICE_ADJUSTMENTS_V: Pricing adjustment view with calculation details.
  • OE_HOLDS_V: Comprehensive hold information view.

Technical Considerations

  • Multi-org architecture implemented through _ALL tables with ORG_ID filtering
  • VPD (Virtual Private Database) policies enforce data security
  • Materialized views like OE_ORDER_SUMMARY_MV optimize reporting
  • API tables (OE_HEADERS_IFACE_ALL) support order import processes

Version-Specific Notes

In 12.2.2, Oracle introduced:
  • Enhanced XML columns in interface tables
  • Additional indexes for performance optimization
  • New columns for cloud integration capabilities
  • Modified views to support REST data services

Usage Patterns

Developers working with OE tables should:
  • Always query _ALL tables with proper ORG_ID filters
  • Use public APIs (OE_ORDER_PUB) rather than direct DML
  • Leverage views for reporting to ensure data consistency
  • Consider Open Interface tables for bulk data operations
This technical reference documentation provides essential guidance for customizations, integrations, and performance tuning in Oracle Order Management implementations.