Hi All,
There is no proper solution find to this issue so I dropped an oss message to sap they reverted with purpose and solution to this issue I followed the same and resolved my issue. Please find the information send by SAP Team it will help you too who are facing this issue.
Reason for that e-mail is that you have obviously a wrong configured
RFC connection in your systems to SAPNet R/3 Frontend (OSS).
Affected systems on your side are the systems ABC and ABC.
The issue behind that e-mail is the following.
Did you also check your that the affected RFC connection in your
systems ECD and ECP uses LOAD BALANCING = YES ?
I saw that the affected RFC destination in your systems is an IP
address.
(see 2 e-mails you`ve received).
Nevertheless, you can identify the affected RFC destination in your
system ABC and ABC in the following way:
Please logon to system ABC and ABC.
1. Call transaction SE16 or SE17
2. Enter the table name RFCDES and choose Enter. You will be in
display mode.
3. In the field RFCOPTIONS, enter user ID from the e-mail you`ve
received with a star * in front and behind your user ID, for example *
ST14_RTCC*. Choose execute (F8)
4. After executing, you get a list of affected RFC connections.
5. Call transaction SM59 to check the RFC connection settings. Expand
the ABAP Connections and select the affected RFC
6. Double click on the RFC connection to display the settings # change
to edit mode
7. Follow the instructions in SAP Note 2000132 (see also below). Make
sure you have these technical settings:
- Load Balancing = YES
- Message Server <customer-specific string because a customer
SAProuter string has to be provided>
- Group = EWA
8. Under the tab Logon & Security, make sure that the correct user ID
and password has been entered.
(before you type in any userid/password, please read this text to it`s
end;
you will get additional helpful information).
9. Save.
10. Perform an authorization test. From the SAP GUI menu, choose
Utililties à Test à Authorization Test
If the result of your authorization test is successful,
congratulations, you are finished.
Remark:
It is important to use LOAD BALANCING = YES
We can not guarantee that LOAD_BALANCING = NO will work in the future.
In case that your identified the affected RFC connections is
SAPNET_RTCC, please correct it in the following way.
Remark:
RFC connection SAPNET_RTCC is a copy of RFC connection SAPOSS.
Normally this user ST14_RTCC is only used in RFC connection SAPNET_RTCC.
So, if the identified RFC connection is SAPNET_RTCC, you can delete
this RFC connection.
Now, please take care of RFC connection SAPOSS
(remark: RFC connection SAPNET_RTCC is a copy of SAPOSS;
which means RFC destination SAPOSS needs to be checked and corrected
first).
Once again; please check RFC connection SAPOSS.
Please write down your SAPRouter string you need in field Message
Server / Target host.
Remark: You can find the SAPRouter string when you use transaction
OSS1 (see SAP note 33135)
RFC Connection SAPOSS needs to be set to LOAD BALANCING = YES.
If this is not the case, please change this RFC connection SAPOSS to
LOAD BALANCING = YES.
Please use Logon Group EWA in that RFC connection SAPOSS.
The password for the user OSS_RFC is CPIC (please see SAP note
182308).
Please do an Authorization test with that RFC connection SAPOSS
Path:
From the SAP GUI menu, choose Utililties à Test à Authorization Test
If the result of your authorization test is successful,
congratulations, you are finished with RFC connection SAPOSS.
Now you can re-create RFC connection SAPNET_RTCC.
Please do the following:
Once again:
Easiest way is to delete that RFC connection SAPNET_RTCC.
Start report RTCCTOOL with transaction SE38 or SA38.
Than this RFC connection SAPNET_RTCC will be created automatically as
a copy of SAPOSS.
Userid/password will automatically be set.
Before you start this report to re-create this RFC connection, please
take care that the RFC connection SAPOSS is set to Load Balancing
(with suggested Logon Group)!!!
Additional I will give you additional information, regarding SAP note
2000132:
The following RFC connections can exist in your SAP System(s) - (it is
also possible that you do not find all these RFC connections in your
system; it is depending on the application related scenarios you use
in your systems).
SAPOSS
SAPNET_RFC
SAP-OSS
SAP-OSS-LIST
SM_SP_<customer number>
SDCC_OSS
SAPNET_RTCC
Load Balancing must be set for all the available RFC connections.
It is necessary to check your RFC connection(s) to SAPOSS.
-> please see e-mails you`ve received.
Possible RFC users can be the following:
ð RFC connection SAPOSS # userid / password => see SAP note 182308
SAP note 182308 is also valid for RFC connection SAPNET_RFC.
ð RFC connection SAP-OSS and SAP-OSS-List-O01 and SM_SP_<customer
number>.
A valid S userid is necessary.
S*userids are individual users in a company of SAP`s Customers.
Password is only known by employee of SAP customer.
You can identify the Master (Super User) of all S*Users in your
company under the following link:
https://service.sap.com/sap/bc/bsp/spn/xsmpuser/report.do?report_id=superadmin
ð RFC connection SM_SP_<customer number> can be available only in a
SAP Solution Manager. Such an RFC connection can be setup by using the
implementation guide.
Such an rfc connection is mainly used by SAP Partners, Value Added
resellers.
ð RFC connection SDCC_OSS is used with userid SDCC_NEW.
You can find the password in SAP note 763561.
Alternative you can find the password of that user in transaction
SDCCN during the setup of that rfc connection to SDCC_OSS.
ð RFC connection SAPNET_RTCC is used with userid ST14_RTCC.
Easiest way is to delete that RFC connection SAPNET_RTCC.
Start report RTCCTOOL with transaction SE38 or SA38.
Than this RFC connection SAPNET_RTCC will be created automatically as
a copy of SAPOSS.
Userid/password will automatically be set.
Before you start this report to re-create this RFC connection, please
take care that the RFC connection SAPOSS is set to Load Balancing
(with suggested Logon Group)!!!
At the end, you can do an RFC authorization test for each single RFC
connection.
Please do an Authorization test with each single and corrected RFC
connection to SAPNet R/3 Frontend (OSS).
Path:
From the SAP GUI menu, choose Utililties à Test à Authorization Test
If the result of your authorization test is successful,
congratulations, you are finished with RFC connections.
Regards,
Thirupathi.