Instructions:
In APDiag-OnErrorExecute messages, function IDs are displayed instead of the function names. These function IDs are only of relevance where there are errors in global script actions. What this means in practice during troubleshooting is that the function ID only has to be checked if the OnErrorExecute message contains no information about the picture, object and property. Here is the procedure for identifying the global script action from the function ID:
 

No.	Procedure
1	Insert a global script runtime application window into a WinCC picture. Fig. 01      Note: A global script diagnostics application window has also been inserted in this example.
2	During the WinCC runtime, open the picture with the global script runtime application window. Fig. 02     The global script runtime window lists information about all the global script actions in tabular form. The action can be determined from the corresponding ID here. The reference for determining the global script action from the function ID is only valid until WinCC runtime ends. Note: The global script diagnostics window contains the same outputs as those which appear in the APDiag output window.
3	Evaluate the screen outputs. The function ID "@7" is displayed as a function name in the global script diagnostics window or APDiag output window. You can identify the relevant function name, in this case "Actions.pas", in the global script runtime window. The diagnostic messages indicate that the function is accessing a non-existent tag. In this example, "Actions.pas", the error message is caused by the "GetTagWord()" being called. An attempt is made to access the tag called "Test_Variable01", although it is not created in the tag management. Note: The global script runtime window allows you, among other things, to open a selected action for editing via the pop-up menu.