Search Results fob_point_code




Overview
Explore in AI Chat

Overview

ASO_I_LINE_TYPES_V is a public APPS view in the Oracle E-Business Suite Order Capture (ASO) module. It is defined as a filtered projection over OE_TRANSACTION_TYPES_VL, restricted to rows where TRANSACTION_TYPE_CODE equals 'LINE'. The view therefore exposes the set of valid order line transaction types — the line-level workflow classifications that govern how order lines behave with respect to pricing, shipping, invoicing, and accounting. In practical terms, ASO_I_LINE_TYPES_V provides a single, read-only source for line type reference data that Order Capture, Order Management, and downstream integration processes rely upon.

The view is stable and valid in both Oracle EBS 12.1.1 and 12.2.2. Its columns correspond directly to the shipping, freight, FOB, invoicing, and accounting attributes attached to each line type, making it a convenient denormalized source for reporting and interface code that must resolve the processing rules associated with a given line type identifier.

Underlying Base Objects

ASO_I_LINE_TYPES_V is defined over the single documented base object OE_TRANSACTION_TYPES_VL, itself a view over the transaction type tables. The VL suffix indicates the view contains translatable (multi-language) name and description columns sourced from the underlying translation tables. The ASO view adds no aggregation or joins of its own; it simply selects a defined column list and applies the filter TRANSACTION_TYPE_CODE = 'LINE'. This contrasts with order header and return transaction types, which are excluded.

  • OE_TRANSACTION_TYPES_VL — the immediate parent view supplying transaction type attributes and translated names.
  • Filter condition — TRANSACTION_TYPE_CODE = 'LINE' limits output to line-level transaction types only.
  • Owner — APPS; the view is granted for reporting and concurrent processing use.

Key Columns

The view exposes the full set of line type configuration attributes. The most significant include:

Common Use Cases and Queries

Typical uses include retrieving the default shipping method for a line type, validating line type configuration during order import, building reference lists in extensions, and reconciling line type attributes across operating units. Because the view is filtered to LINE types, it can be joined directly to line-level tables without additional filtering.

The following query returns line types and their shipping configuration:

SELECT line_type_id, name, shipping_method_code, shipment_priority_code, freight_terms_code, order_category_code FROM apps.aso_i_line_types_v WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

A second common pattern resolves a single line type by identifier:

SELECT name, shipping_method_code, fob_point_code FROM apps.aso_i_line_types_v WHERE line_type_id = :p_line_type_id;

For multi-org reporting, add a predicate on ORG_ID to restrict results to the relevant operating unit.