Results for “ar_line_freight_v”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AR_LINE_FREIGHT_V is a seeded Oracle E-Business Suite view owned by the APPS schema within the Oracle Receivables (AR) module. Its purpose is to identify invoice lines that are eligible for freight charge assignment — specifically, lines that do not already have a related freight line attached to them. The view restricts its result set to transactional lines only (excluding tax, freight, and other non-line components) and applies business rules that govern when freight may legitimately be linked to a line.
The view is documented in the ETRM as a Release 10SC-era object, meaning it predates the 11i and R12 data models and has been retained for backward compatibility. In 12.1.1 and 12.2.2, the view continues to exist as a VALID object in the APPS schema and is referenced by AutoInvoice freight handling logic, freight defaulting routines, and certain diagnostic or reporting queries. Its practical value lies in its self-join against RA_CUSTOMER_TRX_LINES, which encapsulates the "freight eligibility" rule set that would otherwise require verbose NOT EXISTS logic in every calling program.
Underlying Base Objects
The ETRM documents three referenced base objects:
- RA_CUSTOMER_TRX_LINES (accessed via synonym) — the primary transactional table holding all invoice, credit memo, and debit memo lines, along with their LINE_TYPE classification (LINE, TAX, FREIGHT, etc.). The view queries this table twice: once as CTL for candidate lines, and again as CTL2 or PREV_CTL for the freight-existence checks.
- AR_MEMO_LINES (accessed via synonym) — defines memo line types used in credit memo generation. The view joins to this table when a candidate line carries a MEMO_LINE_ID, ensuring freight is only offered for memo line types of 'FREIGHT' or 'LINE'.
- MO_GLOBAL (package) — the Multi-Org access control package. Although not directly referenced in the view text excerpt, MO_GLOBAL participation reflects the view's dependence on operating unit context when queried from a multi-org enabled environment, ensuring only lines belonging to the caller's accessible organizations are surfaced.
Key Columns
- CUSTOMER_TRX_ID — the transaction header identifier (invoice, credit memo, or debit memo) to which the eligible line belongs.
- CUSTOMER_TRX_LINE_ID — the unique identifier of the eligible line itself; used as the link target when creating a freight line via LINK_TO_CUST_TRX_LINE_ID.
- LINE_NUMBER — the user-visible sequence number of the line on the transaction.
- DESCRIPTION — line description text, useful for user-facing freight entry forms.
- INVENTORY_ITEM_ID — the inventory item associated with the line, if any; freight defaulting may vary by item.
- MEMO_LINE_ID — the memo line identifier for credit memo lines, used to validate that freight is permitted on the given memo line type.
Common Use Cases and Queries
The view is typically consumed by freight entry forms, AutoInvoice validation routines, and ad hoc reporting where the requirement is to list lines still eligible for freight. A representative query follows:
SELECT customer_trx_id, customer_trx_line_id, line_number, description, inventory_item_id, memo_line_id FROM apps.ar_line_freight_v WHERE customer_trx_id = :p_trx_id ORDER BY line_number;- Diagnostic query to find all eligible freight lines across a date range by joining to RA_CUSTOMER_TRX_ALL on CUSTOMER_TRX_ID.
- Integration scenario in which an external freight calculation system retrieves candidate lines, computes freight, and returns update instructions keyed on CUSTOMER_TRX_LINE_ID.
Because freight eligibility rules (line type, previous transaction linkage on credits, and memo line restrictions) are embedded in the view definition, custom code should query AR_LINE_FREIGHT_V rather than reimplementing the logic. Note that this view returns no data when the underlying transaction has been fully freighted, making it unsuitable as a historical freight report; RA_CUSTOMER_TRX_LINES with LINE_TYPE = 'FREIGHT' should be used for that purpose.
-
View: AR_LINE_FREIGHT_V 12.1.1
(Release 10SC Only)
APPS.AR_LINE_FREIGHT_V·↳ AR_MEMO_LINES·↳ MO_GLOBAL·↳ RA_CUSTOMER_TRX_LINES·Explore AR module →
-
View: AR_LINE_FREIGHT_V 12.2.2
(Release 10SC Only)
APPS.AR_LINE_FREIGHT_V·↳ AR_MEMO_LINES·↳ MO_GLOBAL·↳ RA_CUSTOMER_TRX_LINES·Explore AR module →
-
VIEW: APPS.AR_LINE_FREIGHT_V 12.2.2
-
VIEW: APPS.AR_LINE_FREIGHT_V 12.1.1
-
SYNONYM: APPS.AR_MEMO_LINES 12.2.2
-
SYNONYM: APPS.AR_MEMO_LINES 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - AR Tables and Views 12.2.2
Territory information
-
eTRM - AR Tables and Views 12.1.1
Territory information
-
eTRM - AR Tables and Views 12.1.1
Territory information
-
eTRM - AR Tables and Views 12.2.2
Territory information