Preventing Orders For Vans Without Attributes From Being Assigned to Vans With Attributes in ORS (Doc ID 1295585.1)

Last updated on FEBRUARY 16, 2011

Applies to:

Oracle Enterprise Real Time Scheduling - Version: 10.1.0 to 10.8 - Release: 10.1 to 10.8
Information in this document applies to any platform.

Goal

The purpose of this article is to provide a solution to the business case described below.

Business Case:

Users have created vans without attributes (ex. Van A ) and vans with attributes (ex. Van B).  Orders are created and slot and booking requests are sent without R_MUST_HAVE and R_MUST_NOT_HAVE attributes.  We expect these orders to go into vans without any attribute (Van A).  However, users see that the orders are assigned to Van B also.

Solution

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