MWM/ORS Site Address Updates Will Not Be Sent To The Scheduler If Geocoding Is Not Enabled
Last updated on JULY 24, 2014
Applies to:Oracle Real-Time Scheduler - Version 2.1.0 and later
Oracle Utilities Mobile Workforce Management - Version 2.1.0 and later
Information in this document applies to any platform.
While using Site Delay or 'Force Use of Site Functionality' Scheduler Configuration parameter for Site Matching, Address updates are not sent to SMAuto and the SiteID is not updated.
Follow this scenario:
1) Create two activities with differing site address details (example, 1 Main St. Apt A and 1 Main St, Apt B) and assign both to the same shift. Each activity will have a different start time since they are on different sites.
2) Update one of the activities' site address so both have the same site address. (example, 1 Main St. Apt A and 1 Main St. Apt A)
Result: The SiteID in the Scheduler is not updated and therefore the orders are not Site Matched and both will still has different start times. It appears that the manual update to the site address on ORS didn't reach smAuto.
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