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
#Dyn365GP2021.01.26Implementing Post Master Enterprise: Installation
#Dyn365GP2021.01.25Implementing Post Master Enterprise: Prerequisites- #Dyn365GP2021.01.22Implementing Post Master Enterprise: Incompatible Modules
- #Dyn365GP2021.01.21Implementing Post Master Enterprise: What batch types are supported?
