Parameters (7)

Kind Optional Name Typecast Reference type Defaultvalue
Exporting - EXCEPT_DESCRIPT Type reference (TYPE) OLE_PARAM-CHAR -
Table - PARAMS Type reference (TYPE) OLE_PA -
Table - VARS Type reference (TYPE) SWCBCONT -
Table - VERBS Type reference (TYPE) OLE_VERBS -
Exception - CALL_METHOD_FAILED Type reference (TYPE) -
Exception - GET_PROPERTY_FAILED Type reference (TYPE) -
Exception - SET_PROPERTY_FAILED Type reference (TYPE) -

Coding

OLE_FLUSH_CALL. 
*"---------------------------------------------------------------------- 
*"*"Lokale Schnittstelle: 
*" EXPORTING 
*" VALUE(EXCEPT_DESCRIPT) LIKE OLE_PARAM-CHAR 
*" TABLES 
*" VERBS STRUCTURE OLE_VERBS 
*" PARAMS STRUCTURE OLE_PA 
*" VARS STRUCTURE SWCBCONT 
*" EXCEPTIONS 
*" CALL_METHOD_FAILED 
*" SET_PROPERTY_FAILED 
*" GET_PROPERTY_FAILED 
*"---------------------------------------------------------------------- 
  SET EXTENDED CHECK OFF. 
  DATA: I TYPE I. 
  IF SY-PAGNO IS INITIAL. 
    NEW-PAGE LINE-SIZE 255. 
  ENDIF. 
  FORMAT RESET. 
  LOOP AT PARAMS. 
    READ TABLE VERBS INDEX PARAMS-VERBID. 
    ON CHANGE OF PARAMS-VERBID. 
      NEW-LINE. 
      CASE VERBS-TYP. 
        WHEN 'S'. WRITE: 'Set Property of:'. 
        WHEN 'G'. WRITE: 'Get Property of:'. 
        WHEN 'C'. WRITE: 'Call Method  of:'. 
      ENDCASE. 
      READ TABLE VARS INDEX VERBS-OBJHD. 
      WRITE: (10) VARS-VALUE, VERBS-NAME INTENSIFIED. 
      IF VERBS-ID <> 0. 
        WRITE: 'DispId:', VERBS-ID. 
      ENDIF. 
    ENDON. 
    WRITE: 
           /2  PARAMS-PARNAM INTENSIFIED, PARAMS-OLETYP. 
    READ TABLE VARS INDEX PARAMS-VARINDEX. 
    FORMAT RESET. 
    WRITE: 
           /2 'Value:', (240) VARS-VALUE COLOR 5. 
  ENDLOOP. 
  SET EXTENDED CHECK ON. 
ENDFUNCTION. 

There is only no documentation for this object available. Sorry.

You could find some helpful information in the inline-coding section.

Parameters (7)

Kind Optional Name Typecast Reference type Defaultvalue
Exporting - EXCEPT_DESCRIPT Type reference (TYPE) OLE_PARAM-CHAR -
Table - PARAMS Type reference (TYPE) OLE_PA -
Table - VARS Type reference (TYPE) SWCBCONT -
Table - VERBS Type reference (TYPE) OLE_VERBS -
Exception - CALL_METHOD_FAILED Type reference (TYPE) -
Exception - GET_PROPERTY_FAILED Type reference (TYPE) -
Exception - SET_PROPERTY_FAILED Type reference (TYPE) -

Coding

OLE_FLUSH_CALL. 
*"---------------------------------------------------------------------- 
*"*"Lokale Schnittstelle: 
*" EXPORTING 
*" VALUE(EXCEPT_DESCRIPT) LIKE OLE_PARAM-CHAR 
*" TABLES 
*" VERBS STRUCTURE OLE_VERBS 
*" PARAMS STRUCTURE OLE_PA 
*" VARS STRUCTURE SWCBCONT 
*" EXCEPTIONS 
*" CALL_METHOD_FAILED 
*" SET_PROPERTY_FAILED 
*" GET_PROPERTY_FAILED 
*"---------------------------------------------------------------------- 
  SET EXTENDED CHECK OFF. 
  DATA: I TYPE I. 
  IF SY-PAGNO IS INITIAL. 
    NEW-PAGE LINE-SIZE 255. 
  ENDIF. 
  FORMAT RESET. 
  LOOP AT PARAMS. 
    READ TABLE VERBS INDEX PARAMS-VERBID. 
    ON CHANGE OF PARAMS-VERBID. 
      NEW-LINE. 
      CASE VERBS-TYP. 
        WHEN 'S'. WRITE: 'Set Property of:'. 
        WHEN 'G'. WRITE: 'Get Property of:'. 
        WHEN 'C'. WRITE: 'Call Method  of:'. 
      ENDCASE. 
      READ TABLE VARS INDEX VERBS-OBJHD. 
      WRITE: (10) VARS-VALUE, VERBS-NAME INTENSIFIED. 
      IF VERBS-ID <> 0. 
        WRITE: 'DispId:', VERBS-ID. 
      ENDIF. 
    ENDON. 
    WRITE: 
           /2  PARAMS-PARNAM INTENSIFIED, PARAMS-OLETYP. 
    READ TABLE VARS INDEX PARAMS-VARINDEX. 
    FORMAT RESET. 
    WRITE: 
           /2 'Value:', (240) VARS-VALUE COLOR 5. 
  ENDLOOP. 
  SET EXTENDED CHECK ON. 
ENDFUNCTION. 
Date Views Headline Answers
20.11.2012 93 Check directory_exist 9
13.07.2012 341 AC_FLUSH_CALL - Usage in Custom program 4
30.09.2011 162 runtime error in OLE_FLUSH_CALL 2
28.09.2011 143 Short dump in OLE_FLUSH_CALL 5
01.08.2011 297 Long OLE_FLUSH_CALL times 2
30.05.2011 595 Performance Issue 8
21.02.2011 1578 Exception GUI_NO_MODE_AVAILABLE while sync from Wi 5
17.11.2010 4126 High Roll (in+wait) time & GUI time 13
11.10.2010 606 File display extremely slow with call of OLE_FLUSH 1
07.09.2010 1484 workflow for PO release 15
31.08.2010 430 Issue with ALV sceen called using BDC in new task 1
19.01.2010 2201 Message a000 being raised after cl_gui_cfw=>flu 3
17.08.2009 1502 Extension Structure for EBAN 6
22.07.2009 779 How to read the file_name. 7
03.07.2009 3251 Message_type_X error while starting the BDLSS 5
12.02.2009 1211 DMS BAPI RFC Open DMS document from external appli 4
09.02.2009 2059 Poor performance - network time / RFCs etc. 5
22.01.2009 1041 Exception condition "INVALID PARAM VERB: TEXTSTREA 4
15.01.2009 2445 How to find network performance 7
02.04.2008 571 INVALID PARAM VERB: SECURESAVEDA 1
06.03.2008 2307 Upload excel- multiple sheets 6
31.08.2007 2025 Issue: ES Employee Photo > Preview 18
28.06.2006 1345 Performace issue on ecc6.0 20
15.05.2006 1233 WebGUI Shortdump on SAPMSSYD 4
26.01.2004 0 Slow response - SAP 46C, oracle, HPUX 3
18.11.2005 1996 Performance issues with OLE_FLUSH_CALL 4
26.09.2005 375 Short dump - No empty keys allowed in GUI mode 5
20.03.2003 0 OLE_FLUSH_CALL 2

Name OLE_FLUSH_CALL
Description
Package SOLE
Module SAP Automation Controller (OLE Automation Interface)
Module ID BC-FES-OAC
Creator SAP
Description OLE

Related SAP objects:

NOTE ST06 STAD
» See all 29 related threads

15

Jan 2009

How to find network performance

07:37


SANJAY BHATNAGAR

Hi

We will be getting a connectivity to customers system soon. We would like to analyze the network performance while accessing the system. Can anybody guide me so as how to measure the same?

Will GUI TIME in STAD transaction help?

Thanks in advance.

 

15

Jan 2009

Re: How to find network performance

09:02


Sandeep Nayak

Sanjay,

You don't have to worry about the network performance.

The data transferred for SAP GUI is hardly few Kilobytes.

if the hardware of server is good you wont have much problem at your end.

Regards,

Sandeep Nayak

15

Jan 2009

Re: How to find network performance

11:10


Shabnam Jamal

Hi Sanjay,

Time spent for network communication between the front end and instance is not included

(unless so-called roundtrips to the front end are taking place), although from an

end-user point of view this time might be significant.

Effectively, the application server sends information in chunks

to the front-end PC during so-called round trips. The time spent for a round

trip is called GUI time; this time is measured at the application server. GUI

time comprises time spans for network communication and the time needed to

generate the screen at the front end.

You stated it correctly that it can be seen throough gui times in statistical records. This corresponds to time spent for the communication between application servers and the front-end, and the time is caused by the network time as well as the time that is needed to process the data by the front-end PC.

Also, check for OLE_FLUSH_CALL in the RFC traces.

The high network time may be caused either by a high amount of data that has to be transferred over the network or by a slow network speed. To reduce the amount of data, you can activate the low speed connection. Enable the u2018Low Speed Connectionu2019 option particularly for WAN connections. See SAP NOTE 203924 (Section 5) for details.

The user may deactivate the new visual design to reduce the CPU consumption on his desktop PC or should upgrade the front-end PC. See SAP NOTE 203924 (Section 6) for details.

YOu should also use ST06 --> Detailed analysis --> Lan check by ping for checking on the network traffic conditions.

Regards,

Shabnam.

23

Jan 2009

Re: How to find network performance

12:17


Hi,

Please read SAP NOTE 1100926

31

Jan 2009

Re: How to find network performance

10:00


Rahul Shetti

Hi,

Dignosis with niping utility.

Regards,

Rahul.

01

Feb 2009

Re: How to find network performance

16:26


Rama krishna

Hi ,

Can you please tell us the way to identify the network time as " high".

Kindly provide us the general path for the OLE_FLUSH_CALL RFC trace.

Also, I have noticed a much crude way of identifying the network problem.

If we execute a transaction on the PRD server itself, it is not taking much time.

But if we execute the same transaction on a PC on the network , it is taking too much time

compared to other time. The cause may be due to the delay in the network.

Please provide your suggestions.

Thx,

DVRK

06

Feb 2009

Re: How to find network performance

07:56


Hi Ram Krishna,

I have few points which may help you:

You can calculate the networktime using following fomular.

excerpt from SAP NOTE 578118.

  >

networktime = (no_of_bytes)/(throughput) + (no_of_round_trips)*(RTT)

Please see the NOTE 578118.

Regarding throughput and RTT time, you can get the time via executing NIPING on your side.

Perform a Network Diagnosis with NIPING - SAP NOTE 500235

Long response times on the SAP GUI#    - SAP NOTE 578118

And check the SAP GUI front end patch level of the PCs connected to your SAP network.You can upgrade the patch level which may resolve this FE time.

Thank you,

Tilak