Search Results ship_date_actual




Overview
Explore in AI Chat

Overview

APPS.RA_CUSTOMER_TRX_FRT_V is a supplementary database view in the Oracle E-Business Suite Receivables (AR) module. It is registered in FND Design Data as AR.RA_CUSTOMER_TRX_FRT_V and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The view exposes freight, shipping, and carrier-related attributes of customer transactions — such as the actual ship date (SHIP_DATE_ACTUAL), waybill number, ship-via method, FOB point, and freight type — alongside the primary transaction identifier. Its central purpose is to simplify forms coding by presenting a denormalized, presentation-ready projection over the core transaction and transaction line tables, combined with shipping lookups and operating-unit configuration sourced from Order Management.

Oracle explicitly documents this as a "supplementary view used to simplify forms coding," with a standing warning that it is not recommended for direct querying or data alteration and that its definition may change dramatically in subsequent minor or major releases. It is therefore best treated as an internal, form-supporting construct rather than a stable integration interface.

Underlying Base Objects

According to the documented dependency information, RA_CUSTOMER_TRX_FRT_V is defined over the following base objects:

  • RA_CUSTOMER_TRX (synonym) — the Receivables transaction header table, supplying transaction identifiers, transaction type, salesrep, and audit columns.
  • RA_CUSTOMER_TRX_LINES (synonym) — the transaction line table, providing the freight and shipping detail that is joined to each header.
  • ORG_FREIGHT (synonym) — the shipping/freight organization configuration, contributing carrier and freight attributes.
  • OE_SYSTEM_PARAMETERS (synonym) and OE_SYS_PARAMETERS (package) — Order Management system parameters used to drive shipping behavior and defaults.
  • AR_LOOKUPS (view) — the Receivables lookup view supplying decoded lookup meanings such as the FOB text (AL_FOB_MEANING) and ship-via description (OF_SHIP_VIA_DESCRIPTION).
  • HR_GENERAL and HR_SECURITY (packages) — Oracle HR security and general utility packages, typically applied to enforce organization or business-group security on the returned rows.

Notably, the ETRM metadata records that RA_CUSTOMER_TRX_FRT_V is not referenced by any other database object, meaning it sits at the leaf of the dependency chain and is consumed only by forms or ad hoc queries.

Key Columns

  • CUSTOMER_TRX_ID (NUMBER) — the primary transaction identifier; the join key back to RA_CUSTOMER_TRX.
  • PREVIOUS_CUSTOMER_TRX_ID (NUMBER) — identifies a prior transaction, supporting credit or adjustment relationships.
  • CUST_TRX_TYPE_ID (NUMBER) — the transaction type of the record.
  • PRIMARY_SALESREP_ID (NUMBER) — the sales representative associated with the transaction.
  • SHIP_DATE_ACTUAL (DATE) — the actual ship date, central to freight and shipping reporting and the term the user searched for.
  • WAYBILL_NUMBER (VARCHAR2) — the carrier waybill or tracking reference.
  • SHIP_VIA (VARCHAR2) and OF_SHIP_VIA_DESCRIPTION (VARCHAR2) — the ship-via code and its decoded description.
  • FOB_POINT (VARCHAR2) and AL_FOB_MEANING (VARCHAR2) — the FOB point value and its lookup meaning.
  • FREIGHT_TYPE (VARCHAR2) — the freight classification.
  • ROW_ID (ROWID) — the unique row identifier.
  • Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Because the view exposes the actual ship date together with carrier and freight attributes, it is commonly used for shipping-information lookups on transaction forms and for freight-oriented reporting. A representative query retrieving shipping detail for a transaction follows:

  • SELECT customer_trx_id, ship_date_actual, waybill_number, ship_via, fob_point, freight_type FROM apps.ra_customer_trx_frt_v WHERE customer_trx_id = :p_trx_id;

Analysts frequently filter or sort on the searched term — for example, listing transactions shipped within a given period using WHERE ship_date_actual BETWEEN :from_date AND :to_date. Given Oracle's explicit caution about query stability across releases, production integrations should prefer the underlying base tables and lookups directly rather than depending on this view.