A:\setup.exe for SAP R/3 - Does something like that exist?

[Former Member]

I have developped a few ABAPS over time which I take with me from client to client. Everytime I have to re-create manually the program using SE38 and the upload source text feature. Screen labels I have to re-create manually. Documentation for the program does not come over. Data dictionary objects the same story, etc. etc.

I'm looking for a better way to install ABAP programs. Does SAP's transport system offer maybe any help? (Yes, an a:\setup.exe like solution would be nice. The utility would prompt your for a transport request and resolve any name clashes.)

Any suggestions for efficiently transporting ABAP programs between independent instances would be highly appreciated!

Thanks,

---Hugo de Groot

[Former Member]

hi,

I know that is possible to catch the request order file and then use that file in the smts target system, but I have never used it.

Anyway, there are some public programs that can help you in this work. One of the best ones (at least for me) is http://www.sapgenie.com/abap/abap13.htm (this one also saves and restores dynpros and pf-status).

have a nice day,

David Rodríguez

[Former Member]

David,

Thanks for the response!

I understand from a Basis guy that the request order file only works if the development class you are using is already existing in the target system. But I never had a chance to try out this method.

I will try out the public program you pointed me to. Do you know of any known issues/limitations with the public program?

Of course it would be nice if SAP provided some standard solution for this problem. I have neen looking into xApps but that solution appears to attempt to tackle a bigger problem.

Thanks,

---Hugo

[Former Member]

David,

Thanks for the response!

I understand from a Basis guy that the request order file only works if the development class you are using is already existing in the target system. But I never had a chance to try out this method.

I will try out the public program you pointed me to. Do you know of any known issues/limitations with the public program?

Of course it would be nice if SAP provided some standard solution for this problem. I have neen looking into xApps but that solution appears to attempt to tackle a bigger problem.

Thanks,

---Hugo