Data Transfer in Runs
Use
The actual data transfer from a file is carried out in a run. When the run is started, all the tasks of the run definition are carried out in sequence when the associated programs are called.
You can also use the
CCMS tools for monitoring the transfer.
Prerequisites
You have created an executable project.
Procedure
Test your project under realistic conditions in a test system, and assess hardware requirements, performance, memory requirements, and database settings.
Only execute the data transfer once testing has been successful.
You can execute any number of runs for one run definition. A run has a status and an application log. You can continue a run that was not completed.
Execute Run and Check Status
When a run is started, all the tasks are executed in sequence.
To start a run, position the cursor on the required run definition and select Start run.
After running a task of program type REPO, BINP or DINP, you must assign the status yourself. All other tasks assign their status automatically and are therefore also executed automatically in sequence, provided no errors occur.
The runs stops if an error occurs.
To process a run in the background, select Schedule run. You have to specify a job name and choose a server name. You then have to choose a start date.
Background processing is only useful if all the tasks of the run definition can run in the background.
Status information is provided for each run definition started.
Task cancelled, Task ended without errors, Task ended with errors, Task ended with errors, no restart, and Task ended manually. For more information, see the F1 help for the Status field.
If, after a run has ended, there is an error file resulting from task type LOA, this can be used for restarting the data transfer once the error has been removed.
Evaluate Log
A log is generated for each run started.
Choose Display log.
All the actions of the project run are contained in the log. Each task executed in the run can generate messages in this log. The log of the project run is also in the application log.
You can go directly to error processing from the log display by double-clicking on an error entry.
Reprocessing Runs
You can reprocess unsuccessful runs as follows:
To continue an incomplete run, correct the errors using the log, position the cursor on the run ID (for example, 003), and choose Continue run. Depending on the status of the run, either the current task is restarted (status 2) or the subsequent task is started (status 3).
If a run cannot be completed, you can terminate it by choosing Cancel run.
You can set a task that has not been completed to completed by choosing End task. When the run is continued, this task is skipped.
You can delete runs that have ended or were canceled by choosing the deletion icon.
Result
You have executed a run and, if it was completed successfully, you have transferred data to your R/3 System.
You can check this data in R/3 with a function module or a report.