what "umod 8" stands for

[Former Member]

Hello

In a note I have warning to :

"import the transport from the attachement as client dependant with umod 8 (as this transport belongs to customizing requests)"

However when trying in stms to import an request I do not have option umod 8 (what does it stands for?). Eg.I have option " overwrite originals"... but no "umod 8"

[Former Member]

Hi

U-Modes / Unconditional Modes:

<b>

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.

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

r3trans in a SAP System

This tool r3trans does the complete transport work for tp. TP controls the transports and generates the r3trans control files, but does no database-connect itself. All the "real work" is done from r3trans.

A sample call to R3TRANS could be as follows:

(edit the following e.g. in the file /tmp/control)

EXPORT

FILE='/tmp/export'

CLIENT=<nnn>

SELECT * FROM <table> (e.g. t000)

You can start r3trans as follows:

r3trans /tmp/control

The output will be generated as follows:

/tmp/export: All exported rows of the table (in a compressed format)

trans.log: Information Output

console: Return Code of R3TRANS (should be lower than 😎

You can download latest versions of r3tans, tp in market place.find the link.

service.sap.com\swdc

Fell free to revert it back any questions.

If u get the answer pls provide the points

---venkat.