Organizing the Transfer in Projects (SAP Library

Organizing the Transfer in Projects

Use

Using the project management in the Data Transfer Workbench, you can clean and extract the transfer data, map it to the target structures, create a data transfer file in SAP format, and load the data into your SAP System.

Prerequisites

You know the data structures to transfer and the target structures.

You have identified the programs, function modules, and BAPIs provided by SAP or you have developed and registered your own (see Developing Programs, Function Modules and BAPIs and Registering Programs, Function Modules and BAPIs).

Procedure

A data transfer project consists of the following objects:

Subprojects
Run definitions
Tasks

These objects are displayed in a hierarchy in the project management of the Data Transfer Workbench. The left frame contains the hierarchy of the project elements; the right frame contains the details of the selected object. You can change the size of the frames by dragging the borders with the mouse.

You can create, change, display, copy, and delete projects, sub-projects, runs, and tasks. You can also transport whole projects into other systems.

To create a complete project, choose Tools ® Data Transfer Workbench and then follow these steps in the order specified:

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 sub-project and at least one run definition and one task:

Proceed as follows:

On the Data Transfer Workbench initial screen, choose Create project.
Enter a name and a description.

Create subprojects

You have created a project.

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

Proceed as follows:

Choose Create sub-project.
Enter a sub-project and a description, and choose an object type.

Create run definitions

You have created a sub-project.

In the run definition, you specify how the data of a sub-project is to be transferred, by creating tasks and specifying the files involved. You can create more than one run definition for each sub-project. 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 sub-project and then starting runs in parallel.

Proceed as follows:

Choose Create run definition.
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 specific 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).

Task Type	Program Type	Registration required?	Description
EXT	FUNC	X	Extracts the external data using a function module
EXT	REPO	X	Extracts the external data using a report
PUR	FUNC	X	Cleans the data using a function module
PUR	REPO	X	Cleans the data using a report
MAP	FUNC	X	Maps the data using a function module
	REPO	X	Maps the data using a report
	DMCW		Converts the data using the DMC Workbench
CHK	FUNC	X	Checks the data using a function module
	REPO	X	Checks the data using a report
	SYNT		Checks that data is in SAP format
LOA	BAPI	X	Loads the data using a BAPI
	BINP	X	Loads the data using batch input
	DINP	X	Loads the data using direct input
	FUNC	X	Loads the data using a function module
	REPO	X	Loads the data using a report
	IDOC	X
AUD	FUNC	X	Checks the loaded data using a function module
AUD	REPO	X	Checks the loaded data using a report
MSC	FUNC	X	Miscellaneous functions using a function module
MSC	REPO	X	Miscellaneous functions using a report
SPL	FINO		Splits a file in fixed, predefined target files

Proceed as follows:

Choose Create task.
Enter a task and a description, and choose the task type and program type.
Maintain the task attributes.

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

Packet 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.

Caution

Always set the deletion indicator when you are working in a productive R/3 system.

Otherwise the objects may be transferred several times to your productive system when a run is restarted.

You do not have to set the deletion indicator in a test system.

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 the task is executed again when the run is continued.

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.

Define the following 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)

Define the following 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.

Proceed as follows:

Select a project, sub-project, run, or task and then choose the copy icon.
Depending on the element you selected, you have to select the relevant target for the project, sub-project, or run using the input help or enter a destination for the task.
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.

Export 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:

Select a project that you want to export.
Choose Project ® Export.
In the dialog box, choose a logical system (target system), file type, and file name.
Choose Continue.

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

In the target system:

Select the highest level node.
Choose Import project.
In the dialog box, choose the file type and file name.

Choose Continue.

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

Transport 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.

Result

You have created a complete and executable project.

You can now execute data transfer in runs.