Please note that JavaScript and style sheet are used in this website,
Due to unadaptability of the style sheet with the browser used in your computer, pages may not look as original.
Even in such a case, however, the contents can be used safely.


Creating a job network
| Unit job | The smallest component that is executed as a job. | |
|---|---|---|
| ERP job | The smallest component that is executed as SAP ERP. | |
| BI job | The smallest component that is executed as SAP BI. | |
| UCXSingle job | A business report can be output at any time from JobCenter by using this command. | |
| Sub JNW | The smallest component that is executed as a job network. | |
| Dialog | A part used for waiting for a response from the user. | |
| Condition branch | A part used for changing the job network flow according to the exit code of a unit job or sub JNW. | |
| Calendar branch | A part for selecting an execution flow according to the date. | |
| Parallel | Executes several jobs or sub job networks. | |
| OR branch | The subsequent parts are executed if one of the multiple branch flows finishes. | |
| Continuity | Jumps to the pre-specified unit job, and re-executes the process after that job. | |
| Sub JNW waiting | Waiting for end of a specified sub JNW. | |
| Job waiting | Waiting for end of a specified job. | |
| File waiting | Waiting for a specified file. | |
| Time waiting | Waiting for a specified time to be reached. | |
| Event transmission | A unit for transmitting an event from one job network to another job network. | |
| Event reception | A unit for receiving an event at one job network from another job network . |



The job network parts, schedule, and operating day calendar can be set up using Excel. The job network flow can also be graphically displayed in Excel, and the operating day and time can be also checked. Definition Helper can be used to maintain periodic batch job definitions, develop large-scale batch jobs, and back up definition information.
Definitions of the job network, schedule and calendar on JobCenter can be imported and exported from the GUI or the target server command line. For example, when the machine environment needs to be migrated, definition information can be selected and exported collectively, individually, or according to user specification, so that only required information for the destination machine can be imported.

The network load status is monitored and jobs are automatically dispatched to the machine with low load. In addition, jobs can be controlled by using queues such as the following.

In a cluster environment, jobs currently being executed can be taken over to another node if the current node fails. This ensures the job operation of mission-critical businesses.


The job execution status can be sent to operators.