Problem while executing SAP transactions

[Former Member]

Dear All,

When I am executing transaction like ME21N, ME51N its going to ABAP runtime error.Below is the runtime error description will you please go through it.

<b>Type group was changed at runtime.</b>

<u>

What happened?</u>

Error in ABAP application program.

The current ABAP program "SAPLMEACCTVI” had to be terminated because one of

The statements could not be executed.

This is probably due to an error in the ABAP program.

<u>

Error analysis</u>

The type group "MMPUR" was changed while the program was running, so that an

inconsistence occurred at runtime.

The type group "MMPUR" has the version 20050805102540.

The program "%_CMMPUR" uses the version 20051012133357.

The internal session was started at 20051121083436.

Please give us the solution as soon as possible...

thanks in advance...

Nagesh Aswartha

[Former Member]

Have the Basis team to look at Versions, Patch levels, LCPs etc in your system. If it cannot be solved by Basis, you need to send the copy of the short dump to SAP for their analysis.

Cheers,

Syd.

[Former Member]

Hi,

Check the user exits. Code in one of the user exits may be causing the problem.

Thanks,

Satyanarayana.

[Former Member]

According to your error analysis type group "MMPUR" was changed while the program was running, so check that type group and try to execute again.

Also check where exactly this error is raising, if error in the user exits then correct the custome code, for me it looks like it is standard code. If the error raises in the standard code then check the OSS notes

Cheers,

Satya

[Former Member]

Hi

Check on the dump (ST22) which is the program that is giving the error (SAPLMEACCTVI), go to transaction SE38 , put the program name there . Then CTRL+F3 (regenerate program) .

This should solve your the issue. This solution is described on SAP Note 589103

Regards

Jose Luis Valverde

[Former Member]

Hi Nagesh Aswartha,

While you on the Debug, try put break points at all the occurences of the message. You do this by just pressing the enter key after /H. Once its in Debug mode follow the path

On the Menu, Breakpoints->Breakpoint at->Statement. At this point you get one pop up. In the Pop up write 'MESSAGE' and press enter. Break point inserted at every occurences of the message and you go on press F8.

Check the place where u r getting the error, and analyze the values in it. You may come to know what is the error and how it is coming in.

probably this may help you.

[Former Member]

Thanks a lot "Jose L. Valverde", your solution worked. Need to analyze how this has happend. Any idea on that????

[Former Member]

Dear All

This post was very helpful for me. We had the same issue and we regenrated the program and it is working now.

The root cause as we identified was creation of new characteristic fields in COPA.

Thanks

Gayani