Users find instances of an item in inventory that claims to be allocated, but no transaction document with the same total allocations for that item exist (allocation enquiry). This happens very frequently and support will be quick to blame 3rd party products, Here I show it happening with base product. So for the question from the user is how could this happen? it is easy to show a sequence of events to replicate it.
The Customer Combiner and Modifier is a tool that allow a customer to be merged into another customer, including account balances and historical records. The source primary records are then deleted leaving one customer. The modifier just allows the "renaming" of a customer id. For the rest of this post I will discuss the combiner, but the principles apply to the modifier too.
A discussion on “The customer combiner” tool/form in Dynamics provokes thoughts on good practice in database field naming. However lets not start there, first instead let me take you through my current thinking. More...
Sales order holds table
This table holds the data relating to process holds on sales orders, the table is shared between work and historical transactions.
Historical transactions will have a posting audit value in the TRXSORCE field, such as :
Work transactions (live orders) will have blank TRXSORCE