Solution : https://service.sap.com/sap/support/notes/812386 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues with RFC connections to the SAPNet R/3 front end. It's pertinent for systems with no connection to SAPNet R/3 and poor performance. For SAP releases 4.0 and above, users must verify their RFC connection settings. The note explicitly instructs to shift from "No load distribution" to load-distributed connections using the SAPOSS for improved handling. Steps include implementing Note 766505 via SNOTE, deleting existing RFC destinations, and recreating them with prescribed procedures to ensure proper configuration. Also, logon groups are no longer usable for transferring data to SAP, necessitating updates in RFC destinations as per this guideline.
Key words :
note 766505sapnet_rfc transaction sdccsapnet_rtcc transaction sdccsdcc_oss sdcc_oss transaction sdccnusing logon groups, sdccn -> goto -> settings -> task specific -> rfc destinations -> change mode -> 'create destination, transaction oss1 ->parameters -> technical settings -> change mode -> save, logon group intended purpose-----------------------------------------------------------1_public note assistant, sdcc -> maintenance -> refresh -> session overview sdcc_oss, se38 -> rtcctool -> list -> refresh, terms logon groups, -----------------------------------------------------------saposs transaction oss1, relevant logon group, rfc connection saposs serves
Related Notes :
| 1172939 | Technical prerequisites for remote service delivery in SSM |
| 906992 | AS/400: Load Balancing |
| 802659 | Update job RNOTIFUPDATE01 no longer works |
| 766505 | OSS1: Changes to the RFC connection to SAPOSS |
| 455709 | Message server in SM59 is too short (shorter than 100) |