Search Results rma_reference




Overview
Explore in AI Chat

Overview

The POS_ASN_SHIPMENT_DETAILS_V view in the APPS schema is a reporting and integration construct within the Oracle iProcurement (ICX) product family. Its purpose is to present consolidated Advanced Shipment Notice (ASN) shipment line details, joining shipment information captured through the iProcurement shop cart ASN flow with the corresponding purchasing, vendor, receiving, tax, and freight reference data. In Oracle EBS 12.1.1 and 12.2.2, this view is particularly relevant when shipment-level cost analysis is required, since it exposes shipping-related cost columns — ACTUAL_COST, TRANSFER_COST, and TRANSPORTATION_COST — alongside quantities and unit prices. This makes the view useful to users searching for transfer_cost, because TRANSFER_COST is sourced directly from the shop cart shipment detail table and is presented here in a ready-to-query, denormalized form. The view does not store data; it is a read-only projection over a set of base tables and synonyms, and it is therefore appropriate for operational reporting, cost reconciliation, and interface extraction rather than as a transactional object.

Underlying Base Objects

The view is defined over a primary shipment table, POS_ASN_SHOP_CART_DETAILS, joined outward to the standard purchasing and reference tables. The documented base objects are:

Most vendor, category, freight, territory, and tax joins are outer joins, so absence of a matching reference row does not suppress the ASN line.

Key Columns

The cost and financial columns are central to this view's use. ACTUAL_COST, TRANSFER_COST, and TRANSPORTATION_COST capture the shipment's cost components, while QUANTITY_INVOICED multiplied by POL.UNIT_PRICE yields an extended line value. NOTICE_UNIT_PRICE records the notice price, and PO_HEADERS.CURRENCY_CODE, RATE_TYPE, RATE_DATE, and RATE support currency conversion. Descriptive attributes include WAYBILL_AIRBILL_NUM, BILL_OF_LADING, CONTAINER_NUM, TRUCK_NUM, BARCODE_LABEL, and PACKING_SLIP. Item and document identifiers include LINE_NUM, SHIPMENT_NUM, ITEM_REVISION, and ITEM_DESCRIPTION. Lineage keys such as ASN_LINE_ID, PO_LINE_LOCATION_ID, SHIP_TO_ORGANIZATION_ID, and SESSION_ID permit joins back to transactional tables.

Common Use Cases and Queries

Typical use is cost review and shipment tracking at PO line-location granularity. A user investigating transfer cost can query directly:

  • SELECT ASN_LINE_ID, PO_LINE_LOCATION_ID, SHIPMENT_NUM, TRANSFER_COST, ACTUAL_COST, TRANSPORTATION_COST FROM POS_ASN_SHIPMENT_DETAILS_V WHERE TRANSFER_COST IS NOT NULL;
  • Reconcile invoiced quantity against price: SELECT LINE_NUM, ITEM_DESCRIPTION, QUANTITY_INVOICED, UNIT_PRICE FROM POS_ASN_SHIPMENT_DETAILS_V WHERE PO_LINE_LOCATION_ID = :p_llid;
  • Currency analysis: SELECT SEGMENT1, CURRENCY_CODE, RATE, TRANSFER_COST FROM POS_ASN_SHIPMENT_DETAILS_V;
  • Carrier and freight reporting by organization and freight description.
  • Interface extraction feeding downstream receiving, logistics, or analytics systems keyed on ASN_LINE_ID.

Because all joins are defined within the view, consumers need not replicate the purchasing and reference joins, but they should filter using indexed lineage columns such as PO_LINE_LOCATION_ID to control query cost.