Question:
Hi,
We made a system copy from the Productive system into our Development system. Now we need to import into our Development system some orders already released in this system but that after the system copy doesn't exist in the Development system (we just have the data and the cofile files at operating system level). Is there any way to view the contents of the transport order?? We add it to the buffer with TMS but if we try to see its contents it gives an error...
Thanks in advance and best regards,
Jon Larrucea
Answer:
Sorry to tell you this, but the administrationdata of the transport-requests are stored on the DEV (not in the seperate transportrequests) and this has been overwritten by the PRD to DEV systemcopy. Getting it back is a hell of job. There is an OSS-note about this problem, but I don't know the number and do know that it wants you to execute some preparationactions before overwritting the DEV, so it is too late for you. Unless, and I think that that is the only option, you do a restore of the DEV.
It is probably easier to manualy recreate the orders. Good luck.
_________________
Best regards, Tim van Steenbergen
Answer:
Hi Jon
You can do this with "tp getobjlist <transportrequest>"
best wishes
MAS
Answer:
OSS note 130906 explains how to keep versions.
SAP Note No. 130906 27.01.2003 Page 1
________________________________________________________________________
Number 130906
Version 7 from 09.08.2001
Status Released for Customer
Set by 08.08.2001
Language EN
Short text How can versions be transported?
Responsible SAP AG
Component BC-CTS
Change and Transport System
________________________________________________________________________
Long text
Symptom
You want to copy the versions of the repository objects from one R/3
System into another, for example because you are planning to copy your
production system to your development system.
Such a procedure does not correspond to the strategy recommended by SAP,
to always retain the development system.
When you delete the development system, important information is lost,
among other things the complete version history of all repository
objects. Since the version history of the changed SAP objects is
particularly important for later upgrades, a workaround is described
here with which the complete version database of the development system
can be exported and imported again after the system copy.
Please note that no change request data is copied in this case.
References from the version database to change requests will only remain
intact if the corresponding change requests were previously included in
the copied production system.
Furthermore you should note that the versions from the copied system are
lost completely with this procedure.
Additional key words
Cause and prerequisites
Solution
Caution: You can only transport ALL versions. All versions existing in
the import system are deleted!
The import and export is only possible with R3trans or database
resources. The import and the export with R3trans is described in this
note.
I) Before the system copy: Export the version database
1) Create a control file for the export with the following contents
export
file = '...' # name of the file into which the export should be
carried out
delete from vrsd
select * from vrsd
delete from vrsx
select * from vrsx
delete from vrsx2
Page 2
select * from vrsx2
delete from vrsmodisrc # table necessary as of release 4.5A
select * from vrsmodisrc # table necessary as of release 4.5A
delete from vrsx3 # table necessary as of release 4.6A
select * from vrsx3 # table necessary as of release 4.6A
Remark: The lines containing select and delete are no SQL statements,
having no effect on the data in the export system.
2) R3trans call for export:
R3trans -w <log file> <name of the control file Export>
II) After importing the system copy
3) Create a control file for the import with the following contents
import
file = '...' # same file as for the export
4) R3trans call for import:
R3trans -w <log file> <name of the control file Import>
If you need additional information on R3trans, refer to Note 1942.
Source code corrections
________________________________________________________________________
Note is release independent
________________________________________________________________________
Snowy
Answer:
Thank you very much for the "tp getobjlist" command and the note, I will apply it in our next system copy...
Thanks!!!
Jon