Updating Carrier/Ship Method On Delivery Does Not Cascade To the Delivery Details in the Shipping Transaction Form (Doc ID 806783.1)

Last updated on AUGUST 31, 2016

Applies to:

Oracle Shipping Execution - Version 11.5.10.2 to 12.2.2 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
Oracle Shipping Delivery Based - Version: 12.0.4
Form:WSHFSTRX.FMB - Shipping Transactions Form
***Checked for relevance on 10-Sep-2012***


Symptoms

If the Freight Carrier or Ship Method is updated on the delivery via the wsh_deliveries_pub.create_update_delivery API or manually in the Shipping Transaction Form, the new values do not cascade to the delivery details.

-- Steps To Reproduce:--

  1. Creation and booking of order
  2. Release the sales order
  3. Perform pick confirm using API inv_replenish_detail_pub.auto_pick_confirm
  4. Update ship method using API wsh_deliveries_pub.create_update_delivery/ or manually in the shipping transaction form
  5. Perform the ship confirm using API or via the application


However ship confirm does not occur when delivery grouping criteria includes Ship Method. The following error is raised:

"W:The Ship Method derived is different from the original Ship Method 000001_CEVA_T_LTL"

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms