ABAPEXEC_EXCEPTIONS - EXEC EXCEPTIONS
BAL Application Log Documentation RFUMSV00 - Advance Return for Tax on Sales/PurchasesThis documentation is copyright by SAP AG.
Exceptions
Catchable Exceptions
- Cause: Error when building up a secondary database connection.
Runtime Error: DBIF_DSQL2_CONNECTERR - Cause: The specified secondary database connection is not registered in table DBCON.
Runtime Error: DBIF_DSQL2_CONNECTSTR_ERROR - Cause: Environment variables with errors in table DBCON usedfor connection to SAP or another external database (Multi-Connect). To build up a connection, the environmentvariables are read from the table DBCON and analysed. The check resulted that the values are longer than allowed, or that environment variables are missing when building up a connection.
Runtime Error: DBIF_DSQL2_INVALENV_ERROR - Cause: Illegal disruption of a database selection. The cursor was closed.
Runtime Error: DBIF_DSQL2_INVALID_CURSOR: - Cause: There is already a dataset with the specified key.
Runtime Error: DBIF_DSQL2_KEY_ALREADY_EXISTS - Cause: The specified key was not found in the database.
Runtime Error: DBIF_DSQL2_KEY_NOT_FOUND on a Native SQL database connection. - Cause: No more memory available for a Native SQLStatement.
Runtime Error: DBIF_DSQL2_NO_MEMORY - Cause: The database object already exists in the database. Youtried to create a database object (table, View, Index, ...) in the database. This object already existed.
Runtime Error: DBIF_DSQL2_OBJ_EXISTS - Cause: You used the name of a table or a view that does not exist in the database.
Runtime Error: DBIF_DSQL2_OBJ_UNKNOWN - Cause: SQL Error at the execution of a Native SQLcommand.
Runtime Error: DBIF_DSQL2_SQL_ERROR - Cause: The maximum number of secondary database connections was exceeded.
Runtime Error: EXSQL_CONNECTION_LIMIT - Cause: The maximum number of cursors was exceeded.
Runtime Error: EXSQL_DSQL_CURSOR_LIMIT
Non-Catchable Exceptions
- Cause: The specified cursor does not exist. At a CLOSEor SELECT command in Native SQL, a cursor was specified which is unknown to the cursor administration.
Runtime Error: EXSQL_DSQL_CURSOR_NOT_FOUND - Cause: The specified cursor is already open. A cursor was specifiedat a OPEN command in Native SQL which the cursor administration knows as already opened.
Runtime Error: EXSQL_DSQL_DUPLICATE_CURSOR - Cause: No more roll memory available. When processing a Native SQL Statement, the internal memory is required to prepare the SQL Call.
Runtime Error: EXSQL_DSQL_NOROLL - Cause: An indicator variable has the wrong type. It must have the type INT2.
Runtime Error: EXSQL_DSQL_WRONG_IVAR_TYPE - Cause: The connection name has already been assigned. At an CONNECTcommand in Native SQL, a connection name was specified which is already used for another connection.
Runtime Error: EXSQL_ILLEGAL_CONNECTION - Cause: At a DISCONNECT command in Native SQL, the connection "DEFAULT" was specified. This connection cannot be terminated with DISCONNECT.
Runtime Error: EXSQL_ILLEGAL_DISCONNECTION - Cause: A Native SQL command contains too many variables. As variablesare considered all ABAPfields that are marked with a preceding colon(":") . If the INTOclause has the form INTO :wa for a work area wa, then all the fields of wa are also considered variables.
Runtime Error: EXSQL_TOO_MANY_VARS - Cause: At a SET CONNECTION or DISCONNECT command in Native SQL, a connection was specified that is unknown to the connection administration.
Runtime Error: EXSQL_UNKNOWN_CONNECTION - Cause: Despite the assurance INTO STRUCTURE, the target option, specified in the INTO-clause, is not structured.
Runtime Error: EXSQL_UNSTRUCTURED_INTO - Cause: A LOB Variable has the wrong type. LOB Variables must have the type string, xstring, c, x or n.
Runtime Error: EXSQL_WRONG_TYPE_FOR_LOB
ABAP Short Reference BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 6313 Date: 20120522 Time: 053242 triton ( 226 ms )
