Results for “so_order_types_115_all”

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

Overview

SO_ORDER_TYPES_115_ALL is the Oracle Order Entry (OE) master table that defines order types in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Each row represents a configurable order type — for example, a standard sales order, a return, a blanket order, or an internal order — and carries the defaulting, pricing, shipping, invoicing, and accounting attributes that Order Management applies to sales orders created under that type. The table is owned by the OE schema, is documented as VALID, and physically comprises 58 columns in the 12.2.2 ETRM schema.

Functionally, SO_ORDER_TYPES_115_ALL operates as a central reference or "setup" table: the order type identifier it owns is consumed throughout Order Management, Receivables, Advanced Pricing, Shipping, and downstream fulfillment and costing flows. Because order type selection governs so much downstream behavior, changes to rows in this table have a wide operational blast radius.

The ETRM relationship metadata classifies this object heuristically as a Data Vault hub. In modeling terms, this is a reasonable suggestion: ORDER_TYPE_ID is a stable business key that is referenced by a very large number of dependent tables, and the descriptive attributes attached to it are defaults rather than transaction facts.

Key Information Stored

The surrogate primary key is ORDER_TYPE_ID, enforced by the constraint SO_ORDER_TYPES_ALL_115_PK. Two unique indexes are documented: SO_ORDER_TYPES_115_U1 on ORDER_TYPE_ID and SO_ORDER_TYPES_115_U2 on NAME, making NAME the principal business-key candidate. The most operationally significant columns include:

• NAME — the user-facing order type name shown in Order Management windows and reports.
• ORDER_TYPE_ID — the surrogate key referenced by virtually every dependent order table.
• ORDER_CATEGORY_CODE and ORDER_NUMBER_SOURCE_ID — control order numbering and classification behavior.
• PRICE_LIST_ID, ENFORCE_PRICE_LIST_FLAG, ENFORCE_LINE_PRICES_FLAG — pricing defaults and enforcement rules.
• WAREHOUSE_ID, SHIP_METHOD_CODE, SHIPMENT_PRIORITY_CODE, FREIGHT_TERMS_CODE, FOB_CODE — shipping and warehouse defaulting.
• INVOICING_RULE_ID, ACCOUNTING_RULE_ID, INVOICING_CREDIT_METHOD_CODE, ACCOUNTING_CREDIT_METHOD_CODE, CUST_TRX_TYPE_ID — invoicing and revenue accounting defaults.
• STANDARD_VALUE_RULE_SET_ID — the Defaulting Rules set applied to this order type.
• CURRENCY_CODE, CONVERSION_TYPE_CODE, COST_OF_GOODS_SOLD_ACCOUNT — currency and costing defaults.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective dating controls.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — the DFF extension columns.
• ORG_ID — the multi-org operating unit discriminator.

Common Use Cases and Queries

Typical uses include setup validation, order-vs-type reporting, and cross-module reconciliation of orders by category or operating unit.

SELECT order_type_id, name, order_category_code, currency_code
FROM   oe.so_order_types_115_all
WHERE  sysdate BETWEEN start_date_active AND NVL(end_date_active, sysdate)
  AND  org_id = :p_org_id;

A common reporting pattern joins SO_HEADERS_ALL to this table to break out open order volumes by order type:

SELECT t.name, COUNT(*) order_count, SUM(h.ordered_amount) total_amount
FROM   oe.so_headers_all h, oe.so_order_types_115_all t
WHERE  h.order_type_id = t.order_type_id
GROUP  BY t.name;

Because NAME is uniquely indexed, lookups by order type name are efficient and are frequently used in concurrent programs and interface loads that resolve an identifier from a value supplied by users.

Related Objects

The table participates in an extensive foreign key web. The most significant referencing objects and join columns are:

• SO_HEADERS_ALL — join on ORDER_TYPE_ID; the primary consumer for all sales orders.
• SO_HEADERS_INTERFACE_ALL — join on ORDER_TYPE_ID and ORDER_TYPE; used by Order Import.
• SO_ORDER_APPROVALS and SO_PICKING_RULES / SO_PICKING_BATCHES_ALL — join on ORDER_TYPE_ID; approval and picking setup.
• RA_CUSTOMERS, RA_SITE_USES_ALL, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL — join on ORDER_TYPE_ID; default order type per customer or site.
• ICX_WEB_STORE_OPTIONS — join on ORDER_TYPE_ID; iStore order type configuration.
• OE_BLANKET_HEADERS_ALL, ASO_QUOTE_HEADERS_ALL, OE_RETROBILL_REQUESTS — join on ORDER_TYPE_ID; blanket, quote, and retro-billing flows.

On the referenced side, this table's own foreign keys point to SO_STANDARD_VALUE_RULE_SETS (via STANDARD_VALUE_RULE_SET_ID) and RA_CUST_TRX_TYPES_ALL (via CUST_TRX_TYPE_ID), which govern defaulting and Receivables transaction typing respectively. Together these relationships make SO_ORDER_TYPES_115_ALL one of the most heavily depended-upon reference tables in the Oracle Order Management data model.