A Batch Job Stream Definition can be transferred from oracle scheduler to the new SaaS batch scheduler. When transferred, a scheduler batch stream definition is created with the same name. The scheduler batch stream definition is created in Pending state. All details can be reviewed, any changes can be made and activated in the new SaaS batch scheduler.

The batch job stream definition is inactivated in the oracle scheduler once it’s transferred to the new SaaS batch scheduler and will be renamed suffixed with “_​Old”.

When transferring job streams from oracle scheduler to new SaaS batch scheduler, it is recommended to transfer when job streams are not running in the oracle scheduler. Additionally, if a job stream with same name exists in the SaaS batch scheduler, the job stream in oracle scheduler cannot be transferred to SaaS batch scheduler.

Scheduler Programs: If batch job stream definition has a scheduler program with business date set, this will be copied onto scheduler batch stream definition only if there is one of them. If there is more than one scheduler program with business date set, then the business date is left blank on scheduler batch stream definition so user can populate it manually.

If batch job stream definition has a scheduler program with custom parameters for a batch control, these custom options are transferred to the new batch scheduler. A batch scheduler batch control is created for these custom options with it’s name suffixed with “_​NEW”.

Sub-streams:  If the stream has sub-streams, then it is recommended that sub-streams are transferred first manually before transferring the main stream. From this process perspective, the batch control to submit sub-stream K1-EXDJS is replaced with K1-RNSBS on the batch job stream definition step batch control. It is customer's responsibility to populate the batch parameter on K1-RNSBS batch control.

If however, K1-EXDJS is referenced on batch job stream definition step using scheduler program, then this custom batch control is transferred to new batch scheduler along with custom batch parameters. In this case it is assumed that the sub-stream mentioned as custom batch parameter was previously transferred to new batch scheduler.