Updating Carrier/Ship Method On Delivery Does Not Cascade to Delivery Details - Ship Method derived is different from the original Ship Method
(Doc ID 806783.1)
Last updated on JULY 12, 2020
Applies to:Oracle Shipping Execution - Version 126.96.36.199 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
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:--
- Creation and booking of order
- Release the sales order
- Perform pick confirm using API inv_replenish_detail_pub.auto_pick_confirm
- Update ship method using API wsh_deliveries_pub.create_update_delivery/ or manually in the shipping transaction form
- 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:
The Ship Method derived is different from the original Ship Method 000001_CEVA_T_LTL
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document