How does Import Shipping Location Concurrent Program Work ?
(Doc ID 436274.1)
Last updated on JULY 23, 2017
Applies to:Oracle Shipping Execution - Version 18.104.22.168 to 12.2.6 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
*** Checked for relevance on 22-JUL-2017 ***
Import Shipping Location Concurrent Program
Currently there is a customer created in an instance which shows ship to address as 'A'
When creating an order, the ultimate ship to is showing different address compared to the customer screen
Customer location in HZ_location got created in 01/Apr/2000.
Shipping location got created in wsh_location in 10/Apr/2004.
The customer location HZ_location got updated on 15/Apr/2007
Sales order is created for customer on 17th Apr 2007.
Since there was a location record inserted for the above, the old value is displayed in ultimate_ship_to location.
What happens if on the WSH_LOCATIONS table there is a valid ship to address, which is different from the HR/HZ LOCATIONS ?
Does the job just import everything on HR/HZ LOCATIONS to WSH_LOCATIONS overwriting everything that is on there already ?
If the customer has an address but also has a different shipping address ,would the running of the Import Shipping Location Concurrent program cause the shipping address to be lost and revert back to the customers address ?
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