Search Results unit_standard_price

Overview

The view BIC_REVENUE_TRX_DETAIL_V is a reporting object associated with the BIC – Customer Intelligence product family, a legacy Oracle E-Business Suite module now classified as obsolete. In Oracle EBS 12.1.1 and 12.2.2 environments, the object is shipped as part of the historical BIC schema, but the ETRM metadata records its implementation status as "Not implemented in this database," indicating that no deployed instance or registered dependency exists in the current environment.

Functionally, the view consolidates revenue-bearing transaction line data sourced from Oracle Receivables and Inventory. It presents customer transaction lines alongside item descriptions, exposing pricing, quantity, and sales order attributes on a single row. Its purpose is to support customer intelligence and revenue analytics reporting — including margin analysis, price-versus-standard-cost comparisons, and product-level revenue aggregation — by joining receivables transaction lines to the item master.

Because the underlying product is obsolete, the view should be treated as a read-only reporting artifact. It is not a supported integration point and is not maintained for functional enhancements, but understanding its structure remains useful for environments that inherited the object during upgrade or consolidation.

Underlying Base Objects

The view is defined over two base tables joined through an outer-join pattern:

• RA_CUSTOMER_TRX_LINES_ALL — aliased as TRX in the view text. This is the primary source of transaction line detail, supplying transaction identifiers, item references, pricing columns, quantities, and sales order information. It is the driving table of the join.
• MTL_SYSTEM_ITEMS — aliased as MT. This table contributes the item DESCRIPTION value and is joined as an outer table so that lines without a matching item master record are still returned.

The join conditions are governed by two profile options evaluated at runtime. The first, FND_PROFILE.VALUE('ORG_ID'), filters TRX.ORG_ID to the current operating unit context. The second, ASO_PRODUCT_ORGANIZATION_ID, constrains the item master join to a specific inventory organization. Both item joins are outer joins ((+) syntax), reflecting the view's origin in an older Oracle database release where ANSI join syntax was not used.

Key Columns

• CUSTOMER_TRX_ID — Identifier of the parent receivables transaction line.
• INVENTORY_ITEM_ID — Inventory item associated with the line; the join key to the item master.
• UNIT_STANDARD_PRICE — The standard unit price for the item. This is the column most commonly referenced by users searching on this term, typically for price variance and margin analysis.
• UNIT_SELLING_PRICE — The actual unit price at which the line was sold.
• QUANTITY_ORDERED, QUANTITY_CREDITED, QUANTITY_INVOICED — Quantity measures supporting net revenue and credit reconciliation.
• SALES_ORDER, SALES_ORDER_DATE — Sales order reference and order date.
• ORG_ID — Operating unit identifier applied by the profile filter.
• DESCRIPTION — Item description from MTL_SYSTEM_ITEMS.

Common Use Cases and Queries

Typical usage includes revenue reporting, standard-versus-actual price variance, and product revenue roll-ups. The following sample retrieves revenue lines with item descriptions:

• SELECT CUSTOMER_TRX_ID, INVENTORY_ITEM_ID, DESCRIPTION, UNIT_STANDARD_PRICE, UNIT_SELLING_PRICE, QUANTITY_INVOICED FROM BIC_REVENUE_TRX_DETAIL_V;
• SELECT INVENTORY_ITEM_ID, DESCRIPTION, SUM(QUANTITY_INVOICED * UNIT_SELLING_PRICE) REVENUE, SUM(QUANTITY_INVOICED * UNIT_STANDARD_PRICE) STANDARD_REVENUE FROM BIC_REVENUE_TRX_DETAIL_V GROUP BY INVENTORY_ITEM_ID, DESCRIPTION;
• SELECT * FROM BIC_REVENUE_TRX_DETAIL_V WHERE UNIT_SELLING_PRICE <> UNIT_STANDARD_PRICE;

Note that results are implicitly limited to the operating unit set in ORG_ID and the inventory organization defined by ASO_PRODUCT_ORGANIZATION_ID, both of which must be correctly configured for the view to return data.