SAP Note

Header Data

Symptom

The RFC connections to the SAPNet R/3 front end (OSS) existing in the SAP system basically work, but they are configured incorrectly.

Other Terms

Logon groups SAPNet R/3 front end (OSS), SMLG, EWA, SNOTE, Solution Manager, SDCC, SDCCN, RTCCTOOL, RSECNOTE, MOPZ, maintenance optimizer, Solution Manager basic functions, RNOTIFUPDATE, RNOTIFUPDATE01, RNOTIFUPDATE7, OSS1, Service Provider, VAR, Service Desk, partner, incident management, RFC connections to SAP, GET_PPMS_DATA_FROM_OSS, RAGS_DSWP_SERV_CONTENT_UPDATE, AI_SC_LISTENER, AI_SC_SEND_SYSTEM_RELATIONSHIP, AI_SC_REFRESH_READ_ONLY_DATA, SOLMAN_SETUP, Service Delivery, ST13, ST14_RTCC, OSS_RFC, EarlyWatch Alert, Service Data Control Center, SAPSNOTE, CUPOSS, SOLMAN_SAP_BACKEND008, REFRESH_ADMIN_DATA_FROM_SUPPORT, SAPOSS, SAP-OSS, SAP-OSS-LIST, CUPOSS, SDCC_OSS, SAPNET_RFC, SAPNET_RTCC, OSS, AI_CRM_IM_UPDATE_FROM_SAP, AI_CRM_IM_UPDATE_FROM_SAP_ISV, SAProuter,

Reason and Prerequisites

Correction of the faulty settings in an existing RFC connection to the SAPNet R/3 front end (OSS).

Solution

The following RFC connections to the SAPNet R/3 front end (OSS) can exist in an SAP system.

RFC connections: SAPOSS EWA SAPNET_RFC EWA SAPNET_RTCC EWA SDCC_OSS EWA CUPOSS EWA OSSNOTE SAP-OSS SAP-OSS-LIST SAPNOTE SM_SP_<customer number> When you use a different RFC connection name to the one listed here for an RFC connection to the SAPNet R/3 front end (OSS), you have to check this connection too. You can find out these RFC connections if necessary by identifying this connection to OSS via transaction SE16 and the table RFCDES.

In any case, the first time the service connection to the SAPNet R/3 front end (OSS) is established, the main RFC connection SAPOSS is generated and then other RFC connections are generated as copies of SAPOSS. If you adapt this RFC connection SAPOSS, the system does not automatically copy these changes to other RFC connections to the SAPNet R/3 front end (= OSS). You should therefore ensure that you adapt 

    2000132 - Configuring RFC connections to the SAPNet R/3 front end (OSS) correctly  

Version   13     Validity: 26.06.2014 - active   Language   English

Released On 26.06.2014 10:37:26

Release Status Released for Customer

Component XX-SER-NET Network connection

BC-UPG-NA SAP Notes Assistant

BC-UPG-PRP Upgrade Preparation

SV-BO Backoffice Service Delivery

SV-ES-SEC SAP Secure Support Services

SV-SMG-INS Installation, Configuration and Upgrade of Solution Manager

SV-SMG-OP Solution Directory

SV-SMG-SDD Service Data Download

SV-SMG-SER SAP Support Services

SV-SMG-SER-EWA EarlyWatch Alert

SV-SMG-SVC Administration of Service Connections with Solution Manager

SV-SMG-UMP Usage measurement of products

XX-SER-NET-HTL Problems with remote access from SAP to Customer system

XX-SER-NET-HTL-CON 2nd Level for RCSC internal use only!

Priority Hot News

Category Customizing

Other Components

all RFC connections to the SAPNet R/3 front end (OSS). You correct an RFC connection by calling transaction SM59 and then adjusting the the technical settings of the RFC connection to the SAPNet R/3 front end (OSS) as follows:

RFC connections  - logon groups: SAPOSS                 => EWA SAPNET_RFC          => EWA SAPNET_RTCC        => EWA SDCC_OSS            => EWA CUPOSS                 => EWA OSSNOTE                => 1_PUBLIC SAP-OSS                 => 1_PUBLIC SAP-OSS-LIST          => 1_PUBLIC

SM_SP_<customer number>   => 1_PUBLIC Logon group "2_JAPANESE": Japanese-language SAP customers can use the logon group "2_JAPANESE".

The following load balancing groups are therefore available for logon to the SAPNet R/3 front end (OSS):

1_PUBLIC 2_JAPANESE EarlyWatch Alert (EWA):

The user and password already assigned to an existing RFC connection to the SAPNet R/3 front end (OSS) do not need to be changed. Of course, the existing user in the RFC connection - and the password - have to work before adjustment of the RFC connection and continue to function after the adjustment of the RFC connection.

The logon groups mentioned further up in this SAP Note (EWA and 1_PUBLIC) are equivalently configured in the SAPNet R/3 front end (OSS), so that an identical logon access behaviour is possible. The same is true for the logon group 2_JAPANESE

You can usually use transaction OSS1 in the SAP system to make the settings for the SAPNet R/3 Frontend (OSS). You can make the adjustments via Parameters and Technical Settings in the menu of the transaction. However, not all existing RFC connections can be identified and adjusted here; for this reason, you should use transaction SM59 to make the checks and the possibly necessary adjustments.

Remarks on the technical settings in transaction SM59 for these ABAP connections: Use the target system "OSS". Use the message server "oss001.wdf.sap.corp". If you previously only used "oss001" instead of "oss001.wdf.sap.corp" and this entry previously worked with "oss001", you can retain "oss001". Otherwise use "oss001.wdf.sap.corp". Mark YES at "Load Balancing“. Use a logon group as already specified further up in this SAP Note.

Target host: /H/X1/S/S1/H/X2/S/3299/H/oss001.wdf.sap.corp with X1 = IP address of the customer SAProuter X2 = IP address of SapservX S1 = Customer SAProuter port Possible entries for SapservX sapserv1 (194.117.106.129) Internet VPN connection sapserv2 (194.39.131.34) Internet SNC connection sapserv3 (147.204.2.5) for customers connected to Germany sapserv4 (204.79.199.2) for customers in the United States sapserv5 (194.39.138.2) for customers connected to Japan sapserv7 (194.39.134.35) for customers in Asia Pacific Japan (APJ) including New Zealand and Australia sapserv9 (169.145.197.110) for customers in APJ including New Zealand and Australia sapserv10 (203.13.159.37) for customers in China

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (3)

2015988   Loadbalancing zum SAPNet R/3 Frontend (OSS) kleiner / gleich Release 4.X

1990918   Beschreibung der RFC Verbindungen zum SAPNet R/3 Frontend (OSS)

1234500   Composite SAP Note: Information about automatic update

1140938   There is no new service plan to be collected ...

982045   Error calling the SAP back-end system

812386   RFC connection to the SAPNet R/3 front end.

766505   OSS1: Changes to RFC connection SAPOSS

763561   Service Data Control Center (SDCCN) - FAQ

216952   Service Data Control Center (SDCC) - FAQ

182308   Incorrect logon data in R/3 destination SAPOSS

33135   Guide for OSS1

33135   Guide for OSS1

766505   OSS1: Changes to RFC connection SAPOSS

2015988   Loadbalancing zum SAPNet R/3 Frontend (OSS) kleiner / gleich Release 4.X