Search Results rounding_fact

Overview

SO_OPTION_LINES_V is a reporting view in the Oracle E-Business Suite Order Entry (OE) module that exposes order line detail, with particular emphasis on configured items and their associated option/component lines. In the 12.1.1 and 12.2.2 releases it is used to present the base order line attributes (columns sourced from OE_ORDER_LINES_ALL and related pricing and header tables) together with derived values that would otherwise require procedural logic. Its principal reporting role is to surface the line type, option flag, ATO (Assemble-to-Order) status, and pricing totals for each order line, enabling configured-item ("Pick-to-Order" and "Assemble-to-Order") structures to be queried in a single pass.

The view is documented in the ETRM metadata as belonging to the Order Entry product. The metadata records that its underlying base objects are not explicitly enumerated and that it is "Not implemented in this database" in the captured excerpt, meaning the object is referenced for reference/documentation purposes rather than as a guaranteed physical object in every environment. Practitioners should verify its presence in their instance before relying on it.

Underlying Base Objects

Although the ETRM metadata does not enumerate base objects, the view text identifies the relevant sources. The primary source is the order lines table, referenced by alias LIN, providing all line-level columns such as LINE_ID, HEADER_ID, PARENT_LINE_ID, ATO_LINE_ID, LINE_TYPE_CODE, OPTION_FLAG, ORDERED_QUANTITY, SELLING_PRICE and pricing attributes. It is joined to the item master (alias MTL, i.e. MTL_SYSTEM_ITEMS_B) for ITEM_DESCRIPTION, BOM_ITEM_TYPE and SERVICEABLE_PRODUCT_FLAG, and to the price list table (alias SPL, e.g. QP_PRICE_LISTS) for PRICE_LIST_NAME and ROUNDING_FACTOR. The lookup meaning for ITEM_TYPE is resolved via a lookup table (alias SO2, the FND lookup values). Two key columns are computed by OE_QUERY functions: ATO_INDICATOR is derived from OE_QUERY.ATO_INDICATOR, and the monetary TOTAL and SERVICE_TOTAL are produced by OE_QUERY.LINE_TOTAL and OE_QUERY.SERVICE_TOTAL respectively.

Key Columns

• LINE_ID / HEADER_ID / PARENT_LINE_ID / ATO_LINE_ID — identifiers establishing the order line, its header, and the parent/ATO relationships that define configured structures.
• LINE_TYPE_CODE — the line's role (for example REGULAR, PARENT, CONFIG, OPTION); used to drive SHIPMENT_SCHEDULE_FLAG (PARENT yields 'Y').
• ATO_FLAG / ATO_INDICATOR — indicates whether the line is Assemble-to-Order. The view returns 'Y' when ATO_FLAG is 'Y', otherwise it invokes OE_QUERY.ATO_INDICATOR(LINE_ID, ITEM_TYPE_CODE) to derive the indicator — directly relevant to the user's search term "ato_indicator".
• OPTION_FLAG / OPEN_FLAG — classify option lines and open lines within a configuration.
• TOTAL / SERVICE_TOTAL — extended line amounts and service amounts computed by OE_QUERY functions.
• ITEM_DESCRIPTION, BOM_ITEM_TYPE, SERVICEABLE_FLAG — item-level descriptive and behavioral attributes.
• PRICE_LIST_NAME, LIST_PRICE, SELLING_PRICE, ROUNDING_FACT — pricing context for the line.

Common Use Cases and Queries

Typical uses include configuration reports, ATO/option analysis, and order-line pricing extracts. For example, to list configured option lines with their ATO indicator and total:

• SELECT line_id, header_id, line_number, line_type_code, option_flag, ato_indicator, item_description, ordered_quantity, total FROM so_option_lines_v WHERE ato_indicator = 'Y';
• SELECT header_id, line_id, parent_line_id, component_code, item_description, option_flag FROM so_option_lines_v WHERE line_type_code = 'CONFIG' ORDER BY parent_line_id;

Because ATO_INDICATOR and the TOTAL columns are function-derived, queries that filter or aggregate on them should expect higher execution cost than direct column reads. Consumers should confirm the object's existence and column set in their specific 12.1.1 or 12.2.2 environment before deploying dependent reports.