Search Results extended_amount

Overview

BIC_INVLINE_V is a reporting view belonging to the Oracle EBS Customer Intelligence product family (module code BIC), which is classified as obsolete in Release 12.1.1 and 12.2.2. The view presents invoice line-level transactional data extracted from Oracle Receivables, exposing quantity, pricing, tax, and order-reference attributes in a single flattened structure. Its intended role was to feed customer intelligence analytics, data warehouse extracts, and downstream BI reporting that required invoice line detail without navigating the full Receivables table structure.

Per the ETRM documentation metadata, the view is flagged as "Not implemented in this database." This indicates that the object is documented for reference only and is not physically created in the environment from which the metadata was extracted. Organizations upgrading from earlier releases should confirm object existence before depending on it, since the BIC module is obsolete and its objects are not guaranteed to be deployed in 12.1.1 or 12.2.2 instances.

The view definition is a straightforward projection over RA_CUSTOMER_TRX_LINES_ALL, applying column aliases that map Receivables terminology to business-friendly reporting names. It contains no joins, aggregations, or filters, so each row corresponds one-to-one with a customer transaction line.

Underlying Base Objects

The view is defined exclusively over RA_CUSTOMER_TRX_LINES_ALL, aliased as CTL in the documented SQL text. No other base tables, views, or synonyms are referenced, and no joins are present. Consequently, header-level attributes such as transaction number, transaction date, bill-to customer, and currency are not available through this view alone; consumers requiring those attributes must join to RA_CUSTOMER_TRX_ALL on CUSTOMER_TRX_ID.

Because the view selects from the _ALL table rather than an org-specific variant, it does not perform any operating unit (ORG_ID) filtering. Multi-org security is therefore not enforced by the view itself and must be applied by the calling application or report, typically through a join to the transaction header or by referencing the appropriate MOAC context.

Key Columns

• CUSTOMER_TRX_ID — Identifier of the parent customer transaction (invoice, credit memo, debit memo, or chargeback).
• CUSTOMER_TRX_LINE_ID — Primary key of the transaction line; unique per invoice line.
• ITEM — Line number of the transaction line, aliased from LINE_NUMBER. Despite the alias, this is a sequence number, not an inventory item.
• QUANTITY_ORDERED — Quantity originally ordered on the line, as captured in Receivables.
• QUANTITY_CREDITED — Quantity credited against the line. This is the column most directly relevant to the user search term "quantity_credited" and is central to credit memo and return analysis.
• QUANTITY_INVOICED — Quantity actually invoiced on the line.
• UNIT_PRICE — Unit selling price, aliased from UNIT_SELLING_PRICE.
• EXTENDED_AMOUNT — Extended line amount, normally the product of quantity and unit price before tax.
• TAX — Tax rate applicable to the line, aliased from TAX_RATE.
• ORDER_NUMBER — Order reference, aliased from INTERFACE_LINE_ATTRIBUTE6. This is a descriptive flexfield attribute used to carry the originating order number into Receivables.

Common Use Cases and Queries

The view supports invoice line analysis, credit and return reporting, and price-versus-quantity comparisons. A typical query retrieves all lines for a given transaction:

• SELECT customer_trx_id, item, quantity_ordered, quantity_credited, quantity_invoiced, unit_price, extended_amount, tax, order_number FROM bic_invline_v WHERE customer_trx_id = :trx_id ORDER BY item;

To analyze credited quantities across transactions, filtering on non-zero credits isolates return and adjustment activity:

• SELECT customer_trx_id, item, quantity_credited, extended_amount FROM bic_invline_v WHERE quantity_credited > 0;

Because the view lacks header context, reporting solutions commonly join it to RA_CUSTOMER_TRX_ALL to obtain transaction date, customer, and currency, and to enforce operating unit security. Where the BIC module is not implemented, equivalent output can be produced by querying RA_CUSTOMER_TRX_LINES_ALL directly with the same column aliases.