SYSTEM_RESTRICTION_VIOLATION SAP ABAP Runtime Error system restriction violation

SYSTEM_RESTRICTION_VIOLATION is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: A - ABAP Programming Error

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

SYSTEM_RESTRICTION_VIOLATION ABAP Runtime Error

For more information on this topic, see SAP Note 1721077. Invalid statement: <runtime parameter>. This statement cannot be executed in restricted mode. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

The system is in a restricted mode. In this mode, the following statements and operations are not allowed:

- Modifying statements using the Native SQL interface. These statements are called using EXEC SQL. .... ENDEXEC. or ADBC methods. In these cases, it is not possible to call the following operations: Modifying operations on the database - Triggering the databasae commit and rollback - CONNECT TO dbs ... - SELECT operations - Executing DDL statements, database functions and SQL script

- Modfiying operations using the Open SQL interface in the database interface: - INSERT INTO dbtab ... or INSERT INTO (db_expr) ... - UPDATE dbtab ... or UPDATE (db_expr) ... - MODIFY dbtab ... or MODIFY (db_expr) ... - DELETE FROM dbtab ... or DELETE FROM (db_expr) ... - Modifying accesses to shared objects areas - Method ATTACH_FOR_WRITE - Method ATTACH_FOR_UPDATE - Method INVALIDATE_INSTANCE - Method INVALIDATE_AREA - Method FREE_INSTANCE - Method FREE_AREA - Modifying operations using the ABAP file interface - OPEN DATASET dset ... FILTER ... - OPEN DATASET dset FOR OUTPUT ... - OPEN DATASET dset FOR APPENDING ... - OPEN DATASET dset FOR UPDATE ... - DELETE DATASET dset. - SET DATASET dset ... - TRUNCATE DATASET dset ... - Specific local and remote calls from a function module or function using: - CALL FUNCTION func IN BACKGROUND UNIT ... - CALL FUNCTION update_function IN UPDATE TASK ... - CALL FUNCTION func DESTINATION dest ... - CALL FUNCTION func IN BACKGROUND TASK ... - Closing database LUW or SAP-LUW - COMMIT WORK. - ROLLBACK WORK. - COMMIT CONNECTION con. - ROLLBACK CONNECTION con. - The following statements for dynamic programm editing: - INSERT REPORT prog FROM itab ... - GENERATE REPORT prog ... - DELETE REPORT prog. - INSERT TEXTPOOL prog FROM itab ... - DELETE TEXTPOOL. - EXPORT DYNPRO h f e m ID id. - DELETE DYNPRO f. - GENERATE DYNPRO h f e m ID g. - Calling programs: - SUBMIT report ... or SUBMIT (name) ... - CALL TRANSACTION ta ... - LEAVE TO TRANSACTION ta ... - CALL DIALOG dialog ... - Access to data clusters - EXPORT ... TO DATABASE dbtab(ar) ... - EXPORT ... TO SHARED BUFFER ...
- EXPORT ... TO SHARED MEMORY ...
- DELETE FROM DATABASE - Access to the Data Dictionary: - EXPORT NAMETAB

In this case, an attempt has been made to execute statement <runtime parameter>. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.