Run a transformation

To run or schedule a transformation:

  1. Go to Icon shows a clipboard. Study Manager > Transformations tab.
  2. Select a transformation and click the Submit Job icon.

    Tip:

    The Submit Job icon is not active if the selected transformation has not been installed. Check the Install Status column.

    If the installation status of the transformation is Warning, you may still be able to run the batch. Check the installation log file.

  3. Enter values:
    • Submission Mode: Select one:

      • Full mode includes data deletion. Use Full mode only if you are confident that you are reloading all current data.

      • Incremental is faster and does not include data deletion.

      If you are submitting a transformation for a single table and the table is defined with Unit of Work processing, select:

      • Full UOW includes data deletion. Use Full UOW only if you are confident that you are reloading all current data for each subject or subject visit that has any data included.

      • Incremental UOW is faster and does not include data deletion.

        Note:

        Set up regular Incremental loads at frequent intervals and do Full loads at longer intervals. Oracle DMW can load direct transformations (or validation checks) quickly when done incrementally. To do this, Oracle DMW automatically generates your MAP package with additional code. For example, you may see lines with the following format in your MAP program:

        If ( execution mode = 'fast incremental' ) then
        --- modified logic
        Else
        ---original logic
        End if:
    • Force Execution: Select if you want to run the job even though the source data currency, parameter values, and the version number of the program(s) have not changed since the last run. The system uses Full mode regardless of the Submission Mode setting. Full mode includes data deletion.

      If not selected and all the conditions are the same as the last run, the system does not execute the job and returns a status of Success.

    • Submission Type:

      • Immediate Run the job once, as soon as possible.

      • Scheduled Set up a regular schedule.

      • Deferred Run the job once, at a future time.

    • Trigger Downstream Transformations and Validation Checks: Select to make this job trigger validation checks on the target model and transformations from the target model to all others that come after it, in sequence. This can happen only if the source models are set up to trigger downstream processes.