A. All are correct

B. Currently in use

C. Terminated on error

D. Are already exported

A. R3LOAD

B. R3LDCTL

A. If no job file is specified, the complete database will be exported by default

B. The existence of a matching import *.STA file identifies a restart situation, otherwise the import starts
from the first data dump file entry.

C. If JPKGCTL was used meta data and table data were put into separate dump files.

D. The existence of a matching export *.STA file identifies a restart situation, otherwise the export starts
from scratch.

A. R3SETUP/SAPINST/MIGMON generates R3LOAD command files for every *STR file

B. Optional MIGMON can be used to reduce the unload and load time significantly

C. R3SETUP generate a DBSIZE.TPL. R3SZCHK create a DBSIZE.XML for SAPINST.

D. Once the size of each table and index has been calculated, R3SETUP/R3SZCHK computes the
required database size.

A. Homogeneous system copy.

B. Heterogeneous system copy.

C. For both systems

A. Size of the target databases

B. Current hardware {RAM, C.P.US, Disk sub-system}

C. JAVA/Perl installable for migration tools {Customer policy}

D. Tables in ABAP Dictionary but not in DB or vice versa

A. SAPINST

B. R3SETUP

A. Export data from the SAP source system

B. A,H,B,C,J,E,D,F,G,I

C. H,A,C,B,J,D,E,F,G,I

D. Perform the follow- up tasks

E. Install migration tools and prepare source system

F. Configure the test environment

G. Install the database software in the target system

H. Install the SAP products on target system

I. Generate the target database

J. A,C,B,J,E,D,F,G,H,I

K. A,B,C,J,E,D,F,G,H,I

L. Load the data export into the target database

M. Transport/share the data export to the target system

N. Perform extensive tests on the migrated system

A. R3LOAD

B. R8SEJP (3.11 4.6J) /SAFINST

C. R3SCUK

D. JLOAD