Scenario : You want to schedule 2-3 tasks, but you would like to define dependency among tasks. Means Task1 should be executed only after completion of Task 3 and Task 2. Advantage : You all might have heard of "Divide and Conquer Rule", So this also implements the same. Generally if you create batch to process 1000 Purchase orders then it might slow down the AOS performance and delay the overall batch performance. But if you create batch and create 10 tasks, each process 100 Purchase orders then will be fast compared to above procedure and will improve overall batch performance. How to : In Dynamics AX 2009, Batch process will make use of below tables BatchJob : Main Job scheduler, consists of task BatchTask : Task in batch which specifies what class to execute in order to achieve certain functionality. BatchConstraint : Used to build dependencies among the tasks. Create a Job, by using below code static void Batch_Creat...