INSERT_REPORT_ILLEGAL_STATE 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.
Please see program correction for more details about the possible cause of this runtime error and how it could be avoided.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
When accessing report or text pool, status is not A or I.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Whe reading, writing, or deleting reports or text elements, you can use
the STATE addition to specify the status 'A' for active or 'I' for
inactive. The runtime error was triggered because a different value was
used ('<runtime parameter>').
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
INSERT_REPORT_ILLEGAL_STATE - insert report illegal state INSERT_REPORT_ILLEGAL_PROGTYPE - insert report illegal progtype INSERT_REPORT_ILLEGAL_FLAG - insert report illegal flag INSERT_REPORT_BAD_EXTTYPE - insert report bad exttype INSERT_REPORT_BAD_EXTENSION - insert report bad extension INSERT_REPORT_BAD_APPTYPE - insert report bad apptype