You can use job management to schedule jobs based on your organizational requirements. For example, you can schedule jobs at non-peak hours to improve the overall system performance in a heavily loaded environment. A job consists of one or more sessions or shell commands, or both, that run without user interaction. The sessions and shell commands in a job can be started while you are not logged on to the ERP system. You can schedule jobs to start processes periodically, at a defined interval, or immediately. Typically, you use job management for print and processing sessions.
Job data - To create a job, you must specify basic job data and link sessions or shell commands, or both, to the job. In the basic job data, you specify whether the job is periodical. For periodical jobs, you specify how the job will be scheduled.
Shared job data tables - Typically, each company stores its own basic job data. As a result, a job runs for a particular company. However, in a job, you can also run sessions in more than one company. You can run sessions in multiple companies when the job data tables of the associated companies are physically mapped to a single main company.
Job execution - Jobs can be started in multiple ways. The job’s status defines how you can start the job. You can start the job if the job’s status is In Queue or Free.
Job history - When the execution of a job stops, for example, when the job completes successfully or when a runtime error occurs, information is written to a history log. The job history contains information, such as the date and time of the execution and the reasons why the job and its associated session ended.