LOAD_SWITCHSTATES_MISMATCH SAP ABAP Runtime Error load switchstates mismatch

LOAD_SWITCHSTATES_MISMATCH 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: I - Internal Kernel 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.

LOAD_SWITCHSTATES_MISMATCH ABAP Runtime Error

As described above, there is a gap in the automatic invalidation logic for ABAP programs. The error can be resolved by regenerating program <runtime parameter>. This should only be done once the error has been analyzed in more detail however, as it makes it impossible to analyze the error again at a later point in time. Check the aggregate switch values of switch <runtime parameter> using transaction SFW1 and check the dependency of program <runtime parameter> on its switches using report RSDEPEND.
It is important that the total change time stamp is not updated for the switches, just the change time stamp itself during the pseudo-include. Current switch states incompatible with program switch states Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.

The switch setting that program <runtime parameter> was created with at <runtime parameter> is incompatible with the current switch setting that program <runtime parameter> should be executed with.
Switch <runtime parameter> currently points to the invalid aggregate value <runtime parameter>, whereas aggregate value <runtime parameter> is expected.

Due to the dependency management between the switch settings and the programs that use the switch, program <runtime parameter> should become automatically invalid as soon as the relevant switch settings change. Due to an internal problem, this did not happen here. The current switch states read for execution of program <runtime parameter> are incompatible with the switch states that program <runtime parameter> was created with at <runtime parameter>.