Skip to content

Execute Job

The Execute Job process handles the execution of a migration job. You may choose to start any job directly online or as a background job. You can also schedule the background job to run at a specified time.

Execution Job window has configuration details of the migration job for viewing purposes. Along with that, it has the Default Tab to handle parameters and Details Tab display data.

Default Tab

It is often useful to be able to enter or edit input parameters to a migration job. Default tab will allow you to do so. Especially, this allows users that do not have access to change jobs through the Migration Job form to change default values. In here you can edit default values on columns from Migration Job> File Mapping Tab or Migration Job > Source Mapping Tab with Change Default Flag set to Allowed.

This also allows to use the same job to transfer data to i.e. different sites or different companies by running the same job twice or several times with different default parameters.

Further, on jobs with Direction 'Out', you can enter a Default Where to fetch the correct selection of data for the job.

Note: The columns in this window is editing the same table and same columns as you see under File Mapping Tab or Source Mappings Tab in Migration Job Form. This means that if you plan to execute the same job several times with different default-values, you must wait until one job is finished before you edit default-values and starts the job over again.

Job Details

Details tab serves a couple of functionalities depends on the job type.

  1. To display the data in the uploaded file for an OnClient, File In type job. You have the option Unpack and check the validity of the data before you start execution.
  2. To display the results of an OnClient, File Out type job after executing. Displayed data can be export to a file after.
  3. To display the error messages after executing a job where errors have occurred.
    1. If the error is due to a faulty input file, or wrong source data, you must clear data and restart the job with corrected data.
    2. If the error is due to faulty basic data in IFS Application, you may restart the job after fixing.

Execution Actions

Start Job

You have 3 options to start the job.

Start Job Online: Start the execution job online. (Provided the file is loaded for FILE IN type jobs)

Restart Online: Once executed, but not succeeded due to some basic data issues, the job can be restarted. When you Restart a job, only rows from the Detail tab will be processed. Remember to eliminate the cause for the error-message before restarting a job. Jobs reading data from an Oracle source can only be restarted if OBJID is part of the select-list.

Background: A background job will be posted to execute the Migration Job. If the job is a long-running one, this is the best option because it will not freeze the window.

Schedule Job

Same option as in Migration Job form. Schedule to execute the job in the background for a given date, given time or weekly.

Load File

For a File In type migration Job with OnClient as file location, first, you must load the file into Data Migration. For that, you can use this action. An upload dialog will help you locate the file and upload.

If you want to inspect a server file before starting the job, you can use the same context menu to load this as well. In this case, you will have no upload-dialog, but the file will be loaded instantly (providing server path and filename is correct).

Escape characters must be properly included if column separator or string delimiter is included as data in the data file. The behaviour is similar as in comma-separated value files (i.e. CSV). For example, if the String Delimiter is a single quotation (‘) and column separator is a semicolon (;) then the escaping has to be as follows.

String Data Data with Escape characters

Note!: Load file will be enabled only for File Migration type jobs and when the detail tab is empty. If it is not available, try Clean Up first.

Export To File

The results in the Detail tab can be exported to a file using this action. Specially the results of the jobs with OnClient and FileOut can be exported to a file.

Unpack File

For debugging purpose only. If you have loaded a file into the Detail tab, you may execute this choice to check if the file has been correctly read according to line details. You can check the result in column 'Attribute string' validate before executing.

Clean Up

After executing a job where errors have occurred, you will find rows with error messages under the Detail tab of window Execute Job.

From the context menu of the upper part of the window, you may Clean Up the detail tab, i.e. delete all error rows before you start the job all over again.


Read more on Execution History and Migration Types