cancel
Showing results for 
Search instead for 
Did you mean: 

Transportation in Unix o.s level

Former Member
0 Kudos

I want do transportation in o.s level give the commonds ( My o.s is Unix )?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear Damodar ,

The Datafile and Cofile foldes in appl server(\usr\sap\trans)

add this request to buffer from command prompt

TP ADDTOBUFFER <REQUEST NO> SID PF=
USR\SAP\TRANS\BIN\TPPARAM_PFL

Then

TP IMPORT <REQUEST NO> SID CLIENT=XXX PF=
USR\SAP\TRANS\BIN\TPPARAM_PFL

Get back to me if you need further assistance !

Regards,

Santosh

Former Member
0 Kudos

Hey Buddy,

Even take care of unconditional mode too.

Use the Santosh's commands and specify uncondittional modes too if you want to specify some conditions.

TP IMPORT <REQUEST NO> <uncondiational mode > SID CLIENT=XXX PF=
USR\SAP\TRANS\BIN\TPPARAM_PFL

Here is brief about U Modes

U-Modes / Unconditional Modes:

The following umodes are available during exports:

1: Ignore the incorrect status of the transport request

8: Allow direct selection of forbidden tables.

Some tables are part of complex objects and generally cannot be exported alone.

The following umodes are available during imports:

0: overtaker, leave the respective task in the buffer, mark it to be imported again (1 or I).

1: repeat the import of the transport request from the beginning.

2: overwrite original objects.

3: not used any more

4: not used any more

6: overwrite repaired objects (that are object being in a unconfirmed repair).

8: ignore restrictions arising from table classes

9: ignore that this type of transport request currently may not be imported

I (in buffer only): repeat the import of the transport request from the beginning. This umode normally only appears in the buffer when umode 0 has been used.

J (in buffer only): repeat the import of the transport request into the respective client from the beginning. That means for example that client independant objects are not imported again. This umode normally only appears in the buffer when umode 0 has been used.

F (in buffer only): buffer entry is at a wrong position. A subsequent (implicit) addtobuffer will correct that later. This umode normally only appears in the buffer of delivery systems when umode 0 has been used.

D (in buffer only): that is not a umode, but the SPAM-tag, this can only be set with the option tag=SPAM.

X (in buffer only): that is not a umode, but the USER-tag, this can only be set with the option tag=X.

N (in buffer only) no delivery. This flag normally is set by the TMS workflow during their addtobuffer commands. However the flag will not be written to the buffer, when the respective buffer entry was already found in the buffer. If the flag is set tp does not deliver the respective buffer entry. In addition buffer entries with all step completed except the delivery step but with umode 'N' set will be regarded as completely imported.

Q (on command line only) ignore inactive entries. Available as of tp version 287.00. This flag is normally set by the TMS workflow only. Without this option tp will stop an import if it finds inactive entries in the buffer (See Quality assurance functionality.)

Regards

Vivek

Former Member
0 Kudos

In this commond line what is "PF" and why we have to give that USR/SAP/TRANS/BIN/TPPARAM_PFL

Former Member
0 Kudos

pf will specify the transport profile.

USR/SAP/TRANS/BIN/TPPARAM_PFL - This is the complete path of transport profile

Why do we need to specify this? - So that tp gets recognized.

Cheer!

Bidwan

Former Member
0 Kudos

Hi, I wanna import a request that is already imported, I tried to use the tp import like you wrote: with umode 1 for reimport the request

tp import <request number> 1 <SID> client=xxx I'm working with a 4.6C

but it doesn't works

Thats the result: What`s wrong?

This is tp version 305.13.23 (release 46D) for ANY database

ERROR: : parameter umode=1 has wrong length

Usage of command IMPORT:

tp IMPORT <TR>|ALL <SAPSID> [options ...]

Runs all steps neccessary for a complete import of <TR> into <SAPSID>.

Options:

U<k>[<l>..] specify unconditional mode(s) <k> [<l>..]

client<n>|client=<n> use client <n>

clires=<list of clie consider only the clients in the list

defaultclient=<n> buffer entries with no client are treaten as client=<

n>

The options clires and defaultclient are only possibl

e with ctc=1.

With ctc=1 'client=<n>' is handled as a shorthand of

'clires=<n> defaultclient=<n>'

tag=SPAM|X handle only tagged buffer entries

proj=<PROJECT> restrict action on project <PROJECT>

pf=<TPPARAM> specify a parameter file

silent redirect stdout to dev_tp in current directory

-D"<entry>" specify a parameter for tp

-t<k> specify a trace level for tp

tf=<filename> specify the name of a trace file for tp

shdwtadir=<tabname> specify the name of a shadow TADIR

Description of arguments:

<TPPARAM> (complete) path of a tp parameter file

<entry> a parameter description as in a tp parameter file

<TR> transport request, e.g. C11K904711

<SAPSID> R/3 system's name, (target or source whatever is appropriate)

<k>,<l> digits, i.e. 0,1,2,..,9

<n> a number between 000 and 999

<PROJECT> A project defined in WBO/TMS

-


tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0206

tp finished with return code: 206

meaning:

parameter %s has wrong length

Answers (0)