The scheduled Order objects, stored in the Order Repository, maintain the schedule information for scheduled orders, as well as extra information as defined by the scheduledOrder item descriptor (for example, name and state).

The scheduledOrder item descriptor is defined in <ATG10dir>/DCS/atg/commerce/order/orderRepository.xml. By default, a scheduledOrder repository item contains the following properties:




The name that the user has assigned to the scheduled Order.


The profile ID of the user who created the scheduled Order.


The ID of the template Order that is cloned whenever the scheduled order is placed.


The state of the scheduled Order (active, inactive, or error).


The list of scheduled orders that have been placed. These Orders are clones of the template Order that have been checked out.


A string describing the Order’s placement schedule.


The next date and time that the scheduled Order should be placed.


The date and time that the scheduled Order was created.


The date and time that start the period within which the scheduled Order can be placed.


The date and time that end the period within which the scheduled Order can be placed.

Note: If unset, the scheduled Order is repeatedly placed indefinitely.


The ID of the scheduled Order object. A read-only property.


The type of repository item. This is set to scheduledOrder.


A value used to protect against data corruption that might be caused if two users attempt to edit this repository item at the same time. The system updates this read-only property automatically.


The current implementation of the scheduled order service can be configured to employ multiple threads when placing orders. By setting the parameter maxThreads to a number greater than 1, you can specify the number of threads that are started to process scheduled orders. If the maxThreads parameter is kept at the default of 1, all orders will be processed in the main thread. The optimal number of threads depends on a variety of factors, including server load, machine and database speed and the complexity of the scheduled order templates.

Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices