I admit, I am not enough of a Dynamics GP geek to thoroughly review all of the new features and enhancements that come out with each new version (okay, that can actually mean that I'm lazy). I typically glance at the GP team's features of the day blog posts, but that's about it.
Normally this doesn't pose much of an issue, but the other day I needed to solve a problem, and I was at a disadvantage since I didn't know about a new enhancement in GP 2013 that will meet the requirements quite nicely.
The issue was that a customer was importing inventory adjustments from another system to maintain inventory quantities in Dynamics GP. When a receipt is submitted to their operational system, an inventory transaction is integrated into GP. There is a lot of background to the story, but I'll skip the gory details.
This integration works great, and the inventory transactions work fine for the client, but they wanted a way to differentiate these imported inventory transactions from any other inventory adjustment that they enter manually into GP. I thought that would be tough, since there is no description field on the Item Transaction Entry window or lines. Fortunately, I called in my colleague Gina and ran the idea by her, and she asked somewhat quizzically, "Why don't you just use the new Reason Code field?". Uh, ya, sure, that's what I was thinking...
The Reason Codes must be pre-defined, which is a good thing. Each reason code can have a description, and you can control which transaction types the reason code can be used with. So some reason codes can be used for Adjustment and Variance transactions, while others might only be used for different types of transfers.
Additional Note: I forgot to check the eConnect 2013 documentation for the new field. Fortunately, the Reason Code field is available for the taIVTransactionLineInsert and taIVTransferLineInsert, so that is good news.