A client recently logged a support call whereby reports were showing incorrect information, including for transactions which had been deleted. I did some exploring mof data and found that the Sales Transaction Amounts Work (SOP10200) and Sales User-Defined Work History (SOP10106) tables contained rows for transactions which were not in the Sales Transaction Work (SOP10100) table.
From…
Continue Reading Ian Grieve’s Article on their blog
Identify and Fix Corrupt SOP Transactions in Microsoft Dynamics GP
A client recently logged a support call whereby reports were showing incorrect information, including for transactions which had been deleted. I did some exploring mof data and found that the Sales Transaction Amounts Work (SOP10200) and Sales User-Defined Work History (SOP10106) tables contained rows for transactions which were not in the Sales Transaction Work (SOP10100) table.
Blog Syndicated with Ian Grieve’s Permission
More About This Author
Array
- Dyn365GP1 May 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Understand the Approaches to Configuring a New Company
- Dyn365GP30 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Restore a Deleted Company
- Dyn365GP29 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Refresh an Environment
- Dyn365GP26 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Restore an Environment to a Point in Time