12.02.2013 Page 1 of 4

SAP Note 101971 - 37527 Graphical full screen is notavailable (RFC)

Note Language: English Version: 17 Validity: Valid Since 21.06.2011

Summary

SymptomYou cannot start the graphical layout editor of the Screen Painter (RFCversion).

Other terms() EUNOTE, EUSCREENPAINTER

Reason and PrerequisitesThis is generally caused by the fact that you cannot set up the RFCconnection between the front-end graphical layout editor and the callingscreen painter program at the backend.Note: For Unicode systems, you should pay particular attention to the sixthoption.

1. Option: Route permission is deniedThe following entry is in the dev_eusp<processID> trace file of thegraphical layout editor

"ERROR in RFCMgr_accept: not accepted",and the following entry of the form is in the dev_rfc.trc RFC trace file

"ERROR route permission denied (<Front-Id> to<BackId>,<Service>)".

If there is a firewall between the front-end host and the applicationserver, you must decide whether you can activate the port for the RFC ofthe graphical layout editor here (see Solution 1 below).If there is no firewall between the front-end host and the applicationserver, the route permission table of the SAProuter either contains noentry for the front-end host (on which the graphical layout editor isstarted) or the entry states that the link is secured by a password. Sincethe connection is denied, the graphical editor process terminates again,and the screen painter switches to the alphanumeric layout editor.

2. Option: Service 'sapgw<serviceID>' unknownThe following entry is in the dev_eusp<processID> trace file of thegraphical layout editor

"ERROR in RFCMgr_accept: not accepted",and the following entry of the form is in the dev_rfc.trc RFC trace file

"ERROR Service 'sapgw<serviceID>' unknown".The sapgw<serviceID> service (for example, sapgw00) is not recognized onone of the hosts that is participating in the RFC communication because therelevant entry is missing in its service file. The affected host may be thefront-end host or the gateway host.

3. Option: The value for the gw/cpic_timeout system parameter is too lowThis system parameter determines how many seconds the gateway waits for theRFC connection to be set up. If there is a high network load, the defaultvalue of 20 seconds is too low and this means that the connection cannot becreated on time. Here the graphical layout editor process also terminateswith the trace file entry "ERROR in RFCMgr_accept: not accepted".

12.02.2013 Page 2 of 4

SAP Note 101971 - 37527 Graphical full screen is notavailable (RFC)

4. Option: Set the abap/no_sapgui_rfc system parameterThe abap/no_sapgui_rfc profile parameter from the system is set (that is,it has a value not equal to space or 0). This prevents the program of thegraphical layout editor from being started with RFC at the frontend.

5. Option: Unnecessary authorization checkThe system issues error message "No RFC authorization for user xxxxxx",even though the check of the RFC authorization was deactivated by theauth/rfc_authority_check profile parameter (value = space or 0). Thisproblem is caused by a program error that ignores the value of the profileparameter when you call the RFC authorization check (see Note 93254). Thiserror can occur as of Release 4.5.

6. Option: RFC destination with "Unicode communication type"This error can only occur on Unicode systems. The system issues the errormessage "EU_SCRP_WN32: Connection closed (no data)". This indicates thatthe "Unicode communication type" is incorrectly set for the EU_SCRP_WN32RFC destination, which is used to communicate with the graphical layouteditor. The graphical layout editor also terminates here and there areentries of the following type in its trace file

Codepage changed from 4110 to 1160

ERROR in RFCMgr_handleCall: unknown function

SolutionIn relation to 1) If there is a firewall between the front-end host and theapplication server, you must decide whether you want to activate the portfor the RFC connection of the graphical layout editor here. This is port33nn, where nn is the 2-digit system number of the SAP application server.As of Release 3.1G, in addition to the existing SAP GUI connection, thegraphical layout editor requires an RFC connection to communicate with theapplication server. In general, the firewall does not permit such a secondRFC connection because it would contradict the security concept (passwordprotection, logging of the connection).If there is no firewall, you should check whether you can include thefront-end host in the route permission table or whether you can remove thepassword option from the existing entry.For details, you should refer to chapter 4.4 of the attached Note 30289.

In relation to 2) Include service sapgw<serviceID> in the service file.Refer to Note 52959 for details.

In relation to 3) Increase the value for the gw/cpic_timeout systemparameter.60 seconds should be sufficent as a timeout limit. When you check thetimeout, the proposals in Note 581509 may also be useful.

In relation to 4) Set the abap/no_sapgui_rfc parameter to space or to '0'You must restart the application server so that the new parameter valuecomes into effect.

In relation to 5) Import the specified Support Package for the relevantrelease or implement the advance source code correction in accordance withthe attached correction instructions.As a workaround, assign RFC authorizations in accordance Note 93254.

12.02.2013 Page 3 of 4

SAP Note 101971 - 37527 Graphical full screen is notavailable (RFC)

In relation to 6) Call transaction SM59 (RFC Destinations) and, under"TCP/IP connections", search for destination EU_SCRP_WN32. When youdouble-click on the names, the system displays the current settings for theconnection. Select the "MDMP & Unicode" tab and, under "Communication Typewith Target System", select "Non-Unicode". You can use the "ConnectionTest" menu option to make sure that you can now successfully set up theconnections.Comment: The graphical layout editor only permits you to edit screens withnon-Unicode characters. For further information about this, see Note1002845, "Graphic Layout Editor in Unicode systems (II)"

Header Data

Release Status: Released for CustomerReleased on: 21.06.2011 11:18:39Master Language: GermanPriority: Recommendations/additional infoCategory: External errorPrimary Component: BC-DWB-TOO-SCR Screen Painter

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SAP_APPL 30 31G 31I X

SAP_APPL 40 40A 40B

SAP_APPL 45 45A 45B

SAP_APPL 46 46A 46B

SAP_APPL 46C 46C 46C

BC-FES-GUI 60 610 620

BC-FES-GUI 60 640 640

BC-FES-GUI 7.10 7.10 7.10

SAP_BASIS 46 46A 46D

Support Packages

Support Packages Release Package Name

SAP_APPL 45B SAPKH45B26

SAP_BASIS 46A SAPKB46A21

SAP_BASIS 46B SAPKB46B13

SAP_BASIS 46C SAPKB46C05

SAP_BASIS 46D SAPKB46D02

Related Notes

12.02.2013 Page 4 of 4

SAP Note 101971 - 37527 Graphical full screen is notavailable (RFC)

Number Short Text

1480854 Message 37 033: EU_SCRP_WN32 : connection closed (no data)

1002845 Graphic Layout Editor in Unicode systems (II)

898102 Error message "Password in router string."

885581 Message 37 573 "Screen & has not been modified..."

581509 Reasons for "timeout during allocate"

113325 37527 graph. fullscreen does not exist

93254 RFC short dump RFC_NO_AUTHORITY

52959 sapms..., sapdp.., sapgw.. unknown (or not found)

30289 SAProuter documentation

9631 Problems with RFC server programs

Correction Instructions

CorrectionInstructions

Validfrom

Validto

SoftwareComponent

Type*)

ReferenceCorrection

LastChanged

177676 45A 45B SAP_APPL C Y4DK8A04E8 07.07.200017:02:21

177677 46A 46B SAP_APPL C Y9AK004255 07.07.200017:04:01

177678 46C 46C SAP_APPL C Y9CK005668 07.07.200017:06:12

*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work