Ошибка sap abap runtime error

• 31 Oct 2013 5:57 am Rohit Mahajan

  Run transaction ST22 to get the details of the error, and find the one for your particular run.
  It will show the program line where the error occurred.
  Find ‘pernr’ to get the employee’s pers.no.
  Then determine the cause of error
  as below:
  a)In transaction SE38 display the program as above. Go to the line where the error occurred,
  b)Set break point just before the line or at the line.
  c)Re-run the payroll for the employee.
  d)When the program stops at the breakpoint, check all the relevant data.
  e)Where required, execute one line at a time, so that you can understand what is happening.

  Then you should be able to find the reason for the error.

  If the problem is in a custom ABAP function, then consult the programmer.

  If the problem is in a SAP program object,
  1)find OSS notes relevant to the problem.
  2)If there are any, apply the notes in the dev.system, import the employee’s data to the dev test client. Repeat the payroll as above and check if the problem is fixed.
  3)If not found, report the error to SAP with an OSS message and all relevant details of data used, transaction, which pay period, expected results, etc.; follow up with SAP for a resolution

To resolve this issue, you can demark the code base between sapRotWrapper and GuiTree, and provide access of only concern objects to both the classes. 

So, for the codebase share here, what you can do is to access and manage the SAP API connection with sapRotWrapper and then once the data is fetched, you can access the tree control using the GUITree. 

I had update the relevant parts of your code for you.

sapRotWrapper:

using SAPFEWSELib;
//...
sapROTWrapperObject = new SapROTWr.CSapROTWrapper();
sapGUIROTObject = _sapROTWrapperObject.GetROTEntry("SAPGUI");//Get the reference to the Scripting Engine
sapEngineObject = sapGUIROTObject.GetType().InvokeMember("GetScriptingEngine", System.Reflection.BindingFlags.InvokeMethod, null, sapGUIROTObject, null);

sapConnectionObject = sapEngineObject.OpenConnection(sapGUIConfig.EndPoint); 
sapCurrentSession = sapConnexionObject.Children(0);

GuiTree:

GuiTree treeFilters = getTreePath("wnd[0]/usr/ssub%_SUBSCREEN_%_SUB%_CONTAINER:SAPLSSEL:2001/ssubSUBSCREEN_CONTAINER2:SAPLSSEL:2000/cntlSUB_CONTAINER/shellcont/shellcont/shell/shellcont[1]/shell");
                treeFilters.ExpandNode("          1");
                treeFilters.SelectNode("         16");
                treeFilters.TopNode = "         15";
                treeFilters.DoubleClickNode("         16");

I’m using C# in order to automate SAP GUI 7.40 with sapfewse.ocx
(inspired By How do I automate SAP GUI with c#)

I’stuck with an error on runtime when the script have to double click on leef of a tree.

private GuiApplication sapEngine { get; set; }
private GuiConnection sapConnexion { get; set; }
private GuiSession sapSession { get; set; }

sapEngine = new GuiApplication();
sapConnexion = sapEngine.OpenConnection(sapGUIConfig.EndPoint,Sync:true);
sapSession = (GuiSession)sapConnexion.Sessions.Item(0);

// ...

    GuiTree treeFilters = getTreePath("wnd[0]/usr/ssub%_SUBSCREEN_%_SUB%_CONTAINER:SAPLSSEL:2001/ssubSUBSCREEN_CONTAINER2:SAPLSSEL:2000/cntlSUB_CONTAINER/shellcont/shellcont/shell/shellcont[1]/shell");
                    treeFilters.ExpandNode("          1");
                    treeFilters.SelectNode("         16");
                    treeFilters.TopNode = "         15";
                    treeFilters.DoubleClickNode("         16");
    
                    // Crash Here after DoubleClickNode Method
    

SAP ERROR: «The SAP application had to terminate due to an ABAP runtime error.»

Note :

The same automation script manage with sapRotWrapper (SapROTWr.CSapROTWrapper) works

sapROTWrapper = new SapROTWr.CSapROTWrapper();
sapGUIROT = _sapROTWrapper.GetROTEntry("SAPGUI");
//Get the reference to the Scripting Engine
sapEngine = sapGUIROT.GetType().InvokeMember("GetScriptingEngine", System.Reflection.BindingFlags.InvokeMethod, null, sapGUIROT, null);

sapConnexion = sapEngine.OpenConnection(sapGUIConfig.EndPoint);
sapSession = sapConnexion.Children(0);

// ...

sapSession.FindById("wnd[0]/usr/ssub%_SUBSCREEN_%_SUB%_CONTAINER:SAPLSSEL:2001/ssubSUBSCREEN_CONTAINER2:SAPLSSEL:2000/cntlSUB_CONTAINER/shellcont/shellcont/shell/shellcont[1]/shell").expandNode("          1");
                sapSession.FindById("wnd[0]/usr/ssub%_SUBSCREEN_%_SUB%_CONTAINER:SAPLSSEL:2001/ssubSUBSCREEN_CONTAINER2:SAPLSSEL:2000/cntlSUB_CONTAINER/shellcont/shellcont/shell/shellcont[1]/shell").selectNode("         16");
                sapSession.FindById("wnd[0]/usr/ssub%_SUBSCREEN_%_SUB%_CONTAINER:SAPLSSEL:2001/ssubSUBSCREEN_CONTAINER2:SAPLSSEL:2000/cntlSUB_CONTAINER/shellcont/shellcont/shell/shellcont[1]/shell").topNode = "         15";
                sapSession.FindById("wnd[0]/usr/ssub%_SUBSCREEN_%_SUB%_CONTAINER:SAPLSSEL:2001/ssubSUBSCREEN_CONTAINER2:SAPLSSEL:2000/cntlSUB_CONTAINER/shellcont/shellcont/shell/shellcont[1]/shell").doubleClickNode("         16");

Is there somebody can help me ?

Note : I’ve the same graphical troubles on screen during the execution, all components are not well displayed, There’s a link ? (like in the question How to Automate SAP GUI 750 with C#)

Whenever SAP comes across an issue that causes it to stop processing it generates an ABAP Runtime Error. A basic example of this would be a divide by zero but there and many such errors defined in SAP such as DBIF_RSQL_INVALID_REQUEST Invalid Request.

The runtime error would be presented immediately if executing a dialog process but can be recovered any time using transaction ST22. All runtime errors that happen during a background or RFC process are also available via tcode ST22.

The runtime error contains all the details about the type of error as well as the contents of the program variables at the point of the error. for example here is an example of the description you might see for DBIF_RSQL_INVALID_REQUEST.

What Happened? The current ABAP/4 program terminated due to an internal error in the database interface. What can you do? Make a note of the actions and input which caused the error. To resolve the problem contact your system administrator. You can use transaction ST22 (ABAP dump analysis) to view and administer termination messages, especially those beyond their normal deletion date. Error analysis.

In a statement, an invalid request was made to the database interface when accessing the table “EKKO”.

SAP Runtime error transactions and ABAP programs

ST22 –ABAP runtime error
RSLISTDUMPS – List All Runtime Errors and short description
RSSHOWRABAX – Program associated with ST22

SAP Runtime error tables 

SNAP – ABAP/4 Snapshot for Runtime Errors (ST22 list)
SNAPTID – ABAP Runtime Errors – Uses SNAPT as a text table so Includes first text line(TLINE) 
SNAPT – ABAP Runtime Error Texts
SNAPTTREX – Exception table for translation

Runtime Error categories (SNAPTID-CATEGORY)

Field: SNAPTID-CATEGORY
Domain: S380CATEGORY

• I Internal Error
• R Error at ABAP Runtime
• Y Error at Screen Runtime
• D Error in Database Interface
• A ABAP Programming Error
• F Installation Errors
• O Resource Shortage
• E External Error
• U End User Error
• K No Error
• S ST Runtime Error
• J Internal ST Error
• X XSLT Runtime Error& Text Include (no Short Dump, only Text Module)
• & Text Include (no Short Dump, only Text Module)
• B ITS Error
• Q Error in Open SQL
• – Unclassified Error

Most common SAP runtime errors

Below is a list of some of the more common runtime errors including a link to full details of the error and what causes it.

DBIF_RSQL_INVALID_REQUEST

MESSAGE_TYPE_X

TIME_OUT

OPEN_DATASET_NO_AUTHORITY

CONVT_NO_NUMBER

GETWA_NOT_ASSIGNED

TSV_TNEW_PAGE_ALLOC_FAILED

LOAD_PROGRAM_CLASS_MISMATCH

LOAD_PROGRAM_INTF_MISMATCH

An ABAP program can be terminated during its runtime for a number of different reasons. The database table SNAPTID lists all existing runtime errors (in total, around 1900).

To allow clearer processing, the runtime errors are divided into categories: