Search Results unit_standard_price

Overview

BIC_REVENUE_TRX_DETAIL_V is a reporting view associated with the BIC – Customer Intelligence module in Oracle E-Business Suite, a product that is now classified as obsolete. The view is designed to expose revenue transaction detail at the invoice line level, combining transaction data from Oracle Receivables with descriptive item information from Oracle Inventory. Its primary purpose is to support revenue analysis, customer intelligence reporting, and downstream integration extracts where line-level revenue, pricing, and quantity information must be correlated with item descriptions.

The view is not implemented in the reference database from which this metadata was captured, meaning it exists in the ETRM dictionary as documentation but is not physically present in that environment. This is a common situation for legacy BIC objects that have been superseded by later analytics offerings. In Oracle EBS 12.1.1 and 12.2.2 environments where it does exist, the view behaves as a lightweight, profile-filtered projection of Receivables transaction lines.

Underlying Base Objects

The view text is defined over two base tables:

• RA_CUSTOMER_TRX_LINES_ALL – aliased as TRX, the primary source of transaction line data. This is the core Oracle Receivables table holding invoice, debit memo, credit memo, and on-account line records.
• MTL_SYSTEM_ITEMS – aliased as MT, joined via an outer join on INVENTORY_ITEM_ID to supply the item DESCRIPTION.

Two profile option filters govern the result set. The join to RA_CUSTOMER_TRX_LINES_ALL is restricted by TRX.ORG_ID = FND_PROFILE.VALUE('ORG_ID'), limiting results to the operating unit of the current session. The outer join to MTL_SYSTEM_ITEMS is additionally constrained by MT.ORGANIZATION_ID (+) = FND_PROFILE.VALUE('ASO_PRODUCT_ORGANIZATION_ID'), so item descriptions resolve against the product organization configured in that profile option. Because the item join is outer, transaction lines without a matching inventory item still return, with DESCRIPTION null.

Key Columns

• CUSTOMER_TRX_ID – Identifier of the parent Receivables transaction, used to join back to RA_CUSTOMER_TRX_ALL and related entities.
• INVENTORY_ITEM_ID – Inventory item identifier for the transaction line; the join key to MTL_SYSTEM_ITEMS.
• UNIT_STANDARD_PRICE – The standard or list unit price for the item, distinct from the actual selling price. This column is the subject of the "unit_standard_price" search and is commonly used to compute price variance against UNIT_SELLING_PRICE.
• UNIT_SELLING_PRICE – The actual unit price charged to the customer on the transaction line.
• QUANTITY_ORDERED, QUANTITY_CREDITED, QUANTITY_INVOICED – Quantity metrics supporting order-to-invoice reconciliation and revenue recognition analysis.
• SALES_ORDER, SALES_ORDER_DATE – Originating sales order reference and its date, enabling demand-to-revenue traceability.
• ORG_ID – Operating unit identifier; combined with the profile filter, enforces multi-org isolation.
• DESCRIPTION – Item description from MTL_SYSTEM_ITEMS, supplied for readability in reports.

Common Use Cases and Queries

The view supports revenue detail reporting, price variance analysis, and item-level revenue trending. A typical query aggregating selling versus standard price follows:

• Revenue by item with price variance: SELECT INVENTORY_ITEM_ID, DESCRIPTION, SUM(QUANTITY_INVOICED * UNIT_SELLING_PRICE) revenue, SUM(QUANTITY_INVOICED * (UNIT_SELLING_PRICE - UNIT_STANDARD_PRICE)) variance FROM BIC_REVENUE_TRX_DETAIL_V GROUP BY INVENTORY_ITEM_ID, DESCRIPTION;
• Sales order traceability: SELECT SALES_ORDER, SALES_ORDER_DATE, CUSTOMER_TRX_ID, UNIT_STANDARD_PRICE FROM BIC_REVENUE_TRX_DETAIL_V WHERE SALES_ORDER IS NOT NULL ORDER BY SALES_ORDER_DATE;
• Credited quantity review: SELECT CUSTOMER_TRX_ID, INVENTORY_ITEM_ID, QUANTITY_CREDITED, QUANTITY_INVOICED FROM BIC_REVENUE_TRX_DETAIL_V WHERE QUANTITY_CREDITED > 0;

Because the view is obsolete and profile-dependent, developers should confirm its presence in the target instance and account for the ORG_ID and ASO_PRODUCT_ORGANIZATION_ID profile settings before relying on results.