Search Results line_discounts

Overview

APPS.OE_BIS_BOOKINGS_V is a seeded Oracle E-Business Suite reporting view owned by the APPS schema and registered in the Oracle Order Management application (FND Design Data: OE.OE_BIS_BOOKINGS_V). It is a denormalized, business-intelligence-oriented projection of booked order line data, designed to support the Order Management Business Intelligence System (OE_BIS) and downstream analytical reporting such as Oracle Sales Analytics and custom booking, margin, and backlog reporting. The view presents one row per order line, exposing pricing, costing, quantity, booking date, organizational, product grouping, and sales channel attributes in a single queryable structure. The object carries a VALID status in ETRM for 12.1.1 and 12.2.2 and is intended for read-only query access; it should not be used as a transactional interface.

Underlying Base Objects

The view is defined over a set of Order Management, Inventory, Costing, and HR/GL objects. The order header and line facts derive from SO_HEADERS_ALL, SO_LINES_ALL, SO_ORDER_TYPES_ALL, and SO_CYCLE_ACTIONS, with SO_LOOKUPS supplying decoded lookup values. Item-level attributes are sourced from MTL_SYSTEM_ITEMS, MTL_PARAMETERS, MTL_UOM_CONVERSIONS, and the category model via MTL_CATEGORIES, MTL_DEFAULT_CATEGORY_SETS, and MTL_ITEM_CATEGORIES. Cost information is joined from CST_ITEM_COSTS. Organizational context is resolved through HR_ORGANIZATION_INFORMATION, while GL_SETS_OF_BOOKS contributes set-of-books information. FND_GLOBAL is referenced to resolve runtime context such as the current organization or user. The view is referenced by the OE_BIS package, confirming its role as a foundation for the Order Management BI schema.

Key Columns

• HEADER_ID / LINE_ID — Primary keys linking back to the order header and line.
• CUSTOMER_ID — Sold-to customer identifier.
• LINE_CURRENCY / LINE_COST_CURRENCY — Transactional and cost currencies (VARCHAR2(15)).
• UNIT_LIST_PRICE, UNIT_SELLING_PRICE — Per-unit list and net selling prices.
• LINE_LIST_PRICE, LINE_SELLING_PRICE, LINE_DISCOUNTS, LINE_MARGIN — Extended line-level pricing, discount, and margin amounts.
• LINE_COST — Line cost used in margin calculations.
• INVENTORY_ITEM_ID, WAREHOUSE_ID, OU_ID — Item, warehouse, and operating unit context.
• ORDERED_QUANTITY, CANCELLED_QUANTITY — Booked and subsequently cancelled quantities.
• BOOKING_DATE — The date the order was booked, central to time-series bookings analysis.
• PRODUCT_GROUP — VARCHAR2(240) attribute reflecting the product grouping (typically derived from item category assignments), commonly used as a reporting dimension.
• SALES_CHANNEL — VARCHAR2(80) representing the sales channel dimension.

Common Use Cases and Queries

The view is typically queried for bookings bookings reporting, margin analysis, product-group rollups, and sales-channel trending. A common query aggregates net bookings by product group and booking period:

• SELECT PRODUCT_GROUP, TRUNC(BOOKING_DATE,'MM') BOOKING_MONTH, SUM(LINE_SELLING_PRICE) NET_BOOKINGS, SUM(LINE_MARGIN) TOTAL_MARGIN FROM APPS.OE_BIS_BOOKINGS_V GROUP BY PRODUCT_GROUP, TRUNC(BOOKING_DATE,'MM') ORDER BY 2,1;
• Filtering by SALES_CHANNEL to evaluate channel performance over a date range.
• Joining on INVENTORY_ITEM_ID or CUSTOMER_ID to enrich bookings data with master data for dashboards.
• Netting ORDERED_QUANTITY against CANCELLED_QUANTITY to measure effective booked demand.

Because the view joins multiple transactional tables, queries should apply selective predicates (booking date, operating unit, product group) to optimize performance in large data volumes.