Change request: data & cofile files

[Former Member]

Hello,

I have two seperate networks that connected. I need to transfer a change request from r/3 at network-a to r/3 at network-b.

Because of security reasons I can't just transfer "cofile and data" files, they have to be recognized as change requset files.

My question: is there a way to do such a check on a server that doesn't has an R/3 system (maybe with tp or something ?) or how else I can perform the check ?

Please Advice,

Dimitry Haritonov

[Former Member]

Hello gurus,

Yes! I found a way to check the files:

"With R3trans -l you can check a datafile. Use:

R3trans -l <datafile with path> If the return code is 0 or 4 then R3trans could read the datafile. The output is trans.log and contains details in case of errors, or in cas eof success the object list.

Typical errors are e.g. 'unexpected end of file'.

With tp createcofile a cofile can be created (if you want to be sure thatit is a cofile and nothing else). So you could try just to copy the datafiles and then use createcofile in order to create them locally on

the separate system. But R3trans is also needed for this and also a tp parameter file."

Ask me if you didn't understand.

Dimitry Haritonov

[Former Member]

Hi Dimitry,

what do you mean by 'they have to be recognized at change requests'. Where do they have to be recognized and how ?

I guess, what you want to achieve is having some central transport directory and publich the files from the QA system to the productive system via this directory. Or do you mean you want to transport the files using RFC ????

Regards,

Patrick

[Former Member]

Hello Patrick,

When I said "recognized" I meant: If there is a way to verify that the files are really change-request files.

The reason is explained above (two different networks, data that transported must be checked).

Regards,

Dimitry