12/31/2007 Page 1 of 8

Note 33135 - Guidelines for OSS1

Note Language: English Version: 15 Validity: Valid from 06/30/2006

Summary

SymptomYou are using transaction OSS1 to establish a remote connection.

More TermsOSS1, RFC connections to SAPNet - R/3 Frontend, SAPOSS, OSS_RFC, SAProuter

Cause and PrerequisitesRemote connection to SAP, R/3 system

Solution

On April 03, 2006, SAPNet - R/3 Frontend was deactivated as a userinterface. SAPNet - R/3 Frontend, which was introduced in 1995 as SAP'sOnline Service System (OSS), was SAP's first and, for a long time, its onlysupport system, which customers worldwide accessed using transaction OSS1.

Today, the SAProuter connection via transaction OSS1 continues to be usedfor the following RFC connections:- Transfer of EarlyWatch Alert data- Exchange of data using the SAP Notes Assistant

To install and configure this transaction, proceed exactly as follows:

1. Making the technical settings for OSS1You must configure transaction OSS1 before you can use it. Choose"Parameter" from the menu bar (-> Techn. Settings) and choose "Change".

The technical settings for transaction OSS1 are set by default to Walldorf(sapserv3) with the IP address 147.204.2.5. If this address does notcorrespond with the entry in your host file, choose the sapserv3 IP addressthat is valid for you by choosing the menu option "SAPRouter at SAP ->Walldorf".Furthermore, enter your local SAPRouter information in the "SAPRouter 1"fields. Now save the settings.

After making these changes, the screen for the technical settings should beas follows:

Router data for the logon to SAPNet - R/3 Frontend

+-Customer SAPRouters-------------------------------------------------+| +-SAPRouter 1------------------+ +-SAPRouter 2-----------------+ || | Name my_saprouter | | Name | || | IP Address x.x.x.x | | IP Address | || | Instanc No. 99 | | Instance No. | || +------------------------------+ +-----------------------------+ |+---------------------------------------------------------------------+

+-SAPRouter and OSS Message Server at SAP-----------------------------+| +-SAPRouter at SAP-------------+ +-OSS Message Server----------+ || | Name sapservX | | Name oss001 | || | IP Address x.x.x.x | | DB Name O01 | || | Instance No. 99 | | Instance No. 01 | |

12/31/2007 Page 2 of 8

Note 33135 - Guidelines for OSS1

| +------------------------------+ +-----------------------------+ |+---------------------------------------------------------------------+

NOTE: Replace sapservX with the following values:

sapserv1 (194.117.106.129) connection via Internet VPN sapserv2 (194.39.131.34) connection via Internet SNC sapserv3 (147.204.2.5) for customers with connection to Germany sapserv4 (204.79.199.2) for customers in America sapserv5 (194.39.138.2) for customers with connection to Japan sapserv6 (194.39.139.16) for customers in Australia and New Zealand sapserv7 (194.39.134.35) for customers in Asia

Choose "Start Logon to SAPNet - R/3 Frontend". If the system issues messageS1 452, there are errors in the operating system configuration. In thiscase, see appendix A.When you install an access authorization file "saprouttab", you shouldensure that all of your front ends and R/3 servers can establish aconnection to sapserv3, service sapdp99. Appendix E contains examples ofsaprouttabs. For more information on the SAPRouter, refer to the SAPRouterdocumentation (Note 30289).Try it again until the dialog box "Please select a group" appears. If thedialog box "Please select a group" is displayed, the configuration fortransaction OSS1 is correct. You can then proceed with the next section.

NOTE:When you try to log on to SAPNet - R/3 Frontend, the system issues an errormessage indicating that you are no longer allowed to log on to SAPNet - R/3Frontend.

2. Further questions?As soon as you have carried out the steps described above, transaction OSS1should connect you to the most efficient SAPNet - R/3 Frontend applicationserver.If you have further questions or problems, the file entitled "OSS1.TroubleShooting" contains additional information. If you have a problemthat you cannot solve, contact our hotline: 0180/5 34 34 3-3.

Appendix A

If message S1 452 appears when you try to log on to SAPNet - R/3Frontend with transaction OSS1, there is an incorrect setting somewhere(either in the technical settings for OSS1 or at operating system level).To find out why the connection to the message server was unsuccessful,choose Tools (Case, Test ( Developer trace (transaction ST11). The tracecontains an entry for dev_lg. This file contains the error log. TheLOCATION line, if available, contains the host on which the error occurred.The problem description is found in the ERROR line. If you cannot find theentry dev_lg, check whether the program "lgtst" exists (see appendix B).

Examples of the contents of dev_lg:

************************************************************************** ERROR partner not reached (host abc.def.gh.i, service sapdp99)*

12/31/2007 Page 3 of 8

Note 33135 - Guidelines for OSS1

* TIME Thu Aug 10 09:17:57 1995* RELEASE 21J* COMPONENT NI (network interface)* VERSION 15* RC -10* MODULE niuxi.c* LINE 773* DETAIL NiPConnect* SYSTEM CALL connect* ERRNO 239* ERRNO TEXT Connection refused* COUNTER 1*************************************************************************Here, the system could not reach the SAPRouter. For example, no SAProutercould be found under service 99 (port 3299) on the host with the IP addressabc.def.gh.i. The SAPRouter process does not work or the IP address was notconfigured correctly in OSS1.

************************************************************************** ERROR service 'sapdp99' unknown** TIME Thu Aug 10 09:22:00 1995* RELEASE 30A* COMPONENT NI (network interface)* VERSION 17* RC -3* MODULE niuxi.c* LINE 404* DETAIL NiPServToNo* SYSTEM CALL getservbyname* COUNTER 1*************************************************************************This message indicates that the service sapdp99 was not entered in/etc/services. Add the entry in /etc/services. This must be available onall R/3 servers and front ends.

************************************************************************** LOCATION SapRouter on abc.def.gh.i* ERROR route permission denied (XXXXXXXX to sapservX, sapdp99)** TIME Thu Aug 10 09:37:44 1995* RELEASE 30A* COMPONENT NI (network interface)* VERSION 17* RC -94* MODULE nixxrout.c* LINE 1426* COUNTER 1*************************************************************************The file saprouttab, which contains the valid connections, is not correct.The SAPRouter on the host abc.def.gh.i does not set up the connection tosapservX. Check the SAPRouter file saprouttab. This should contain everyR/3 server and frontend (see also appendix E).

12/31/2007 Page 4 of 8

Note 33135 - Guidelines for OSS1

************************************************************************** LOCATION SapRouter on abc.def.gh.i* ERROR internal error** TIME Thu Aug 10 10:50:18 1995* RELEASE 21J* COMPONENT NI (network interface)* VERSION 15* RC -93* MODULE niuxi.c* LINE 773* DETAIL NiPConnect* SYSTEM CALL connect* ERRNO 242* ERRNO TEXT No route to host* COUNTER 1*************************************************************************This error message indicates that the host abc.def.gh.i cannot process theIP address of the next host configured in OSS1. If the SAPRouter errormessage appears and the next host is sapservX, check the address forsapservX. OSS1 is delivered with the default settings sapserv3 and IPaddress 147.204.2.5. Customers in the U.S.A. are normally connected tosapserv4, IP address 204.79.199.2. If required, change the technicalsettings of OSS1 accordingly.

************************************************************************** ERROR internal error** TIME Thu Nov 23 00:11:20 1995* RELEASE 21J* COMPONENT NI (network interface)* VERSION 15* RC -1* COUNTER 1*************************************************************************This message shows that the instance number entered does not agree with atleast one of the technical settings for the SAPRouter defined in OSS1. Thedefault for the instance number of the SAPRouter is 99. Under nocircumstances should you enter the instance number of your R/3 system forthe SAPRouter. You need to specify instance number 99 for sapservX.Otherwise, it is not possible to log on to SAPNet - R/3 Frontend.

************************************************************************** LOCATION SapRouter on sapservX* ERROR route permission denied (XXXXXX to oss002, sapmsO01)** TIME Mon Nov 27 19:25:54 1995* RELEASE 30A* COMPONENT NI (network interface)* VERSION 15* RC -94* MODULE nixxrout.c* LINE 1390

12/31/2007 Page 5 of 8

Note 33135 - Guidelines for OSS1

* COUNTER 1*************************************************************************An incorrect server was entered as message server 001, in this example, theserver oss002. The message server for O01 is oss001. Change the technicalsettings for transaction OSS1 accordingly.

Appendix B (for Windows NT only)

Change to the directory "\usr\sap\<SID>\SYS\exe\run" and search for theprogram "lgtst.exe". If you cannot find it, or if the length of this fileis not exactly 640216 bytes, import the program "lgtst.exe" from sapservXvia ftp:

> ftp sapservXConnected to sapservX.220 sapservX FTP server (Version 1.7.194.2 Wed Sep 8 17:23:04 GMT 1993)ready.Name: ftp331 Guest login ok, send ident as password.Password: <Your_customer_number>ftp> cd dist/permanent/OSS1/lgtst.exe250 CWD command successful.ftp> binary200 Type set to I.ftp> get lgtst.exe150 Opening BINARY mode data connection for lgtst.exe (640216 bytes).226 Transfer complete.640216 bytes received.ftp> bye

Copy this file into the aforementioned directory.

Appendix C

The messages from transaction OSS1 (error messages and information) aregiven in the following list. Each message is described briefly.

-----------------------------------------------------------------------|No.| Message Text-----------------------------------------------------------------------|450| Maintain technical settings first.|452| Unable to connect to SAPNet - R/3 Frontend message server.|454| E: Unable to start SAPGUI.|455| SAPGUI was started.|456| Specify a server name.|457| Specify an IP address.|458| Specify an instance number.|459| Specify a database name.|460| No authorization to log on to SAPNet - R/3 Frontend.|461| No authorization to maintain technical settings.

12/31/2007 Page 6 of 8

Note 33135 - Guidelines for OSS1

|462| E: RFC destination could not be generated-----------------------------------------------------------------------

Number 450: Maintain technical settings firstYou can only log on to SAPNet - R/3 Frontend if the technical settingsare maintained. The technical settings determine the network path from thecustomer R/3 system to the online service system.

Number 452: Unable to connect to SAPNet - R/3 Frontend message server.This message appears if the connection to the SAPNet - R/3 Frontend messageserver was not possible (system name O01, server oss001). There can bedifferent reasons for this (see appendix A).

Number 454: E: Unable to start SAPGUI.Transaction OSS1 could start the SAPGUI (not SAPTEMU), either because theprogram does not exist in the path given, or because the execute permissionis not set correctly. Check whether the SAPGUI exists; SAPTEMU alone is notsufficient.

Number 455: SAPGUI was started.This is not an error message. It merely informs you that an additionalSAPGUI was started to establish a connection to SAPNet - R/3 Frontend.

Number 456: Specify a server name.The server name was omitted from the technical settings.

Number 457: Specify an IP address.The IP address was omitted from the technical settings.

Number 458: Specify an instance number.The instance number was omitted from the technical settings.

Number 459: Specify a database name.The database name for the Online Service System (001) was omitted from thetechnical settings.

Number 460: No authorization to log on to Online Service SystemYou do not have authorization to call transaction OSS1. Up to Release 2.2F:The authorization S_TSKH_ADM is checked for value 1. After Release 2.2F:For transaction OSS1, there are two special authorization profiles (seeappendix D).

Number 461: No authorization to maintain technical settings.You do not have the authorization to maintain the technical settings (seeappendix D).

Number 462: E: RFC destination could not be generated.In Releases 2.2*, you can ignore this message. When saving the technicalsettings, an attempt is made to generate the RFC destination SAPOSS. Thelength of an RFC destination is limited in 2.2*, and the maximum length wasexceeded by the parameters of the technical settings.

Appendix D

As of Release 2.2F, there are two different authorization profiles for

12/31/2007 Page 7 of 8

Note 33135 - Guidelines for OSS1

transaction OSS1: S_OSS1_START and S_OSS1_ADMIN.

S_OSS1_START authorizes you to call transaction OSS1 and to log on to theOnline Service System. In addition, S_OSS1_ADMIN contains theauthorization to maintain the technical settings for the transaction.

The technical settings of OSS1 must be made at least once. Therefore, addS_OSS1_ADMIN to your user profile, log off, and then log on againafterwards.

Appendix E

Prerequisites:(A TCP/IP connection can be established between the SAProuter onthe customer system and the SAProuter on sapserv3 in Walldorf.(The SAProuter process must be started on the server that is registeredwith SAP:

saprouter -r -R saprouttab &

Example of the "saprouttab" file with minimum configuration:

# saprouttab - Example## Allows connections from the entire customer network to sapservX# and therefore to the Online Service System via SAProuter port 3299.P * sapservX sapdp99 *# Allows connections from sapserv3 to the entire customer network,# for example for EarlyWatch or First Level Support.P sapservX * * *

Header Data

Release Status: Released for CustomerReleased on: 06/30/2006 09:13:57Priority: Correction with high priorityCategory: Consulting

Main Component XX-SER-NET Network connection

The note is not release-dependent.

Related Notes

12/31/2007 Page 8 of 8

Note 33135 - Guidelines for OSS1

Number Short Text

982045 Error calling the SAP back-end system

883401 RFC destination SAPOSS without description

766505 OSS1: Changes to the RFC connection to SAPOSS

200436 How to establish an SAPNet R/3 connection in CIS

137342 Schedule - connection to SAP extranet, OSS and SAPNet

122827 How to establish an OSS connection in Poland

35010 Service connections: Composite note (overview)