sap-gui-object-details

To inspect SAP GUI components during automation issues, you can dump the active screen's component tree to identify unexpected popups, greyed-out fields, or changed control IDs. This requires an active SAP GUI session with sapgui/user_scripting enabled.

The best way to extract SAP GUI component IDs and properties is by running an inspection in tree, wnd, menu, type, or id mode. These modes dump full component trees for all windows or provide a full property dump for a specific component path to resolve screen flow issues.

Yes, you can inspect a specific SAP GUI control path by using the id inspection mode. This mode targets a specific component path to provide a full property dump, rather than extracting the entire window or full component tree like the wnd or tree modes.

Yes, you must enable sapgui/user_scripting on the server to extract SAP GUI screen component data. An active SAP GUI session with this scripting setting enabled is a strict prerequisite for inspecting and dumping component IDs and properties.

SAP GUI scripts fail when control ID drift occurs across releases because automation scripts reference hardcoded IDs. You can use an inspection tool to dump the current component tree and properties, allowing other scripts to dynamically discover the actual current screen state and adapt.

Five SAP GUI inspection modes are available for diagnosing unexpected screen behavior: tree, wnd, menu, type, and id. They support dumping full component trees for all windows, a single window, or a full property dump for a specific component path.