There is a "Hotfix download available" section at the top of this Knowledge Base article. You cannot change the price of an item to zero by using the Price Override function in Microsoft Dynamics AX for Retail 2009 R2 Refresh POS, even if the item has the Zero Price Valid option enabled.Ī supported hotfix is available from Microsoft. This article applies to Microsoft Dynamics AX for Retail 2009 R2 for all regions. On the positive side there do seem to be a million different ways to do the same thing in NAV, and many of the built in reports are extremely useful assuming that the information in the system is correct.Microsoft Dynamics AX 2009 Service Pack 1 Microsoft Dynamics AX for Retail More.
Perhaps on the accounting end it has some ease of use, but due to how difficult it is to understand on the operations end, the accounting rarely comes out correct due to faulty information in the system. Now having said all that, obviously I am looking at this from a supply chain perspective as it is what I do. All in all, its a sub-par program that you can tell is 5 or 6 different original programs that have been slapped together to try an resemble an ERP system. Our MRP has never worked correctly, so in general, we are forced to use Excel to put together our production schedule.
Microsoft dynamics pos 2009 price code#
The Dimensions on lines can mysteriously disappear, even though the G/L Code and Department code show as filled out in the order. We get a lot of errors where the tables are locked with other users, and you are just stuck until the report or other person finishes up. The easiest way to figure that out seems to require access to the warehouse functionality, which you may or may not want people to have. There are some other basic functionality issues, like figuring out what day you actually shipped or received an item. This same, strange flow of documents, that are essentially intermediary documents only existing to complete a transaction, over complicate what should be a straight forward shipping and receiving process. The only place your purchase order exists in its original form is the in Purchase order Archive, which was never mentioned to us during implementation, forcing us to call Just Foods later on and pay for their customer service. Now once the invoice comes in and is posted against the posted warehouse document, your purchase order disappears. Otherwise, figuring out if you over or under received is difficult at best. At this point your original Purchase order has been changed to reflect what ever was received in, and you have to have a second column to view what you originally ordered. However, once it is received in the warehouse, the receipt document disappears and becomes a posted receipt document (both have completely different document numbers that don't connect to each other). For instance Purchase Orders follow this document flow - First the purchase order is created once you receive your order, a warehouse receipt document is created and received in. This pushed the change to a new ERP and Microsoft NAV was chosen through their partner company Just Foods.Ī truly bizarre system, the flow of documentation through the program makes little sense and over complicates what would normally be easy transactions. The biggest issue seemed to be how incredibly date sensitive how ever without requiring dates at the same time. Our old ERP was limiting, though it was also fairly straight forward. Overall: I have worked in the supply chain for 5 years now and have experience with 3 different ERP's.
0 kommentar(er)
