Search Results pricing_method_code

Overview

BOM_LINES_VIEW is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It resides within the Bills of Material (BOM) product family and is documented in the ETRM repository as an order lines view used by delete constraints. The view exposes the full column set of the order line entity, including scheduling, pricing, shipping, return, and service-related attributes. Its primary architectural role is to present a consolidated, queryable projection of order line data that BOM-related delete processing can reference when validating referential integrity across order and configuration structures.

Because it is a view rather than a table, BOM_LINES_VIEW contains no data of its own. It is not intended to be the target of DML; inserts, updates, and deletes against order lines must be performed against the underlying base table. The view is marked VALID in the ETRM metadata, indicating that all referenced objects resolve successfully in the target environment.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, BOM_LINES_VIEW is defined over a single referenced base object: the synonym SO_LINES_ALL. The view definition text, as recorded in the ETRM repository, projects a wide selection of columns directly from the order line source, with no aggregation, joins, or computed expressions apparent in the excerpt. This means the view functions as a narrow, purpose-built projection of the order line record rather than a denormalized reporting construct.

The view inherits WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) from the source, confirming it is a standard Oracle Applications entity view compliant with the product's audit and concurrent manager conventions.

Key Columns

The column list reflects the breadth of the order line model. Structurally significant identifiers include LINE_ID, HEADER_ID, SOURCE_LINE_ID, SHIPMENT_SCHEDULE_LINE_ID, PARENT_LINE_ID, ATO_LINE_ID, LINK_TO_LINE_ID, and the column the user searched for, SERVICE_PARENT_LINE_ID. This last column associates a service line with the parent line that generated it, supporting service and warranty line hierarchies in order configurations.

• SERVICE_PARENT_LINE_ID — identifies the parent order line to which a service line is attached; central to service-enabled and ATO order structures.
• PARENT_LINE_ID and LINK_TO_LINE_ID — define hierarchical and linkage relationships among configured or option lines.
• LINE_TYPE_CODE, OPTION_FLAG, OPEN_FLAG, ITEM_TYPE_CODE, ATO_FLAG — classify the line and its behavior in configuration and fulfillment.
• INVENTORY_ITEM_ID, COMPONENT_SEQUENCE_ID, COMPONENT_CODE — tie the line to the item and bill of material component context.
• ORDERED_QUANTITY, SHIPPED_QUANTITY, INVOICED_QUANTITY, SERVICED_QUANTITY — quantity tracking across the order-to-cash and service lifecycles.
• PRICE_LIST_ID, SELLING_PRICE, LIST_PRICE, PERCENT_BASE_PRICE — pricing attributes carried on the order line.
• SERVICE_DURATION, SERVICE_START_DATE, SERVICE_END_DATE, SERVICE_COTERMINATE_FLAG — define service coverage terms for service lines.

Common Use Cases and Queries

The view is most commonly queried when diagnosing delete constraint failures, investigating service or configuration line hierarchies, or extracting order line detail for reconciliation. A typical query to identify service lines and their parents is shown below.

• SELECT line_id, header_id, parent_line_id, service_parent_line_id, inventory_item_id, ordered_quantity FROM bom_lines_view WHERE service_parent_line_id IS NOT NULL;
• SELECT line_id, header_id, line_type_code, option_flag, ato_flag FROM bom_lines_view WHERE header_id = :header_id ORDER BY line_number;
• SELECT line_id, ordered_quantity, shipped_quantity, invoiced_quantity FROM bom_lines_view WHERE inventory_item_id = :item_id;

Because the view is a projection of SO_LINES_ALL, queries against it are subject to the same access controls and performance characteristics as the base order line table. Appropriate predicates such as HEADER_ID or LINE_ID should always be supplied to limit the result set.