Getting Started Newsletters Store

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center
Lines of Business University Alliances Events & Webinars Innovation
Log On Join Us Hi, Guest Search the Community
Activity Communications Actions
Browse
manfred.lutz
Previous
post
Next
post
0 Tweet 0
The last ABAP Trial Version for Newbies Part 7: Creating a Program and a Package - An Introduction to the SAP
Change and Transport System was about the CTS (Change and Transport System), where you have got a brief
overview of the transport mechanism on the ABAP Application Server. This blog explains what you have to do to get a
package with your development objects out of a system. For our purposes, exporting a package means to get it out of
the ABAP universe to the installation level. Let's assume that you have created some programs or Web Dynpro
components in the old (SP8) Trial Version and you want to upgrade the Trial Version to SP11. You use the transport
system to save your programs and components and make them availiable in the new system. You first need to set
up the Transport System for the export. On the installation level, the 'SAP' directory must be shared to the 'System'
user. Open the MS Explorer, select the 'SAP' directory and choose 'Sharing and Security...' from the context menu.
Select the 'Share this folder' option, and enter 'sapmnt' as the share name.
Choose 'Permissions'. Add a new user 'SYSTEM' with full
ABAP Trial Version for Newbies: Part 8 ' Exporting
development objects from SP8 '
Posted by Manfred Lutz in manfred.lutz on Apr 25, 2007 6:21:05 AM
Share 0 Like
control. Choose 'Apply' and then 'OK'. Now the changes
on installation level are complete. To set up the transport environment, you need to start the Transport Managment
System (Transaction STMS).
Choose 'System
Overview' (red rectangle) and select 'CL5' from the table. Open the context menu, and choose 'Extras'. Then, choose
'Distribute and Activate Configuration'.
Leave the distribution
options as the default. Choose 'Enter'. After you have successfully distributed the transport environment, there are
two files in the 'bin' directory of the 'trans' tree on the installation level. These files are required by the RFC (Remote
Function Call) to retrieve information about the receiver side.
The
tree should look like this. Now the setup of transport system is complete. In our example, we assume that there is a
development object 'Z_MY_QUIZ' in an old Trial Version (SP8) that you need to migrate to the new Trial Version
(SP11), since you can have only one ABAP Trial Version on your PC. This object is a copy of the 'WDT_QUIZ' Web
Dynpro ABAP component in the Trial Version. To export an object, it must belong to a package. How to create a
package is shown in the previous New Blog Series: ABAP Trial Version for Newbies in this series. The package for
migration in this blog is 'Z_MY_PACKAGE'. Let's assume that the object you want to migrate is created as a local
object. (new users do not normally concern themselves with packages and workbench orders.) You first need to
reassign the object to a package. Go to the ABAP workbench (SE80) and select the component you want to reassign.
This would be the right
way to reassign the object, but be careful: there is a bug in the current version. Mime objects will not be written to the
export. For that you need to copy the component to a new object that is related to a package.
Choose ENTER.
The system prompts you with the
workbench request to create the package. This request will comprise all the objects from the package, and will be the
basis of the transport. Choose ENTER. SAVE.
There may be another dialog step - confirm this in the same way. Now the package Z_MY_PACKAGE which contains
all the objects in the Web Dynpro Component/Application Z_MY_QUIZ is linked to the workbench order NSPK900044.
In the following steps, this order and the related tasks will be released. Open the transport organizer (transaction
SE09). You will find the virtual system 'CL5' as the destination of our transport.
Select the
correction (NSPK900045) for our workbench order, and click the truck icon in the menu bar. This releases the
correction. A released correction cannot be changed. To release a workbench order, all the related corrections must
be released first. After releasing the correction, an OK icon appears right to the correction.
You
process the workbench order in the same way. Place the cursor on the workbench order and click the truck icon in the
menu bar. This starts the physical transport.
To find
out when the transport is finished, you will have to refresh a couple of times.
Now
the transport is complete. On the level of the intallation, there is data written to two files. The 'cofiles' directory contains
the header information in a file beginning with 'K' followed by the workbench order number and ended with the system
ID. The transport data can
be found in the 'data' directory beginning with 'R' followed by the workbench order number and ended with the system
ID. These two files can be
copied to the corresponding directories in any other SAP system in order to be imported. This will be the topic of the
Average User Rating
(0 ratings)
My Rating:
0 Tweet 0
next blog. There are two forums where you can post your questions and ask for help in case of trouble. Software
Downloadsfor general discussions about the trial versions ( interesting projects you are doing with it, wishes for the
future,) SAP NetWeaver Application Serverfor concrete problems with the installation
2751 Views
Share 0 Like
16 Comments
Like (0)
Peter Inotai Apr 25, 2007 6:59 AM
Hi Manfred,
I was surprised, that sapmnt wasn't shared by default. I think it was the case for previous releases.
Is there a particular reason for this?
If not, it would make sense to have it by default as part of the installation script.
Thanks in advance,
Peter
Like (0)
Klaus Keller Apr 25, 2007 1:57 PM (in response to Peter Inotai)
Hi Peter,
In earlier releases the installer added a dedicated operating system user and shared the
folder as sapmnt by the default. The newer versions don't create this specific sap user and
as you can read in this blog, the system (owner of the sap application server process)
needs full access, thus write and read to the sapmnt. Sharing by default would lead to a
share, that could be written and read by everyone. So, for security reasons the user have to
set up this share on his own using the above mentioned sharing permissions as explained
above in this blog.
Kind regards,
Klaus
Like (0)
Peter Inotai Apr 26, 2007 12:03 AM (in response to Klaus Keller)
Hi Klaus,
Thanks for your detailed explanation.
Best regards,
Peter
Like (0)
Jun 18, 2009 2:44 AM (in response to Peter Inotai)
Hi
i had install SAPNWABAP701SR1_TRIAL on my server. In the transaction
STMS want configuration for transport under "extras->Distribute and
Activate TMS Configuration" and choose the option "Distribute
Configuration to All Systems". Than the error message
System NSP Command TMS_PM_DISTRIBUTE_PROFILE
Client 001 Service Communication Interface
User BCUSER Start Online
Date 17.06.2009 Function TMS_PS_WRITE_PROFILE_TO_DISK
Time 11:52:39 Message RFC_COMMUNICATION_FAILURE
RFC communications error with system/destination
TMSADMatNSP.DOMAIN_NSP
Error when opening an RFC connection
The folder usr is share named "sapmnt" and the SYSTEM User had full
permission of the folder.
What i do it wrong?
Like (0)
Christian Kipp Aug 26, 2009 2:07 AM (in response to )
Hello, maybe the solution described here will solve the
problem:
NetWeaver ABAP Trial version 7.01 error
TP_CANNOT_CONNECT_SYSTEM
It worked for me. I just changed the host to "localhost"
Like (0)
kumar r Mar 10, 2008 10:24 PM (in response to Klaus Keller)
Hi Klaus,
Thanks for your guidance, I have given the access permissions for the shared
folder for the user "SYSTEM". In XP , But i am getting the following error
"TP_DOMAIN_NSP.PFL could not be opened for writing (Invalid argument)".
What would be the issue ? When i try to access my sapmnt shared folder thorugh
windows explorer, The accesss is been denied by the system.
Like (0)
Klaus Keller Mar 11, 2008 9:02 AM (in response to kumar r)
Hi,
The user SYSTEM requires read and write permission to the file (see
2nd screenshot). Have you granted these permissions to the user
SYSTEM and checked whether the file "TP_DOMAIN_NSP.PFL" exists?
Kind regards,
Klaus
Like (0)
Karthikeyan B Jun 15, 2009 4:05 AM (in response to Klaus Keller)
Hi Klaus,
I tried the same.
the folder 'sap' is shared for user SYSTEM with full access.
But when i try generate from STMS transaction,the two files are
generated in the 'bin' folder.
Thanks in Advance!
Regards
Karthik
Like (0)
Klaus Keller Jun 18, 2009 2:16 AM (in response to
Karthikeyan B)
Hi Karthik,
The bin folder is the correct place for the 2 files.
Kind regards,
Klaus
Like (0)
David Leon Jun 9, 2007 9:27 AM
My XP computer does not provide same options for folder sharing. Instead of the dialogs shown it
instructs me to drag the folder to the Shared Doc folder which I did once and caused a disaster as I
had to reinstall NW04s. Any suggestions?
Klaus Keller Jun 26, 2007 2:53 AM (in response to David Leon)
Hello,
You could try this:
Open an explorer, go to "Tools"->"Folder Options..."->"View". In the "Advanced settings" area
disable the option "Use simple file sharing".
Now right-click on the SAP folder and click on "Sharing and Security...". You should be able
to apply as described in this blog.
Hope this helps.
Kind regards,
Klaus
Site Index Contact Us SAP Help Portal
Like (0)
Like (0)
Community User Sep 5, 2007 6:42 AM
I am new to SAP and could not proceed to complete the steps in the blog above.
My platform is PC desktop with WinXP and SAP NW7.0 ABAP Trial SP12. I am stuck at the locating
the z_my_quiz to change the package assignment. I will have the problem to complete part 8 and 9
as these blogs are related.
Is there any methods to create the respective objects (z_my_quiz and z_my_package) in SP12 alone
as I do not have SP8?
Your response is highly appreciated.
Thank you.
Like (0)
Julio Torres Oct 9, 2007 7:11 PM
Hi,
Like (0)
Fabiano Bartholomeu Sep 6, 2008 10:08 PM (in response to Julio Torres)
Hi, File
smartbrowsesandvine\sapmnt\trans\bin\TP_DOMAIN_N <br/> could not be opened for
writing (No such file or <br/> directory) <br/>Believe or
not, I've already wasted more than fifty hours searching the web and trying to solve this
problem! <br/><br/>Please, I need some help.<br/><br/>Thanks in advance,<br/>
<br/>Fabiano Bartholomeu.
Like (0)
Christian Zahl Aug 19, 2009 8:26 AM
Hi,
I installed the SAPNWABAP701SR1_TRIAL and followed the steps in this BLOG (many thanks for
writing this helpful baby!!!). When trying to setup the transportation layer, I also got the error window
regarding "RFC_COMMUNICATION_FAILURE".
After digging a long time in the web and the logs, I found the reason behind. In the dev_w0 I found:
M Wed Aug 19 16:53:08 2009
M ***LOG Q0I=> NiPGetHostByName: hostname 'PWDF3101' not found: gethostbyname (11004:
WSANO_DATA: Valid name, no data record of requested type) [ninti.c 320]
There is an APAP connection defined, which referes to the host "PWDF3101" (can be seen in the
verified by SM59). As this is unknown, the "gethostbyname" returns with the error code 11004 (which
you can see in the sapmmc).
By adding this host to the local hosts file, while pointing to my own IP, the problem was solved, e.g.
10.10.0.10 PWDF3101
. Note that you have either to reset the hostname buffer (SM51), or simply restart the SAP by the
sapmmc.
Hope this is helpfull...
CU,
Christian
Like (0)
Sep 1, 2009 4:37 AM (in response to Christian Zahl)
Hi,
I have just changed the Target Host in the TMS configuration for NSP with transaction STMS
before distributing and the problem was solved.
Regards,
Rafael
Follow SCN Privacy Terms of Use Legal Disclosure Copyright