Undefined Symbol Errors When Upgrading from a version to another

This morning, a customer reported the following error while printing their checks remittances: Undefined Symbol F01343D00789 Sequence Num Last week I have upgraded this customer from Microsoft Dynamics GP Version 10.0 with Service Pack 4 to Microsoft Dynamics Version 2010 with Service Pack 1, when the customer sent me the package, I found that the package they sent is mapped to a table called ” PM_Payment_WORK ” while the original reports is mapped to ” pmRemittanceTemp ” then I figured out the reason behind this, this was due to the enhancements applied to this feature in GP 2010. To resolve this, the hard way of doing this is by re-implementing the customizations on the original report.

Originally posted here:
Undefined Symbol Errors When Upgrading from a version to another