Results for “ship_via”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RA_CUSTOMER_TRX_FRT_V is an APPS-owned view in the Oracle E-Business Suite Receivables (AR) module, documented in ETRM metadata as a Release 115 era object that remains present and valid in the 12.1.1 and 12.2.2 code lines. The view consolidates freight-related attributes of a Receivables transaction — the ship-via method, FOB point, waybill number, actual ship date, and the freight type (header-level or line-level) — alongside core transaction identifiers. Its purpose is to present a single denormalized row per customer transaction, decoding code values into their human-readable meanings so that freight information captured on the transaction can be reported or consumed by downstream integration without repeated lookups against Oracle Lookups and Order Management freight codes. Because it is a view rather than a table, it is read-only by definition and carries no independent storage or validation logic.

Underlying Base Objects

The documented view text defines RA_CUSTOMER_TRX_FRT_V over several sources, all joined with outer joins except the key drivers:

  • RA_CUSTOMER_TRX — the primary driving table, providing the transaction rows, ship-via code, FOB point, waybill number, actual ship date, salesrep, and audit columns.
  • RA_CUSTOMER_TRX_LINES — referenced in a correlated subquery on LINE_TYPE = 'FREIGHT' to determine whether the freight is attached at header or line level.
  • AR_LOOKUPS — joined twice, once for FOB point meaning (LOOKUP_TYPE = 'FOB') and once for freight type (LOOKUP_TYPE = 'FREIGHT_TYPE').
  • ORG_FREIGHT and OE_SYSTEM_PARAMETERS — used to resolve the freight code to its description via the master organization defined in Order Management parameters.

ETRM metadata further lists HR_GENERAL and HR_SECURITY as referenced package dependencies, reflecting the standard EBS security model applied to the base tables, along with the OE_SYS_PARAMETERS package behind the synonym. RA_CUSTOMER_TRX_LINES is also derived from the synonym layer.

Key Columns

Common Use Cases and Queries

The view is typically used to expose freight and shipping context for invoices without re-deriving the FOB and freight-type lookups in custom reports, AR extracts, or integration staging. A representative query retrieves freight detail for a specific transaction:

SELECT customer_trx_id, ship_via, of_ship_via_description, fob_point, al_fob_meaning, freight_type, waybill_number FROM ra_customer_trx_frt_v WHERE customer_trx_id = :p_trx_id;

For header-versus-line freight analysis, filtering on freight_type supports distribution and freight-recovery reporting. Joining the view back to RA_CUSTOMER_TRX via customer_trx_id enables full transaction detail alongside these decoded freight attributes, which is the most common pattern in custom AR reporting and interface staging logic.