Organizing Transfers in Projects

Create Projects

A project is used to group business objects together for transfer.

For each business object type to be transferred, you have to create at least one subproject and at least one run definition and one task:

Proceed as follows:

1. On the Data Transfer Workbench initial screen, choose Create Project.

2. Enter a name and a description.

Create Subprojects

You have created a project.

The subproject is used to divide a project up. Precisely one business object type is assigned to each subproject and this business object type is transferred in this subproject. You can create several sub-projects for the same business object type within one project (for example, subprojects document data transfer from plants 1, 2 and 3).

Proceed as follows:

1. Choose Create Subproject.

2. Enter the subproject and a description.

3. Specify an object type.

Create Run Definitions

You have created a subproject.

In the run definition, you specify how the data of a subproject is to be transferred, by creating tasks and specifying the files involved. You can create more than one run definition for each subproject. Depending on the type, different methods can be used in the respective runs.

You can transfer the data in parallel by creating several run definitions with different file names in one subproject and then starting runs in parallel.

Proceed as follows:

1. Choose Create Run Definition.

2. Enter a run definition and a description.

Create Tasks

You have created a run definition.

You can use a task to specify which program is to be executed and with which attributes.

You have to select one task type (extract, map, load) for each object type you select.

Program types are assigned to each task type (BAPI, function module, batch input...). This specifies how the task is executed. Object type-specific programs must be registered for data transfer beforehand. Programs that are not intended for a specific object type do not have to be registered.

For certain object types, SAP already provides registered standard programs in the Data Transfer Workbench.

You have to register all other programs that you want to use for data transfer (see Registering Programs, Function Modules, and BAPIs).

Proceed as follows:

1. Choose Create Task.

2. Enter a task and a description, and choose the task type and program type.

   Use the input help (F4 )and the field help (F1).

   Depending on the program type (BAPI, DINP, BINP, ...), you can enter attributes that control the execution of this task.

   BAPI/IDoc

   For more information, see Data Transfer Techniques.

   Define the following attributes:

• Method

  Name of the BAPI from the BOR

  • Package size

    Number of objects forwarded in an LUW to the BAPI. The packet size affects the performance of the transfer. The bigger the packets, the less load placed on the database but the bigger the rollback area required on the database.

  • Maximum Number of Errors

    If the threshold value for the number of objects not posted by BAPI is exceeded when a task is executed, the task is terminated.

• Parallel Loading in Server Group

• Sequential Loading

• Deletion Indicator: Delete files after run?

  • Deletion indicator set

    After the input files have been completely read in and all the objects have been passed to the BAPI, the files are deleted.

  • Deletion indicator not set

    After the input file has been completely read in and all the objects have been passed to the BAPI, the input file remains. When the run is continued, this input file is used again. If an error file is created, it is not used further.

  • You can store objects that are not transferred as follows:

    • In Error Files

      If errors do occur, the task is assigned status 2. This means that when you continue with the run this task is executed again.

    • As an IDoc in the SAP system (see Status Monitor for ALE Messages)

      If errors do occur, the task is assigned status 3.

      If objects that could not be transferred are stored in the database, you can process them manually (see Status Monitor for ALE Messages). You then have to end the task. When the run is continued, the subsequent task is executed.

  • Input Files

    • Type and name of input files

    • Type and name of error files

• Batch Input (BINP)

  For more information, see Data Transfer Techniques.

  Define the following attributes:

  • Report

    Name of a program registered for this program type for generating batch input sessions.

  • Variant

    When scheduling a run, the program is started with this variant in the background.

• Direct Input (DINP)

  For more information, see Data Transfer Techniques.

  Defining attributes

  • Report

    Name of a registered program for this program type

  • Variant

    When scheduling a run, the program is started with this variant in the background.

    You can only specify a variant with programs that are started directly.

• Report (REPO)

  Defining attributes

  • Report

    Name of a registered program for this program type

  • Variant

    When scheduling a run, the program is started with this variant in the background.

• Function Module (FUNC)

  You can select the following attributes:

  • Function module

    Name of a registered function module for this program type

  • Input and Output Files

    These file names are passed to the function module.

• Syntax Check (SYNT)

  Define the following attributes:

  • Program type of load program

  • Program to load data

  • File type of file to check

  • Name of file to check

• Predefine Target Files (FINO)

  Define the following attributes:

  • Program type of load program

  • Program to load data

  • File type and name of source file

  • Type and name of target files

Copy Project Elements

You can reuse all the elements belonging to a data transfer project - from project objects, subproject objects, and run objects through to task objects. You can react quickly to changes and develop new solutions from elements belonging to earlier migration projects.

To do this, proceed as follows:

1. Select a project, subproject, run, or task and then choose the copy icon.

2. Depending on the element you selected, you have to select the relevant target for the project, subproject, or run using the input help or enter a destination for the task.

3. Choose Continue.

   Your element will be copied and will appear in the hierarchy.

Change or Delete Project Elements

You can change or delete the attributes of projects, sub-projects, run definitions, and tasks, provided that you have not yet started a run and no log exists.

Once you have executed a run, you can only change the description.

If you delete an element, any dependent elements are also deleted. You cannot delete elements if a run has not ended.

Exporting Projects into Other Systems

You can export projects, including all the dependent objects, from a source system into other systems and use them there.

In the source system:

1. Select a project that you want to export.

2. Choose Project  Export.

3. In the dialog box, choose a logical system (target system), file type, and file name.

4. Choose Continue.

Your project is exported into a file on the application server.

In the target system:

1. Select the highest level node.

2. Choose Import Project.

3. In the dialog box, choose the file type and file name.

4. Choose Continue.

   Your project will be imported from the file and will appear in the hierarchy.

Transporting Projects

You can also transport projects into other systems using the SAP transport functions.

Note that the file names specified in the tasks are not transported because the paths usually changed when you switch systems.