Search Results movement_id

Overview

The IBE_RA_CUSTOMER_TRX_LINES_V view belongs to the Oracle iStore (IBE) module and exposes invoice line details for post-sales customer interactions. Its documented purpose is to retrieve the line-level composition of a receivables transaction so that iStore can present invoice, credit memo, and debit memo lines within a customer-facing self-service context. The view is a reporting and integration convenience layer rather than a transactional object: it consolidates line attributes from the Receivables customer transaction line model into a single, presentation-oriented projection.

The object is a read-only database view, and the ETRM metadata notes that it is "Not implemented in this database" in the documented environment. This means the view exists as a shipped definition but may not be deployed or populated in every instance, and its availability depends on whether the iStore post-sales components have been installed and configured.

Underlying Base Objects

The documented view text selects primarily from RA_CUSTOMER_TRX_LINES_ALL, aliased as CTL, which supplies the core invoice line columns such as CUSTOMER_TRX_LINE_ID, DESCRIPTION, UOM_CODE, and LINE_TYPE. A self-join to the same table via the CTL2 alias resolves the LINE_NUMBER through a DECODE on LINK_TO_CUST_TRX_LINE_ID, allowing credit or adjustment lines to inherit the line number of the transaction line they reference. The view also joins to RA_CUSTOMER_TRX_ALL (aliased CT) to obtain INVOICE_CURRENCY_CODE, which drives currency formatting through FND_CURRENCY.SAFE_GET_FORMAT_MASK, and to the unit of measure reference via UOM to derive UNIT_OF_MEASURE. A lookup join to the AR_LOOKUPS table, aliased AL_LINE_TYPE, returns the MEANING of the LINE_TYPE code.

Because the view relies on RA_CUSTOMER_TRX_LINES_ALL and RA_CUSTOMER_TRX_ALL, any row visible here corresponds to a committed Receivables transaction line. The absence of documented base objects in the ETRM metadata record indicates that the dependency graph is not formally cataloged, but the embedded view text confirms the Receivables and lookup dependencies.

Key Columns

• CUSTOMER_TRX_LINE_ID — Primary identifier of the invoice line; the join key to the underlying Receivables line record.
• CUSTOMER_TRX_ID — Identifier of the parent transaction header in RA_CUSTOMER_TRX_ALL.
• LINE_NUMBER — Display line number, resolved through the link to the referenced credit or adjustment line when applicable.
• LINE_TYPE and MEANING — The line type code and its decoded lookup meaning from AR_LOOKUPS.
• QUANTITY, QUANTITY_ORDERED, QUANTITY_CREDITED, QUANTITY_INVOICED — Quantity measures; QUANTITY uses NVL to prefer QUANTITY_CREDITED over QUANTITY_INVOICED.
• UNIT_SELLING_PRICE, EXTENDED_AMOUNT, REVENUE_AMOUNT — Monetary values formatted as character strings using the parent transaction's currency code.
• INVENTORY_ITEM_ID and ITEM_CONTEXT — Inventory item reference and the context describing the item association.
• SALES_ORDER and INTERFACE_LINE_ATTRIBUTE7 — Order reference and, for ORDER ENTRY context, the associated order number.
• LINK_TO_CUST_TRX_LINE_ID, PREVIOUS_CUSTOMER_TRX_LINE_ID, INITIAL_CUSTOMER_TRX_LINE_ID — Linkage columns supporting credit, adjustment, and lineage tracing.
• ACCOUNTING_RULE_ID and related rule columns — Revenue recognition rule and its duration, start date, and processing status.

Notably, the view does not expose a SOLD_TO_CUSTOMER_ID column. Identifying the sold-to customer requires joining through the parent CUSTOMER_TRX_ID to RA_CUSTOMER_TRX_ALL, where SOLD_TO_CUSTOMER_ID is maintained.

Common Use Cases and Queries

A typical use is retrieving invoice line detail for a given transaction in a customer self-service screen or report. The following query joins back to the parent transaction to supply the sold-to customer, since the view itself omits that column:

• Invoice line detail for a customer: SELECT v.customer_trx_id, v.line_number, v.description, v.quantity, v.extended_amount FROM ibe_ra_customer_trx_lines_v v WHERE v.customer_trx_id = :p_trx_id ORDER BY v.line_number.
• Sold-to customer lookup: SELECT v.customer_trx_line_id, v.line_number, ct.sold_to_customer_id, ct.invoice_currency_code FROM ibe_ra_customer_trx_lines_v v, ra_customer_trx_all ct WHERE v.customer_trx_id = ct.customer_trx_id AND ct.sold_to_customer_id = :p_customer_id.
• Credit line tracing: SELECT customer_trx_line_id, link_to_cust_trx_line_id, previous_customer_trx_line_id FROM ibe_ra_customer_trx_lines_v WHERE link_to_cust_trx_line_id IS NOT NULL.

Because monetary and price columns are returned as formatted character strings, aggregations should be performed against the base RA_CUSTOMER_TRX_LINES_ALL table rather than this view. Use the view for display, drill-down, and integration presentation where formatted values and decoded meanings are required.