Results for “invoice_source_id”

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

Overview

The OE_AK_ORDER_TYPES_V view is a reporting and integration object within the Oracle Order Management (ONT) module of Oracle E-Business Suite, owned by the APPS schema and marked VALID in ETRM for releases 12.1.1 and 12.2.2. It is a lightweight projection over the seeded OE_ORDER_TYPES_V view, which itself resolves the order transaction type configuration defined for a given operating unit. The "AK" prefix reflects the Oracle Alert / Applications Knowledge convention originally used to expose descriptive-flexfield-friendly views for lookups and integration endpoints.

Functionally, the view presents the attributes that govern how an order transaction type behaves: default currency, price list, warehouse, shipping and freight attributes, demand class, and the accounting, invoicing, and credit rules applied to downstream AR and inventory transactions. Because it flattens the order type configuration into a single row per transaction type, it is frequently consumed by concurrent programs, Order Import, BI Publisher reports, and custom PL/SQL routines that need to resolve order-type defaults without joining the base order-type tables directly.

For users searching on invoice_source_id, this view is the documented source: it exposes both INVOICE_SOURCE_ID (the delivery-based invoice source) and NON_DELIVERY_INVOICE_SOURCE_ID (the invoice source used when goods are not shipped), enabling reporting on how an order type generates receivables transactions.

Underlying Base Objects

Per the ETRM metadata for 12.2.2, the only referenced base object is the view OE_ORDER_TYPES_V, owned by APPS. OE_AK_ORDER_TYPES_V is therefore a second-level view rather than a view over physical tables; the physical order type definitions reside in the base order types table (OE_ORDER_TYPES) that OE_ORDER_TYPES_V resolves. The projection is not a simple SELECT *: the view renames and re-aliases certain columns. Notably, the base attribute WAREHOUSE_ID is surfaced as SHIP_FROM_ORG_ID, and a literal space (' ') occupies the position commonly exposed elsewhere as ORDER_NUMBER_SOURCE_ID, while DEF_TRANSACTION_PHASE_CODE is passed through unchanged. Understanding this aliasing is essential when troubleshooting column-not-found errors in custom code.

Key Columns

• TRANSACTION_TYPE_ID — Surfaces as ORDER_TYPE_ID; the primary key of the order transaction type and the join key to OE_ORDER_HEADERS_ALL.ORDER_TYPE_ID.
• ORDER_CATEGORY_CODE — Identifies the order category (for example, ORDER, RETURN, or MIXED).
• CURRENCY_CODE and CONVERSION_TYPE_CODE — Default currency and the GL conversion type applied to the order type.
• CUST_TRX_TYPE_ID — The Receivables transaction type used when the order is invoiced.
• INVOICE_SOURCE_ID — The invoice source used for delivery-based invoicing.
• NON_DELIVERY_INVOICE_SOURCE_ID — The invoice source applied when invoicing occurs without shipment.
• INVOICING_RULE_ID and INVOICING_CREDIT_METHOD_CODE — Invoicing rule (for example, advance or arrears) and credit method.
• ACCOUNTING_RULE_ID and ACCOUNTING_CREDIT_METHOD_CODE — Revenue recognition rule and credit method.
• PRICE_LIST_ID and SHIP_FROM_ORG_ID — Default price list and shipping warehouse (base column WAREHOUSE_ID).
• DEMAND_CLASS_CODE, SHIPMENT_PRIORITY_CODE, SHIPPING_METHOD_CODE, FREIGHT_TERMS_CODE, FOB_POINT_CODE — Fulfillment and freight defaults.
• AGREEMENT_TYPE_CODE — Default agreement type associated with the order type.
• DEF_TRANSACTION_PHASE_CODE — Default transaction phase used for order processing.

Common Use Cases and Queries

The view is typically joined to order headers to report order type configuration alongside transactional data, or queried directly to validate setup. A representative query resolving the invoice source configuration is:

• SELECT order_type_id, order_category_code, currency_code, invoice_source_id, non_delivery_invoice_source_id, cust_trx_type_id FROM apps.oe_ak_order_types_v;

Typical scenarios include auditing which order types reference a specific invoice source, verifying that return order types carry the correct accounting and credit rules, and populating integration payloads where the order type defaults must be passed to an external fulfillment or billing system. Because it is a view, it is read-only and should not be used for DML; changes to order type configuration must be made through the Order Management setup forms. Users should note that the view is not filtered by operating unit, so reports spanning multiple operating units must restrict results using the calling context or by joining additional setup views.