Search Results su_bill_to_location




Overview
Explore in AI Chat

Overview

APPS.RA_CUSTOMER_TRX_V is a supplementary Oracle EBS view owned by the APPS schema and registered under FND Design Data as AR.RA_CUSTOMER_TRX_V. Oracle classifies it as a "supplementary view used to simplify forms coding," and the standard ETRM warning applies: Oracle does not recommend querying or altering data through this view, since its definition may change dramatically across minor or major releases. In practice, the view presents a denormalized, form-oriented projection of the accounts receivable transaction header (invoice, credit memo, debit memo, on-account credit, chargeback, and deposit) together with selected bill-to and ship-to address attributes.

For users searching on "su_bill_to_location," this view is significant because it exposes the bill-to and ship-to party and site-use identifiers (BILL_TO_CUSTOMER_ID, BILL_TO_SITE_USE_ID, SHIP_TO_CUSTOMER_ID, SHIP_TO_SITE_USE_ID) needed to resolve a transaction's "ship-to / bill-to location" context. The view effectively consolidates header-level AR data with customer, site, and location descriptors so that a form block or report can display an invoice with its associated addresses without navigating the underlying normalized HZ and RA tables directly.

Underlying Base Objects

The documented base objects underlying RA_CUSTOMER_TRX_V span the Receivables and Trading Community (HZ) schemas, plus several Oracle-supplied packages and views:

The view thus joins transaction headers to the HZ customer and site model, which is why it can present location-derived fields alongside financial header data.

Key Columns

Common Use Cases and Queries

The view is typically used in forms-based inquiry and reporting where a transaction must be shown with its bill-to and ship-to context. A representative query selecting transactions for a given bill-to or ship-to site use is:

  • SELECT trx_number, trx_date, term_due_date, bill_to_customer_id, bill_to_site_use_id, ship_to_customer_id, ship_to_site_use_id, invoice_currency_code FROM apps.ra_customer_trx_v WHERE ship_to_site_use_id = :site_use_id;
  • SELECT trx_number, trx_date, status_trx, complete_flag FROM apps.ra_customer_trx_v WHERE bill_to_customer_id = :cust_account_id ORDER BY trx_date DESC;

Because the view is a forms-support construct, it should be used for read-only presentation and not for direct DML. For production reporting, Oracle generally recommends querying the documented base tables (RA_CUSTOMER_TRX with RA_CUST_TRX_TYPES and the HZ address tables) to ensure stability across releases and patch levels.