DBIF_REPO_ILLEGAL_CALL 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: D - Error in Database Interface
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.
- Check the parameters in the ABAP command (the content of the program
name and program part for example).
- Analyze system log entries.
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.
Please see internal call code for more details about the possible cause of this runtime error and how it could be avoided.
Incorrect parameter settings in program interface (<runtime parameter> part <runtime parameter>).
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Various causes:
- Incorrect parameters submitted, such as blank program name or program
name with HEX-0.
- Internal error.
Please see runtime error for more details about the possible cause of this runtime error and how it could be avoided.
DBIF_REPO_ILLEGAL_CALL - dbif repo illegal call DBIF_REPO_END_OF_DATA - dbif repo end of data DBIF_REPO_BUFFER_TOO_SHORT - dbif repo buffer too short DBIF_REPO_ALREADY_ACTIVE - dbif repo already active DBIF_PGNT_UNEXPECTED_CODE - dbif pgnt unexpected code DBIF_PGNT_TABLE_NOT_FOUND - dbif pgnt table not found