Ansicht
Dokumentation

Now does R3trans work? <br />Tip-No.: 1942 ( INFO1942 )

Now does R3trans work?
Tip-No.: 1942 ( INFO1942 )

PERFORM Short Reference   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Now does R3trans work?
Tip-No.: 1942

Symptom

Customer wants to/must use R3trans directly.

Cause

1. Transport services not (yet) installed at customer's.
2. Customer wants to use an R/3trans function that is not yet available
directly from the transaction.

Solution

Comprehensive written documentation exists for R3trans. We
therefore only list a short overview of the most important R3trans
functions and their handling.

I. Export:

1. Using Transaction SE01/STAR (transport and correction system),
create a transport order in which you enter objects you want to
transport. This also works if the transport system has not yet been
installed in your system.
2. Go to the operating system level and generate a control file that
will later serve as input for R3trans and which describes what
R3trans should do. It has the following contents:

export
file = '...' # name of the file to which the export should go
client = ... # client from which export should be made
use commandfile '...' #For the first generated transport order

Explanations:
You can specify any file name as the export file, even with an
absolute path. If you do not use this option, the export occurs
according to trans.dat in the current directory.
If you do not specify a client, the export takes place from client 0.
If you do not want to transport any entries from client-specific
tables, you do not need to use this option.

3. Now call up R3trans:

R3trans -w -u 1

Explanations:
The -u 1 option (-u = "always" mode) is necessary because the
transport order you generated in the system does not have the correct
status (you could not release it in the system).

It is important that your environment is set correctly, so that
R3trans exports from the correct data base.
For ORACLE: you must either set environment variable TWO_TASK
(and orasrv must run), or you must set environment variables
ORACLE_HOME and ORACLE_SID. In addition, the data base must,
of course, be running.

II. Import:

You can, of course, import the dataset you generated into the same
or a different system.

1. Generate another control file for R3trans:

import
file = '...' # same file as with export
client = ... # target client, if required

2. Call up R3trans:

R3trans -w

The environment must be correct here, as well.

The data format is release-independent - you can also use R3trans for
data migration (export from the old system using the old R3trans and
import into the new system with the new R3trans).

III Copying clients:

You can set up any mandate from another client, either for all client-
dependent tables or for a portion thereof.

1. If you want to create a new client for specific tables, it is best
if you create a new transport order (see above).

2. Generate a control file:

clientcopy
source client = ...
target client = ...
use commandfile '...' # If you have one OR
# select * # for ALL client-dependent tables
# select * from xxx # for individual tables
# select * from yyy # for individual tables

3. Call up R3trans:

R3trans -w -u 1

The environment must, of course, be correct here also.

The table entries you have generated can also be deleted again:

clientremove
client = ...
use commandfile '...' # only one of these
# select * # three lines
# select * from xyz # (see above)

Setting up and dissolving a client is also described in the
update guidelines.






TXBHW - Original Tax Base Amount in Local Currency   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4264 Date: 20240328 Time: 183733     sap01-206 ( 26 ms )