LOAD_REPORT_PART_NOT_FOUND 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.
Check the PART specified in the statement and note in particular that
it has to be written in uppercase. Currently the following PARTs may be
specified: HEAD, TRIG, CONT, DATA, DATV, SELC, STOR, LITL, SYMB, SSCR,
BASE, INIT, TYPE, PBAG, CLAS, EVNT, VTAB, INTI, INTD, OREF, IREF and
CREF.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
LOAD REPORT: PART <runtime parameter> not found
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
The current program contains the LOAD REPORT <runtime parameter> PART <runtime parameter> ...
statement.
PART <runtime parameter> does not exist however.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
LOAD_REPORT_PART_NOT_FOUND - load report part not found LOAD_REPORT_PART_LREF - load report part lref LOAD_PROGRAM_UNICODE_REQUIRED - load program unicode required LOAD_PROGRAM_TABLE_MISMATCH - load program table mismatch LOAD_PROGRAM_NOT_FOUND - load program not found LOAD_PROGRAM_LOST - load program lost