Introduction › Move Request Progression › Move Processing Cycles

Move Processing Cycles

Move Processing Cycles provide a conceptual framework for evaluating your Production turnover requirements. Move Requests are grouped together in cycles based on common timing requirements. For example, you might establish the following types of Move Processing Cycles:

• Schedule Move Requests for batch applications at noon, but schedule Move Requests for your online system for midnight, after the online system has come down. Establish different Move Processing Cycles for each group of Move Requests and schedule each cycle to run daily at the appropriate time.
• Provide for emergencies, for Move Requests that must be processed immediately, without regard to the status of processing for regularly scheduled Move Requests. Establish a Move Processing Cycle for emergency Move Requests only. That cycle is run on demand only when you must process an emergency Move Request. The normal cycle is run on a regularly scheduled basis.
• If some of your Move Requests depend on input from a source that cannot be regulated by time, establish a Move Processing Cycle that can be run regularly, but not at a preset time.

You can establish distinct Move Processing Cycles to be run periodically according to a schedule or on-demand at your site. Each cycle represents a different scheduling requirement for Move Request processing.

If you do not set up Move Processing Cycles on your own, CA‑PanAPT uses a single cycle indicated by a Move Type of M. This is the default value for all panels.