Instructions for Checking and Updating an RFC

Connection to SAPNet R/3 Frontend (OSS)

It could be that you have incorrect RFC connections to SAPNet R/3 Frontend (OSS). By incorrect, we
are referring to a direct connection to the central instance to OSS and/or a user ID and password
error. To avoid service disruptions with SAP, you need to adjust your RFC connection so that it
correctly connects to a logon group which manages load balancing. In addition, the RFC connection
needs to be established with a functioning user ID and password as well.

To set-up a correct RFC connection to SAPNET R/3 Frontend (OSS), please follow these instructions.
Here are the affected RFC connections. They are described in more detail in SAP Note 2000132:
SAPOSS
SAPNET_RFC
SAPNET_RTCC
SDCC_OSS
SAP-OSS
SAP-OSS-LIST
SM_SP_<customer number>

Log on to the system with an RFC connection to SAPNET R/3 Frontend (OSS).
Call transaction SM59
Choose the RFC connection you want to check (see PDF with title How-to-adjust_RFC-to-loadbalancing which is attached to SAP note 2000132)
The connection should be set-up as follows:
The RFC connection to SAPNet R/3 Frontend (OSS ) needs to be set up as follows:
Load Balancing = Yes
The Logon Group needs to be one of these three: 1_PUBLIC or 2_JAPANESE or EWA
Perform an authorization test. This is done by choosing the menu options Utilities Test and
then the option Authorization Test. If the authorization test is successful, then your RFC
connection is correct; then no further actions are required
If the authorization test mentioned in the step above is not successful or Load Balancing is set to NO,
continue with these steps.
Activate load balancing for your RFC connection (set Load Balancing to YES).
Enter a valid user ID and password.
(a) Information regarding User ID and Password
A list of valid user IDs is provided further on in this document
If your password is incorrect in the RFC connection, enter the correct password.

Passwords for S-users are unique. You may have to request a new password
The password for the user ID OSS_RFC is available in SAP Note 182308
The passwords for the user ID SDCC_NEW in the RFC connection SDCC_OSS need to be
generated automatically by calling the transaction SDCCN. This is described in SAP Note
763561.
(b) Load Balancing
Once you have a correct user ID and password, you can check the load balancing setting for
your RFC connection. Under the tab Technical Settings for your RFC connection in
transaction SM59, make sure the technical setting Load Balancing is set to Yes.
If load balancing is already set to YES, then you are finished.
If load balancing is set to No, proceed as follows:
Choose your RFC connection to SAPNET R/3 Frontend (OSS) in transaction SM59. Switch from
display mode to change mode. Under the tab Technical Settings, choose the setting called
load balancing and set it to YES.
In the field Target System, enter the system Identifier (SID) = OSS.
In the field Message Server (Msg. Server), enter your SAPRouter string to SAPNet R/3
Frontend (OSS) => You can find more details in SAP Note 33135 (and SAP Note 2000132).

In your SAPRouter string to SAPNet R/3 Frontend (OSS), you can use either
oss001.wdf.sap.corp or oss001 (both entries are valid).
In your SAPRouter string to SAPNet R/3 Frontend (OSS), you can use either TCP Port sapdp99
or 3299 (both entries are valid).
Make sure you use one of the three following logon groups:
1_PUBLIC
2_JAPANESE
EWA.

(c) Connections
The available RFC connections to SAPNet R/3 Frontend (OSS) are documented in SAP Note 2000132.
Log on in client 001 when maintaining RFC connections.
Choose EN or DE as your log on language.

The RFC connection SAPOSS is usually set up with the user ID OSS_RFC. The password for this
user is found in SAP Note 182308. This note also applies to the RFC connection SAPNET_RFC.
The RFC connections SAP-OSS, SAP-OSS-List-O01 und SM_SP_<customer number> require a valid
S-user ID.
S users IDs are unique and are assigned to single employees. If the S user ID required for your
RFC connection to SAPNet R/3 Frontend (OSS) is not yours, contact the employee with the S user
ID and have them enter the password. If this is not possible, contact the S user ID Super
Administrator in your company. Super Administrators can be found in SAP Service Marketplace
(service.sap.com) at this link:
https://service.sap.com/sap/bc/bsp/spn/xsmpuser/report.do?report_id=superadmin
The RFC connection called SM_SP_<customer number> is created in SAP Solution Manager by a
guided procedure in SAP Solution Manager. This RFC connection is used when multiple customer
numbers and installation numbers are used in a central SAP Solution Manager. This is the case
with Value Added Resellers and SAP Partners who manage multiple customers with SAP
installations.
The RFC connection SDCC_OSS works with the user ID SDCC_NEW. The password for this user ID
is available in SAP Note 763561.
In addition, there is more information on this user ID and password in the transaction SDCCN.
The RFC connection SAPNET_RTCC works with the user ID ST14_RTCC. The easiest way to change
this connection is to first delete it.
This connection will then be re-created automatically as a copy of the RFC connection SAPOSS.
Before you generate the SAPNET_RTCC RFC connection, make sure the source connection
SAPOSS is correctly configured with Load Balancing = YES and logon group 1_PUBLIC or
2_JAPANESE or EWA.
When the SAPOSS connection is correct, call the transaction SE38 or transaction SA38 and run
the report RTCCTOOL. With this report, the RFC connection SAPNET_RTCC will be created as a
copy of SAPOSS and the correct user ID and password will be applied.
The RFC connection SAPNET_RTCC is used for the delivery of ST-SER Support Services and works
with the data collecting software component ST-A/PI.

Additional Information Regarding RFC Connections to SAPNet R/3 Frontend (OSS)

33135 Guide for OSS1
182308: Incorrect logon data in R/3 destination
216952: Service Data Control Center (SDCC) FAQ
763561 - Service Data Control Center (SDCCN) FAQ (SDCC_OSS)
766505: OSS1: Changes to the RFC connection to SAPOSS

797001 - SAP-Notes Unable to download an SAP Note with SNOTE (SAPOSS, SAPSNOTE)
802659 - Update Job RNOTIFUPDATE01 no longer works (SAP-OSS-LIST-O01)
812386: RFC connection to the SAPNet R/3 front end
1788467 - SDCC_OSS issue in AGS_UPDATE - Message no. AGS_DSWP_INFRA000 (SDCC_OSS)
2000132 - Configuring RFC connections to the SAPNet R/3 front end (OSS) correctly

Example RFC Connections to SAPNet R/3 Frontend (OSS)