Today we are announcing that we will end product support and updates for Dynamics GP on the 30th of September 2029 (with security patches ending on the 30th of April 2031).
Enterprises may have subsidiaries in multi countries, in that scenario you can utilize the multi-language capabilities in Microsoft Dynamics AX. This enables translation of the client interface, including menus and data translation. In this blog post I will focus on translation of the shared chart of account functionality, this enables translation of the client interface,
This is about the following report – Procurement and Sourcing / Reports / Status / Accrued purchases. In AX2012 (companing with AX2009) we’ve made a performance improvement of the report by changing it’s datasource. But if you use discounts the report might show you a wrong value. Below you will find a way to resolve
Installing the latest AX kernel version has the advantage of improving the quality and stability of the product because the kernel bundles all fixes checked in up to the release date. Until recently, finding the latest AX kernel version required searching for hot-fixes to specific problems and installing the corresponding KB package. The new feature
There are general ledger transactions posted in correspondence to inventory financial transactions, these transactions may relate to the financial updates of purchase orders and/or sales orders. Inventory transactions posted to general ledger are configured by inventory model groups. In this post I will focus particularly on the post financial inventory option in relation with purchase
There are general ledger transactions posted in correspondence to inventory financial transactions, these transactions may relate to the financial updates of purchase orders and/or sales orders. Inventory transactions posted to general ledger are configured by inventory model groups. In this post I will focus particularly on the post financial inventory option in relation with sales
We are continuing to see a reoccurrence of very similar error messages when using Dynamics Online Payment Services (DOPS) with Microsoft Dynamics AX 2009 and 2012. The resolutions normally deal with the setup and configuration of either AX or DOPS. This blog is intended to cover some of the common errors encountered with the resolutions
Recently I shared a post explaining how to consolidate intercompany vendor invoices. In this post I will cover how to consolidate intercompany customer invoice. In order to achieve the consolidation of intercompany customer invoices the default summary update for the customer should be activated for intercompany customer account, otherwise the arrange function will not be
The intercompany transactions are frequently used between sister companies; at the end of the trading cycle the invoicing should take place. Let us assume that there is trading relation between two sister companies, in daily business practice company A sells goods to its sister company B. The invoices relation could be one invoice for one
AX2012 R3 CU8 introduced exciting new cross-docking functionality for product packages. This article describes the setups that must be in place for cross-docking to work in the warehouse. The 2nd part of the post describes the end-to-end process from the creation of the purchase order through to the shipping of the transfer orders. Â Â
AX2012 R3 CU8 introduced exciting new cross-docking functionality for product packages. This first part of this article described the setups that must be in place for cross-docking. This article describes the end-to-end process from creation of a purchase order through to shipping of the transfer orders. Â Â Â Cross-docking Process The process begins with
When a user tries to change the application of item ledger entries, they can see the following error message: “Remaining Quantity is too low in Item Ledger Entry Entry No.=’341′.” In Dynamics NAV 2013Â we made a much needed change to the inventory costing functionality, and the error message is the result of that: We wanted
I recently worked with a customer whom was in the process of implementing the Production control module in Dynamics AX 2012 R3. Specifically they were trying to figure out why costs weren’t being estimated on Production orders for Components\Raw materials that used a FIFO valuation methodology. Specifically, the scenario was as follows: –Â The finished
