Part 3 – Enable Transport System on Netweaver 7.01 Trial
In order to create a more realistic development environment, along with other good reasons, it is a good idea to enable the transport management system (TMS) in netweaver 7.01 trial. By default the TMS does not work in this version (or at least it didn’t work in mine), but it doesn’t take much to get it up and running, if you know how to do it…
I followed a very useful blog by Manfred Lutz called ABAP Trial Version for Newbies: Part 8 ‘Exporting development objects from SP8′ which along with the comments and other forum posts, helped me to get the TMS working.
I suggest you follow Manfred’s blog first to see if his approach works – If so, you’re in luck. If not, I’ll help you out… My problem was that I got a TP_CANNOT_CONNECT_SYSTEM error when tryin got distribute the settings.
If you have a closer look, there is an ABAP RFC connection called TMSADM@NSP.DOMAIN_NSP (Transaction SM59). When you look at the settings, it refers to a host called ‘PWDF3101′ – This is incorrect but we cannot change it here because the RFC is locked for editing. This is a system generated RFC. Here’s how to fix it:
You need to make sure that your host file is configured correctly. Go to C:\Windows\System32\drivers\etc\hosts and open it with notepad. Either make sure that it exists, or add an entry to map your computer name to the correct IP address:
K5ERP-SERVER localhost
Note that K5ERP-SERVER should be replaced by your computer name. Save this and restart the computer.
After restarting and firing up the SAP server using MMC console, go to transaction STMS and click on the “Overview->Systems” menu. Highlight the NSP line and go to the “SAP System->Change” menu. Go to the “Communication” tab and enter your computer name as the target host. Go to the “Transport Tool” tab and enter your computer name as the DBHOST. Also change the TRANSDIR to match your computer name like \\k5erp-server\sapmnt\trans\ where “k5erp-server” is the computer name. When done click save and it should all now be working!
Now you can follow the rest of Manfred’s blog to find out how to save your development objects to transports and then export them from your system into another SAP system.
This is part of a series: Netweaver 7.01 ABAP Trial Tips (Series)
[...] This post was mentioned on Twitter by Tom Barr, Jan Penninkhof. Jan Penninkhof said: RT @davidbann: New blog post – Enable Transport System on Netweaver 7.01 Trial (http://bit.ly/3OQYKN) << Great hack. Will try this out soon! [...]
[...] Part 3 – Enable Transport System on Netweaver 7.01 Trial RSS feed Articles in this seriesPart 4 – Configure the Workflow Engine in Netweaver Trial 7.01Part 3 – Enable Transport System on Netweaver 7.01 TrialPart 2 – Netweaver Trial Remote AccessPart 1 – Netweaver 7.01 ABAP Trial Tips FB.init("3c5ad27f6d3d2e816e6c6ad4a5a36e7b");SAP Consulting South Africa on Facebook Job OpeningsGeneral SAP ABAP (Hire)General SAP Archiving (Hire)General SAP Authorisations (Hire)General SAP Basis (Hire)General SAP BW/BI (Hire)General SAP CRM (Hire)General SAP DMS (Hire)General SAP FI (Hire)General SAP HR (Hire)General SAP Industry Solution (All) (Hire) Feedjit Live Blog Stats [...]
Hi David,
thanx a lot for your tips, they helped me a lot to get my NW-System running smoothly.
One question concerning the transport system: Have you tried to import the TechEd2007 examples [SDN, Manfred Lutz: Web Dynpro ABAP exercises from TechEd 2007]?
Request Y7AK068639 fails with return code 12. When looking at the details, there is an ABAP syntax error in class CL_PROXY!! I have looked for a workaround (including OSS) all day long, in vain… Have you faced the same problem?
Regards, Paul
@Paul
Hi Paul,
I will try this out and let you know my results…
@Paul
I have tried to import this and have had the same problem as you – syntax errors. I have however been able to import transports from other systems, so it is not a transport system error. The problem obviously lies in a difference between the source and target systems. It looks like the TechEd 2007 transport depends on certain objects to already exist with very specific methods, parameters etc, but they are not there or are not the same. Sorry that I could not be of more help.
@David Bann
I tested the imports on a second trial NW-System at work and it didn’t work either. Due to backwards compatibility, the imports should normally work in newer systems too. I will add a post on SDN-topic of Manfred Lutz, hoping that the SAP guys can give us a solution. Thank you for having tried and I hope to see some more tips on your blog!