Getting Runtime Error: LOAD_PROGRAM_INTF_MISMATCH

[Former Member]

Experts,

Am getting the following error

Please suggest how why this error was comming and how to resolve this

Runtime Errors LOAD_PROGRAM_INTF_MISMATCH

Date and Time 24.12.2008 12:40:29

Short text

The interface "IF_EX_MB_ME_CSGMT_BADI_SAP" was changed at runtime.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLMEPO" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

The interface "IF_EX_MB_ME_CSGMT_BADI_SAP" was changed during program flow,

which caused

inconsistencies at runtime.

The program "SAPLEINR" uses the interface version 20081224091037.

The program "SAPLMEPO" uses the interface version 20081223194933.

The internal session was started at 20081224124029.

How to correct the error

Try to restart the program.

Trigger Location of Runtime Error

Program SAPLMEPO

Module type (FORM)

Module Name BET_INIT

Please help.

Satya

[Former Member]

hi,,,,,

LOAD_PROGRAM_INTF_MISMATCH error can occur if you applied some corrections and are running the programs for the first time since then. In that case it can happen that some interfaces have to be generated. This could actually be ignored since it will not occur any more if you run the program again.

Thanks

saurabh

[Former Member]

Hi,

Please suggest me what to do to prevent this Dump

Please help me out.

Satya

[Former Member]

Hi Satya,

Check this consulting SAP note Note 351695

Regards

[Former Member]

hi,

you can Activate your program and standard program and execute it once again.

thanks

[Former Member]

Hi,

Thanks a lot...

Its resolved now..

This happened when i have changed the technical setting of a table..

may i know why this causing problem ?

[Former Member]

LOAD_PROGRAM_INTF_MISMATCH error can occur if you applied some corrections and are running the programs for the first time since then. In that case it can happen that some interfaces have to be generated. This could actually be ignored since it will not occur any more if you run the program again.

Thanks

saurabh