Capacity Values Not Passed For Multi Stop Jobs Due to Incorrect Request Schema (Doc ID 2089928.1)

Last updated on DECEMBER 17, 2015

Applies to:

Oracle Real-Time Scheduler - Version 2.2.0 and later
Oracle Utilities Mobile Workforce Management - Version 2.2.0 and later
Information in this document applies to any platform.


On : version, Scheduling

Why aren't capacity values passed for Multi Stop Jobs ?

When sending a Multi stop job to MWM/ORS with Capacity values defined, there is no error reported in the message but the capacity values are not stored on the database and are not passed to the scheduling engine. This prevents the scheduling engine from restricting activities to only those vehicles that have the capacity to fit the activity on board.


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