Enforcing sequential execution of jobs

To control jobs which must be run sequentially, a Job Name can be specified when triggering any financial batch job. A common requirement is for A/P Voucher Generation, Freight Bill Generation, A/P Transaction Run and A/P Accrual Run to be performed sequentially because the output from one job is used as the input for the next job. With multi-threading enabled, these jobs could be executed concurrently. This may not be the desired behavior for certain requests.

To force financial jobs to be executed in a specific sequence, specify a Job Name when triggering any financial batch job. For example, if an A/P Voucher Run, a Freight Bill Generation Run, an A/P Transaction Run and an A/P Accrual Run must be run in sequence, they should be submitted with the same Job Name, such as "Financial Runs for End of June". These four jobs are executed sequentially based on the Priority and Scheduled Date Time. If there is currently an active job that refers to the same Job Name, any other jobs referencing the same Job Name is skipped until the active job completes.