SAP Actions
The following are the errors that can occur while using SAP actions.
LaunchApplication(SAP): The given window name is not found (SAP)
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:<application path>; <window name> (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) (SAP)
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.
Provide the correct SAP server description exactly as it appears in the SAP Logon connection list (e.g., the connection/system name shown in SAP Logon).
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 (SAP)
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.
Error occurred due to unexpected alert #
This error occurs when an unexpected alert or pop-up appears during execution, preventing Avo Assure from interacting with the application.
Handle or dismiss the unexpected alert before continuing execution or add appropriate alert-handling steps in the test case.
Element not found #
This error occurs when the captured element cannot be found on the application screen during execution, or when the element's properties have changed, causing Avo Assure to be unable to locate or interact with it.
Verify that the target element is present on the application screen during execution. If the element has changed or cannot be identified, update its object properties in the Element Repository and recapture the element if necessary before retrying the execution.
Values does not match #
This error occurs when Avo Assure compares the expected value with the actual value obtained during execution and finds that they do not match. As a result, the verification fails and returns a False status.
Verify both the expected and actual values, and ensure that the application contains the correct data before executing the verification.
Last updated