Спасибо большое за ссылку. Так и есть – ошибка GUI Scripting "
Control ID not found".
Относительные/полные-тех имена полей оказвается зависят от настройки подключения Low/High Speed Connection соответсвенно.
И, как вишенка на торт, "изящное решение" (спойлер - его нет):
Code:
To ensure that you do not get this error, record the script in a system that has the same connection speed setting as the system where the script will be run. To view the connection speed settings, right-click the system name in the SAP Logon Pad, click Properties, and then click Network. The connection speeds are listed under Network Settings.
Руки бы вынуть разработчикам этого "подукта".
Еще немного текста из ссылки.
Code:
Depending on the SAP system connection speed, the field names are represented differently in the recorded GUI Scripting script. If Low Speed Connection is selected, the fields will be represented using relative naming. If High Speed Connection is selected, the fields will be represented with their full technical names.
A script that is recorded in a Low Speed Connection system will fail when it is executed in a High Speed Connection system. When the script reaches the screen that contains the first field, it will likely return a "Control ID not found" error in the log for the first field.
In the example below, rows 6 and 7 (customer and company code) are represented differently in the recordings carried out in different SAP clients:
Relative field names (Low Speed Connection)
Full technical field names (High Speed Connection)
For more information, refer to the following SAP Notes:
- 587202 Restrictions when using SAP GUI scripting
- 161053 Using SAP GUI in WAN
Вход
Регистрация
FAQ пользователя
Поиск
) нативного решения этой проблемы нет и надо принудительно советовать пользователям переключаться в тот режим подключения в котором записаны скрипты, ну или в коде делать сразу в двух версиях.