Description

When running a script that has been created in GUI Scripting mode, the record fails to update and a "Control ID could not be found" error appears in the Log Column.

Applies to

Scripts that have been written in GUI Scripting Recording Mode using any version of Transaction or Studio.

Cause

This is a general error when using GUI Scripting Mode that occurs any time the script is not able to find an element in SAP that it is supposed to interact with. In this case, elements can be data fields, GUI controls, items in a hierarchy tree, etc.

Solution/Immediate Workaround

Run the script in Debug Mode and walk through each step in the script to determine where the failure is occurring. Once the step that is failing has been identified, determine if it is an issue that is particular to that record that needs to be addressed, or if the script should be modified to correct the error. 

If the script is working for one user, but not another, it is likely due to differences in the layout of the SAP screen. When updating fields in a table, there is a position identifier on that field name in the mapper that indicates the row and column where the script would expect to find that field. Differences in layouts can impact the positioning of fields or controls and cause the Control ID not found error.