Search Results demand_class_code

Overview

BOM_LINE_DETAILS_VIEW is a read-only dictionary view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is shipped as a VALID database object within the Bills of Material (BOM) product family and exposes order line detail records sourced from the sales order line details entity. The view's documented description states that it provides "order line details" and that it is "used by delete constraints." This indicates that the view exists primarily to support referential integrity logic — the database-level constraints and foreign key relationships that govern deletion of parent records — rather than as an end-user reporting interface. Because BOM structures (bills of material, components, and routing operations) intersect with order entry data, delete constraints against sales order line details must be able to resolve component and schedule information. BOM_LINE_DETAILS_VIEW provides that bridge by presenting a stable, denormalized projection of SO_LINE_DETAILS with the columns relevant to shippable, transactable, and reservable component lines. For reporting and integration purposes, the view is a convenience layer that allows BOM-side logic to reference order line detail columns without querying the base sales order table directly, and it is therefore typically accessed by concurrent programs, workflow background processes, and custom extensions rather than by interactive forms.

Underlying Base Objects

Per the documented ETRM metadata for release 12.2.2, the view is defined over a single referenced base object: SO_LINE_DETAILS, exposed through a SYNONYM in the APPS schema. The view text confirms this directly with a simple projection:

• SO_LINE_DETAILS — the underlying order line details table that stores one row per scheduled line detail, including item, quantity, warehouse, schedule date, and component-level flags.

The view applies no joins, filters, or aggregation; every row returned corresponds one-to-one with a row in SO_LINE_DETAILS. Its value lies in column selection and in providing a BOM-owned object name that can be referenced by delete constraints, so that constraint definitions do not have to hard-code a dependency on the Oracle Order Management schema. This separation is important during patching and upgrades: the BOM development team can adjust the view definition without altering the constraint targets, and Order Management can evolve the base table as long as the projected columns remain stable.

Key Columns

The view exposes 41 columns, of which the following are most significant.

• LINE_DETAIL_ID — primary key of the line detail record; uniquely identifies each row returned by the view.
• LINE_ID — foreign key to the parent order line, linking each detail back to its order line header.
• INVENTORY_ITEM_ID — the inventory item associated with the line detail; joins to MTL_SYSTEM_ITEMS_B.
• SHIPPABLE_FLAG — indicates whether the line detail may be shipped; a central column for the user's search and for fulfillment eligibility checks.
• TRANSACTABLE_FLAG — indicates whether the detail can be transacted in inventory.
• RESERVABLE_FLAG — indicates whether the detail is eligible for reservation against on-hand inventory.
• RELEASED_FLAG — indicates whether the detail has been released to the warehouse for picking and shipping.
• QUANTITY, WAREHOUSE_ID, SUBINVENTORY, REVISION, LOT_NUMBER — fulfillment attributes describing what is being shipped, from where, and in what configuration.
• SCHEDULE_DATE, SCHEDULE_STATUS_CODE, SCHEDULE_LEVEL_CODE, DEMAND_CLASS_CODE — scheduling and demand classification attributes used by planning and order scheduling logic.
• COMPONENT_SEQUENCE_ID, COMPONENT_CODE, COMPONENT_RATIO, INCLUDED_ITEM_FLAG — component context used where the order line detail represents a configured or included item.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns, available for customer-specific extensions.

Common Use Cases and Queries

Because the view mirrors SO_LINE_DETAILS, it is most often used to inspect shippable or releasable order line details, to validate delete-constraint behavior during data cleanup, and to support custom reporting that needs BOM-side visibility into order details. Typical queries include:

• List all shippable line details for a given order line: SELECT line_detail_id, inventory_item_id, quantity, shippable_flag FROM apps.bom_line_details_view WHERE line_id = :line_id AND shippable_flag = 'Y';
• Identify unreleased but reserved details prior to pick release: SELECT line_detail_id, warehouse_id, subinventory FROM apps.bom_line_details_view WHERE released_flag = 'N' AND reservable_flag = 'Y';
• Audit scheduling by demand class and schedule date: SELECT demand_class_code, schedule_date, schedule_status_code, COUNT(*) FROM apps.bom_line_details_view GROUP BY demand_class_code, schedule_date, schedule_status_code;

All queries should be issued against the APPS synonym or with an explicit APPS schema prefix, and callers should treat the view as read-only, relying on the base SO_LINE_DETAILS table or the Order Management APIs for any data modification.