> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/error-logs/errors/action/sap-actions.md). # SAP Actions The following are the errors that can occur while using SAP actions. | Error | Description | Solution | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **LaunchApplication**(**SAP**): The given window name is not found | This error occurs when the **Launch Application** action is used for SAP, the window name & path provided in the **Input Value** column does not match the actual SAP application window and path. | Provide the correct application path and window name in the format:**\; \** (e.g., C:\Program Files (x86)\FrontEnd\SapGui\App.exe; SAP Logon 760).Ensure the executable path is valid on the execution machine and the window name matches the SAP window exactly. | | **SAP ServerConnectError occured** : Given Server discription is incorrect, (-2147352567, 'Exception occurred.', (614, 'saplogon', 'The enumerator of the collection cannot find an element with the specified index.', 'C:\Program Files (x86)\SAP\FrontEnd\SapG ui\saplogon.HLP', 393215, 0), None) | This error occurs when the **Server Connect** action is used for SAP and the server description provided in the **Input Value** column does not match any entry in the SAP Logon connection list. |

Ensure the entry exists in SAP Logon on the execution machine, and the name matches exactly, including spacing and case. For example: SAP HANA

| | Unable to launch the application | This error occurs when Avo Assure fails to start the specified application. This may happen due to an incorrect application path, missing executable, insufficient permissions, or application compatibility issues. | Verify the application path, ensure the executable exists, confirm sufficient permissions, and check that the application is compatible with the operating system. | | Incorrect file path or window name (Launch Application) | This error occurs when the Launch SAP Application action receives a file path that is incorrect or a window name that does not identify a valid SAP GUI window. | Verify the SAP GUI executable path is correct and the window name matches the SAP application title exactly. | | Unable to launch SAP application / SAP launch error code: \ | This error occurs when the SAP application process fails to start — for example, the executable is blocked, the SAP GUI is not installed, or the OS returns a specific error code (listed in SAP\_ERROR\_CODES). | Verify SAP GUI is installed, the executable path is correct, and the user has permission to run it. Refer to the error code in the message for the specific OS-level cause. | | SAP Logon window does not exist (Server Connect) | This error occurs when the **Server Connect** action cannot find the SAP Logon window on the execution machine — SAP Logon is not running or the window title does not match. | Ensure SAP Logon is running before executing Server Connect, and verify the window title in the configuration matches the actual SAP Logon title. | | Given server description is incorrect (Server Connect) | This error occurs when the **Server Connect** action cannot find the specified server in the SAP Logon system list, or the server description is misspelled. | Verify the server description matches exactly as it appears in the SAP Logon list, including case and spaces. | | Unable to Find Logon Button or Filter Text Box (Server Connect) | This error occurs when Server Connect locates the SAP Logon window but cannot find the logon button or the server filter field, typically due to a version mismatch or UI change in SAP Logon. | Verify the SAP Logon version is supported and the logon window is fully loaded before Server Connect runs. | | Session not found (Start Transaction) | This error occurs when the Start Transaction action cannot obtain an active SAP session - no SAP GUI session is open or the session object is unavailable. | Ensure Launch SAP Application and Server Connect have run successfully and a valid SAP session is active before executing Start Transaction. | | SAP Session and Window not found (Status Bar / Close Window) | This error occurs for multiple actions: when Get Status Bar Message or Close Window cannot retrieve the SAP session and application window - the SAP GUI session has been closed or is not accessible. | Verify the SAP session is active and a screen is open before executing the action. | | Element is not GuiModalWindow or GuiMainWindow type (Close Window) | This error occurs when the **Close Window** action targets an element that is not a GuiModalWindow or GuiMainWindow SAP control type. | Verify the element captured for Close Window is the main window or a modal dialog. Recapture the correct window element. | | Element is not GuiModalWindow type (Get Window Name) | This error occurs when the **Get Window Name** action targets an element that is not of type GuiModalWindow. | Verify the element captured is a modal dialog window. Recapture the correct modal element. | | No message displayed in status bar | This error occurs when the Get Status Bar Message action reads the status bar and finds it is empty — no message has been set by the SAP application. | Verify a preceding action has triggered a status bar message before running Get Status Bar Message. | | No message, unable to perform DoubleClick on status bar | This error occurs when the **Double Click Status** Bar action finds the status bar is empty, there is nothing to double-click. | Ensure a status bar message exists before executing Double Click Status Bar. | | Button is disabled (Toolbar Action) | This error occurs when the Toolbar Action keyword targets a toolbar button that is present but in a disabled state. | Verify the toolbar button is enabled at execution time. Add a wait/ verify enabled step if the button is enabled dynamically. | | Could not find the specified button (Toolbar Action) | This error occurs when the Toolbar Action keyword cannot find a toolbar button matching the given name or ID. | Verify the button name or ID matches exactly as it appears in the SAP toolbar. | | Unable to find the menu item (Select Menu) | This error occurs when the **Select Menu** action cannot locate the menu item specified either the menu path is wrong or the item is not visible. | Verify the menu path matches the SAP application menu exactly, including item names, separators, and case. | | Invalid Input / Invalid element type (Get Popup Text) | This error occurs when the **Get Popup Text** action receives an empty input or targets an element that is not a SAP popup/dialog type. | Ensure the element captured is a SAP popup window and provide the required input value. | | Element is not present on the page where the operation is trying to be performed | This error occurs for multiple actions: when any SAP action resolves the SAP element ID but cannot find the element using FindById in the current session — the screen has changed or the element is not on the current SAP screen. This also applies to Get Text, Set Text, Set Secure Text, Clear Text, Verify Text, Get Textbox Length, and Verify Textbox Length when the SAP textbox element cannot be found in the current session. | Verify the correct SAP screen is active and navigate to the expected screen before running the step. Recapture the element if the screen layout has changed. | | Element is not changeable, element state does not allow to perform the operation | This error occurs for multiple actions: when Set Text, Select Radio Button, Select/Unselect Checkbox, or Upload File targets a SAP element that is read-only or not interactive on the current screen. This also applies to Set Text, Set Secure Text, and Clear Text when the SAP textbox field is read-only or not in edit mode. | Verify the field is editable on the current SAP screen. Some fields become editable only in change/edit mode — ensure the SAP screen is in the correct mode before the step. | | Invalid element type, element state does not allow to perform the operation | This error occurs for multiple actions: when Get Count, Select Tab, Verify Tree Path, Verify Values Exists, or Get Row Count is executed on an element whose SAP control type does not support the operation. This also applies to Get Text, Set Text, Clear Text, and Get Textbox Length when the element is not a GuiTextField or GuiCTextField type. | Verify the captured element is the correct SAP control type for the action (for example, a ComboBox for Get Count, a GuiTab for Select Tab). | | Element is disabled | This error occurs when the **Verify Enabled** action checks the SAP element and finds it is disabled. | Verify the element is expected to be enabled on the current SAP screen and that the screen is in the correct mode. | | Element is enabled | This error occurs when the **Verify Disabled** action finds the element is currently enabled rather than disabled. | Verify the application flow actually disables the element before this verification step. | | Element is visible | This error occurs when the **Verify Hidden** action finds the element is currently visible on the screen. | Verify the application flow actually hides the element before this step. | | Element is hidden | This error occurs when the **Verify Visible** action finds the element is not visible on the current SAP screen. | Verify the element is displayed on the current screen and navigate to the correct SAP transaction before the step. | | Element not present, unable to highlight | This error occurs when the **Verify visible** action cannot find the element and the highlight attempt also fails — the element is absent from the current screen. | Verify the correct SAP screen is active and the element exists. Use a **VerifyExists** step after navigating to the right screen. | | Entered text is empty / Input value is invalid | This error occurs for multiple actions: when **Verify Element Text** or **Verify Text** receives an empty expected value, or a SAP action receives an invalid input. | Provide a valid, non-empty expected value in the Input Value column. | | Entered text is empty / Input value is invalid | This error occurs for multiple actions: when **Verify Element Text** or **Verify Text** receives an empty expected value, or a SAP action receives an invalid input. | Provide a valid, non-empty expected value in the Input Value column. | | ToolTipText not available for the element | This error occurs when the **Get Tooltip Text** action hovers the element but no tooltip text is present for it. | Verify that the element actually shows a tooltip in the SAP application. Not all SAP controls have tooltips. | | ToolTipText does not match input text | This error occurs when the **Verify Tooltip Text** action compares the input value with the element's tooltip and finds a mismatch. | Verify the expected tooltip text matches exactly, including case and spaces. | | Icon name does not exist for the element | This error occurs when the **Get Icon Name** action targets an element that does not have an associated icon. | Verify the element is an icon-type SAP control before using Get Icon Name. | | Value did not match (Verify Icon Name) | This error occurs when the **Verify Icon Name** action compares the input value with the element's icon name and finds a mismatch. | Verify the expected icon name that matches the SAP icon identifier exactly. | | No input help is available | This error occurs when the **Get Input Help** action is executed on an element that does not provide F4 input help in the SAP application. | Verify the field supports F4 input help in the current SAP context. | | Scrollbar cannot be moved | This error occurs when the Scroll Up/Down action cannot operate the scrollbar — either the scrollbar does not exist for the element or the scroll operation is blocked. | Verify the element has a scrollbar and content to scroll. Use a different scroll method if the SAP control does not support this scroll type. | | Button name is not defined | This error occurs when the **Get Button Name** action reads the Text property of the SAP button element and finds it is empty. | Verify the button element has a visible label in the SAP application. | | Button name does not match | This error occurs when the **Verify Button Name** action compares the input value with the SAP button's text and finds a mismatch. | Verify the expected button name matches the actual button label exactly, including case and spaces. | | Input text and Element text do not match (Verify Selected Value) | This error occurs when the **Verify Selected Value** action compares the expected input value with the currently selected SAP ComboBox value and finds a mismatch. | Verify the expected value matches the selected item text exactly and that the correct option has been selected before the verification step. | | Count Verify has failed | This error occurs when the **Verify Count** action compares the expected count with the actual number of items in the SAP dropdown and finds a difference. | Verify the expected count and ensure the dropdown is fully populated before the verification step. | | No matching data found (Verify Values Exists) | This error occurs when the **Verify Values Exists** action searches the dropdown options and none match the provided input value. | Verify the expected value exists in the dropdown option list and matches exactly. | | No matching text found in the table / No matching text found in shell | This error occurs for multiple actions: when Get Column Number By Text or Get Row/Column By Text searches the SAP table or shell grid for the given text and finds no matching cell. | Verify the search text exists in the table/grid at execution time, including exact spelling and case. | | Index value of row or column is negative or not valid | This error occurs for multiple actions: when Get Cell Value, Select Row, or Select Column receives a row or column index that is zero, negative, or non-numeric. | Provide a valid positive integer for the row and column index, starting from the first row/column as applicable. | | Cell value and Input value do not match (Verify Cell Value) | This error occurs when the **Verify Cell Value** action compares the expected input with the actual SAP table cell value and finds a mismatch. | Verify the expected value matches the cell content exactly. Use Get Cell Value first to confirm the current value. | | Error: Type Mismatch (Get Cell Status) | This error occurs when the **Get Cell Status** action targets a table cell whose SAP control type does not match the expected radio or checkbox type. | Verify the correct cell is targeted and that it contains a radio button or checkbox control. | | Index value of row/column is negative or not valid (Select Row/Column) | This error occurs when Select Row or Select Column receives a negative or non-numeric index. | Provide a valid positive integer for the row or column index. | | Element is not a shell object | This error occurs for multiple actions: when Get Row Count, Click, Get Row/Col By Text, or Select Context Menu By Text is executed on an element whose SAP type is not GuiShell. | Verify the captured element is a SAP GuiShell control (ALV grid, tree, calendar, toolbar) and recapture if the screen has changed. | | No matching text found in shell (Get Row/Col By Text) | This error occurs when the Get Row/Col By Text action searches all cells in the shell grid and finds no cell matching the given text. | Verify the search text exists in the grid at execution time and matches exactly. | | Row and column values are incorrect (Get Cell Text) | This error occurs when the **Get Cell Text** action is given row/column values that are out of range for the current grid. | Verify the row and column numbers are within the grid's actual dimensions. | | Element is not changeable / Out of bounds exception / Element has zero row count (Set Cell Text) | This error occurs for multiple actions within Set Cell Text: the target cell is read-only, the row/column index is out of bounds, or the grid has no rows. | Verify the cell is editable, the row/column index is valid, and the grid contains data before calling Set Cell Text. | | Unable to press button / Button does not exist (Press Toolbar Button) | This error occurs when the **Press Toolbar Button** action cannot find or press the specified toolbar button — the button ID or name is incorrect or the button is not on the current toolbar. | Verify the toolbar button ID matches exactly as it appears in the SAP toolbar. Use Get Toolbar Buttons to identify available buttons. | | Column header/headers do not exist (Get Column Number By Header) | This error occurs when the **Get Column Number By Header** action searches the grid column headers and finds no match for the given header text. | Verify the column header text matches exactly as it appears in the ALV grid, including case and spaces. | | Invalid index / Invalid row count (Get Cell Color / Scroll To Row Number) | This error occurs for multiple actions: when Get Cell Color or Scroll To Row Number receives an index or row number that is out of range for the current grid. | Verify the index/row number is within the grid's actual row count. | | Column Number exceeds the number of columns / Column not found (Tree Traverse) | This error occurs when the Tree Traverse action is given a column number larger than the number of columns in the tree, or the column identifier cannot be found. | Verify the column number is within range or the column name matches exactly. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.avoautomation.com/avo-assure/error-logs/errors/action/sap-actions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.