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 R/3 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 administration 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:

Creating 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 initial Data Transfer Workbench screen choose Create project.
Enter a name and a description.

Creating Sub-Projects

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

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

Creating 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
	LSMW		Converts the data using the LSM 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 R/3 format
LOA	BAPI	X	Loads the data into R/3 using a BAPI
	BINP	X	Loads the data into R/3 using Batch Input
	DINP	X	Loads the data into R/3 using Direct Input
	FUNC	X	Loads the data into R/3 using a function module
	REPO	X	Loads the data into R/3 using a report
AUD	FUNC	X	Loads the data into R/3 using a function module
AUD	REPO	X	Loads the data into R/3 using a report
MSC	FUNC	X	Miscellaneous functions using a function module
MSC	REPO	X	Miscellaneous functions using a report

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 F4 input help and F1 field help.

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

BAPI

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 size of the packet affects the performance of the transfer - the larger the packets, the larger the required rollback area on the database.

Error before termination

When the task is being executed, if the threshold for objects not updated by the BAPI is exceeded, the task is terminated.

Objects that were not transferred can be stored as follows:

In an error file

If errors occur, the task is assigned status 2. This means that the task is executed again when the run is continued.

An an IDoc in R/3 (see Status Monitor for ALE Messages)

If errors occur, the task is assigned status 3.

You can maually process the objects not transferred which have been saved in the R/3 database (see Status Monitor for ALE Messages). Then complete the task. When the run is continued, the next task is executed.

Type and name of input file
Delete indicators: Delete file after run?

Deletion indicator set

After the input file has been completed read in and all the objects have been passed to the BAPI, the file is deleted.

If objects that could not be transferred are stored in an error file, the error file is becomes the input file which is then used when the run is continued.

Deletion indicator not set

After the input file has been completed 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 should always set the deletion indicator, if you are working in a production system.

Otherwise there is the danger that the objects could be transferred several times to your production system, when a run is restarted.

You can only work without setting the deletion indicator in a test system.

Batch Input (BINP)

For more information see Data Transfer Techniques.

Define the following attributes:

Report

Name of a registered program to create batch input sessions for this program type

Variant

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

Status of task:

Task completed without errors
Task completed with errors
Task completed without errors, no restart

When a run is scheduled the task is completed with the selected status (independently of the actual result of the program).

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.

Status of task:

Task completed without errors
Task completed with errors
Task completed without errors, no restart

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.

Status of task:

Task completed without errors
Task completed with errors
Task completed without errors, no restart

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

Legacy System Migration Workbench (LSMW)

Define the following attributes:

LSMW project
LSMW subproject
LSMW object

An LSMW conversion object is selected by these three parameters.

For more information see Using the LSM Workbench for the Conversion

Copying Project Elements

You can reuse all the elements belonging to a data transfer project - from project objects, subproject objects, 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 select 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.

Changing or Deleting 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 therefore no log exists.

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

If you delete an object 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 here.

In the source system:

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

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

In the target system:

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

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

Result

You have created a complete and executable project.

Then you can execute Data Transfer in Runs