Results for “initial_customer_trx_line_id”

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

Overview

The view APPS.ARBV_FREIGHT_CHARGES is a reporting and integration object within the Oracle Receivables (AR) module. It exposes freight line information stored against customer transactions, presenting a denormalized, read-only projection of freight charge data that combines attributes from both the transaction header and its associated freight lines. The object is documented with the status VALID and is marked as "Retrofitted," indicating it was carried forward or re-created as part of the ETRM (E-Business Suite Technical Reference Manual) documentation effort for the 12.1.1 and 12.2.2 releases.

The view is defined with the clause WITH READ ONLY, confirming that it is intended strictly for query, extraction, and reporting purposes rather than for transactional data manipulation. Its name, ARBV_FREIGHT_CHARGES, follows the conventional "ARBV" (Receivables Business View) naming standard, signalling its role as a business-facing view layered over base transaction tables.

Underlying Base Objects

According to the documented metadata, the view is defined over two referenced base objects, both exposed through synonyms:

• RA_CUSTOMER_TRX_LINES (SYNONYM) — aliased as CTL, supplying the line-level freight attributes.
• RA_CUSTOMER_TRX (SYNONYM) — aliased as CT, supplying header-level shipping attributes.

The two objects are joined on CTL.CUSTOMER_TRX_ID = CT.CUSTOMER_TRX_ID, and the view restricts rows with the predicate CTL.LINE_TYPE = 'FREIGHT'. As a result, only transaction lines explicitly classified as freight charges are returned, ensuring the view is scoped precisely to freight activity rather than all invoice lines.

Key Columns

The view exposes a focused set of columns relevant to freight reporting. Notable columns include:

• TRANSACTION_LINE_ID — the freight line identifier, mapped from CTL.CUSTOMER_TRX_LINE_ID.
• AMOUNT — the freight charge value, derived from CTL.EXTENDED_AMOUNT.
• FREIGHT_CARRIER — the carrier, sourced from the transaction header's SHIP_VIA attribute.
• SHIP_DATE — the actual shipment date, from CT.SHIP_DATE_ACTUAL.
• SHIPPING_REFERENCE — the shipping reference, mapped from CT.WAYBILL_NUMBER, which carries the waybill or tracking reference associated with the shipment.
• _LA:REASON and _LA:FOB_POINT — lookup-backed descriptive columns joined to AR_LOOKUPS for reason codes and FOB point meaning.
• Identifier columns such as CUSTOMER_TRX_ID, PREVIOUS_CUSTOMER_TRX_ID, PREVIOUS_CUSTOMER_TRX_LINE_ID, INITIAL_CUSTOMER_TRX_LINE_ID, LINK_TO_CUST_TRX_LINE_ID, and ORG_ID.
• Standard WHO columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY.

The SHIPPING_REFERENCE column is of particular interest to users searching for shipment documentation, as it surfaces the waybill number directly alongside freight amount and carrier details.

Common Use Cases and Queries

This view supports freight charge analysis, carrier reporting, and reconciliation of shipping costs against invoices. A typical query to retrieve freight charges with shipping references is:

• SELECT transaction_line_id, shipping_reference, freight_carrier, ship_date, amount, customer_trx_id FROM apps.arbv_freight_charges WHERE org_id = :p_org_id;

Analysts may filter by carrier or date range to audit freight spend, or join the view to RA_CUSTOMER_TRX_ALL to obtain invoice-level context. Because the view is read-only and built on standard transaction tables, it is suitable for custom reports, extracts, and integration interfaces that require freight detail without querying base tables directly.