SAP GUI LoadRunner Commands

The SAP Add-in for LoadRunner provides several sapgui specific functions. A recording of the SAPGUI front end client connecting and logging into the server captured these functions: sapgui_open_connection_ex( sapgui_select_active_connection("con[1]"); sapgui_select_active_session("ses[0]"); sapgui_select_active_window("wnd[0]"); sapgui_window_resize( sapgui_logon( When a SAP transaction/command is specified: sapgui_set_ok_code( sapgui_send_vkey(F4, sapgui_select_menu sapgui_press_button("Enter Times (F5)", btn5, sapgui_select_tab and sapgui_is_tab_selected sapgui_select_active_window("wnd[1]"); sapgui_window_scroll_to_row("0", Actions on a data entry screen: sapgui_set_focus(ctxtBSEG1, sapgui_set_text("Text", "{Text}", ctxtBSEG1, NOTE: Variable-length strings (defined as char*) are automatically created during recording within lr_strings.h for reference in commands. sapgui_set_password( sapgui_set_checkbox( and sapgui_is_checkbox_selected sapgui_select_radio_button( and sapgui_is_radio_button_selected sapgui_select_combobox_entry( sapgui_table_fill_data("Table", tblSAPLCATSTC_CATSD2, "{data}", Verification functions: sapgui_get_active_window_title( sapgui_get_ok_code( in the Command field text sapgui_get_text( sapgui_get_status_bar_text( sapgui_grid_get_cell_data( sapgui_grid_get_rows_count(

Web Services IDoc (intermediate document) provide a standard data container structure for SAP to exchange data between processes, such as asynchronous EDI (electronic data interchange) between application programs written for SAP or between an SAP application and an external program. IDocs is the vehicle for data transfer in SAP's Application Link Enabling (ALE) layer. Different types of IDoc are used for purchase orders or invoices. In other words, an IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another. Each IDoc generated exists as a self-contained text file that can then be transmitted to a receiver (requesting workstation) without connecting to the central database. There are several types of IDoc records: a single Control Record, one or many Data Records, and one or many Status record. Segments and attributes of segments (maximum number, hierarchical sequence, segment status, etc.) are used for interpretating the SDATA field in the data record. Each IDoc consists of several segments and a unique number assigned each iDoc for tracking and future reference. Each segment contain several fields. IDoc data is then converted by SAP's EDI subsystem to a universal EDI standard such as UN/EDIFACT (Electronic Data Interchange for Administration, Commerce, and Trade) or ANSI/X12. Business Application Programming Interface (BAPI) is used for synchronous communication method sRFC because data usually is returned to the sending system. BAPI methods are stored as RFC-capable function modules in the ABAP Workbench Function Builder accessing the SAP Business Object Repository (BOR).