New Locations Created in EBS Used For Pool Point And Xdock Are Not Found In OTM
(Doc ID 2861901.1)
Last updated on AUGUST 27, 2022
Applies to:
Oracle Shipping Execution - Version 12.2.6 and laterOracle Inventory Management - Version 12.2.6 and later
Oracle Transportation Management - Version 6.3.1 and later
Information in this document applies to any platform.
Goal
Locations created in EBS Inventory that are used as pool point locations are not being synched with Oracle Transportation Management(OTM).
These locations are not used on sales orders and therefore have no customer site tied to it.
Pool point and Xdock locations are locations that come in between the source and destination for any order.
----
In EBS:
Inventory or Purchasing Responsibility
Setup > Organizations > Locations
Enters address and shipping address details
Select Global Scope and save.
----
----
In OTM, these locations can be found and managed in the Shipment Management > Location Management Form.
----
If the location is NOT a ship to and/or ship from on a delivery, but rather a pool point or xdock then how can locations be sent when Shipping Transportation Outbound Interface is NOT applicable in these scenarios?
What method are these types of locations automatically synchronized with OTM?
Or is it expected for these types of locations to be manually entered in both EBS and OTM and it is not expected or as per functionality that they are automatically synchronized?
Solution
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
Goal |
Solution |
References |