Search Results bim_fctv_order_lines

Overview

BIM_FCTV_ORDER_LINES is an Oracle E-Business Suite view belonging to the BIM (Marketing Intelligence) product family. Its documented purpose is to serve as a staging source used by concurrent programs that load the Marketing Intelligence summary tables. The view consolidates order header and order line information drawn from the Oracle Order Management and Advanced Supply Chain (ASO) interfaces, enriched with marketing source-code attribution and party market-segment data, so that downstream fact and summary tables can be populated in a single pass.

The name itself reflects this role: "FCTV" denotes a fact-style staging object, and "ORDER_LINES" indicates the grain of the data. Each row returned represents a single order line combined with its parent header attributes, forming the transactional foundation for marketing intelligence reporting such as sales analysis by campaign, media, channel, geography, and product. Because the object is a view rather than a table, no physical storage is required; the view is resolved at execution time by the calling concurrent program.

For the user searching on "selling_price," the relevant column is SELLING_PRICE, which is sourced directly from ODL.UNIT_SELLING_PRICE on the order line. This is the unit selling price of the ordered item and is distinct from LIST_PRICE, which is mapped from ODL.UNIT_LIST_PRICE.

Underlying Base Objects

The view is defined over four documented base objects. Two are order table interfaces from the ASO schema: ASO_I_ORDER_HEADERS_V (aliased ODH) and ASO_I_ORDER_LINES_V (aliased ODL). These supply header-level attributes such as order number, party, customer account, ordered date, operating unit, transaction currency, and return reason, and line-level attributes such as line number, quantity, pricing, and shipment details.

Two additional objects provide marketing context. BIM_SOURCE_CODE_DETAILS (SRCD) is outer-joined on ODH.MARKETING_SOURCE_CODE_ID and supplies the campaign, media, channel, event offer, and event identifiers. AMS_PARTY_MARKET_SEGMENTS (PMKT) contributes the market segment identifier applied to the transaction. The view also invokes BIM_GEO_PKG.GET_GEOGRAPHY_CODE to derive bill-to and ship-to geography codes from the invoice-to and ship-to organization identifiers, defaulting to the header values when the line-level organization is null or empty. The ETRM metadata records no owner and no separately documented referenced base objects; the four objects above are established by the embedded view text.

Key Columns

• SELLING_PRICE — Mapped from ODL.UNIT_SELLING_PRICE; the actual unit price at which the line was sold.
• LIST_PRICE — Mapped from ODL.UNIT_LIST_PRICE; the unit list price before discounts.
• HEADER_ID, LINE_ID, LINE_NUMBER — Primary identifiers establishing the order header and line grain.
• CUSTOMER_ID, ACCOUNT_ID — Party and customer account identifiers from the header.
• CAMPAIGN_ID, MEDIA_ID, CHANNEL_ID, EVENT_OFFER_ID, EVENT_ID — Marketing attribution keys, defaulted to -999 when no source-code detail exists.
• BILL_TO_GEOGRAPHY_CODE, SHIP_TO_GEOGRAPHY_CODE — Geography codes resolved by BIM_GEO_PKG.
• ORDERED_QUANTITY, SHIPPED_QUANTITY, CANCELLED_QUANTITY — Quantity measures used in marketing summaries.

Common Use Cases and Queries

The principal use case is concurrent processing that loads BIM summary tables, where the view supplies a pre-joined transactional extract. A typical query retrieving pricing alongside marketing attribution might read:

SELECT order_number, line_number, selling_price, list_price, campaign_id, sales_channel_code FROM bim_fctv_order_lines WHERE org_id = :p_org_id AND ordered_date BETWEEN :p_start AND :p_end;

Analysts may also aggregate selling price by campaign or geography for ad hoc analysis. Because the view relies on outer joins to source-code and market-segment data, results should be filtered or grouped with awareness that absent attribution returns -999 sentinels rather than nulls.