Upgrade 4.5B to 4.7 -- ERROR: "VBAK has already been declared".

Question

Dear Friends,
After upgrade 4.5B to 4.7, there is the same ERROR when executing most of SD transaction and creating/displaying/modifying PO and GR.
This error is related to SD pricing procedure. In the ABAP error dump said that: VBAK has already been declared. I have tried to look for SAP Notes but cannot find one.
I think this problem is a common problem in upgrading from 4.X to 4.7. Need help from you guys who ever have upgrading experience.. : )
Does anyone know on how to FIX this problem?
Cheers,
Will
THE ABAP DUMP is as below:
===============================================
Syntax error in program "SAPLV61A ".
What happened?
The following syntax error occurred in the program SAPLV61A :
""VBAK" has already been declared."
Error in ABAP application program.
The current ABAP program "SAPLMEPO" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLV61A ".
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
The following syntax error was found in the program SAPLV61A :
""VBAK" has already been declared."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Information on where terminated
The termination occurred in the ABAP program "SAPLMEPO" in "REFRESH_TABLES".
The main program was "RM_MEPO_GUI ".
The termination occurred in line 35 of the source code of the (Include)
program "MM06EF0R_REFRESH_TABLES"
of the source code of program "MM06EF0R_REFRESH_TABLES" (when calling the
editor 350).
===============================================

Answer 1

Check OSS Note 133433 is exactly axplain your problems
will resolve your problems