In-Transit Transfer Transactions in Microsoft Dynamics GP 10.0

For those of you who have embarked in the implementation of ITTT, please be aware of the following issues in Microsoft Dynamics GP 10.0:

1. When you post an In-Transit Inventory transaction at the transaction level from the Receivings Transaction Entry window, posting will finish. However, the data in the Inventory tables will be incorrect. You can navigate to the Receivings Transaction Entry window from the Transactions menu, point to Purchasing, and then click Receivings Transaction Entry.

2. When you try to post a Purchasing Transaction batch from the Purchasing Batches window that contains an In-Transit Inventory transaction, the processing stops with the progress bar at 100% and the posting process does not finish. You can navigate to the Purchasing Batches window from the Transaction menu, point to Purchasing, and then click Purchasing Batches.

The above issues have been resolved with the latest patch release for Microsoft Dynamics GP 10.0. (Service Pack 1).

3. When you use the In-Transit Transfer in the Receivings Transaction Entry window the quantity decimal places are being truncated to 0, therefore, only showing a whole number. This is causing the quantity to only partially transfer.

4. When you post an In-Transit Transfer transaction from the Receivings Transaction Entry window or Receiving Batches window, the incorrect account is used when using site segments. The debit and credit both pull from the To Site account.

5. When you post multiple in-transit transactions on one In-Transit inventory receipt, duplicate records are created in the Inventory module without posting the transactions to the Purchase Order Processing tables. This problem occurs when you save the transactions to a batch, and then print the edit list. To work around this issue, follow one of these methods:Use transaction level posting instead of batch postingPost the transaction by batch without printing the edit list

6. When you use the in-transit transfer functionality in the Receivings Transaction Entry window, the currency amounts are rounded to 2 decimal places instead of remaining at 3 decimal places.

Because of these issues, it is recommended that you do not use the In-Transit Transfer functionality in Microsoft Dynamics GP 10.0 at this time. Microsoft has confirmed that this is a problem with the Inventory module and is working to correct the issue, which will probably be delivered with Feature Pack 2 (that's right a Service Pack with more functionality!).

Until next post!

MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Is there anything new on this article, we attend to start using In-Transit Transfer Transactions instead of Item Transfer Entry.
Mariano Gomez said…
These issues have been resolved long time ago. Make sure you are running SP4 or the latest hotfix.

MG.-
We are running SP3, FP1.

I had install SP4 some time before, but its cause me some problems. So, I'm not sure if am going to do it again.
dtmMichael said…
Is there a resolution for existing in-transit transaction that were posted prior to the SP4 being applied, they are 'lost'
Mariano Gomez said…
@Michael,
I don't think so. You may want to check with Microsoft Support.

MG.-
Mariano Gomez, MVP

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

eConnect Integration Service for Microsoft Dynamics GP 2010