Microsoft Dynamics 365 for Finance and Operations (or Dynamics AX) was an ERP product in the Dynamics family. It has been split into separate Dynamics 365 products to provide more flexibility to customers, allowing users to pay only for the functionality they need. Microsoft Dynamics AX will reach end of support in 2021, and end of extended support in 2023. Financial tracking and budgeting features are now found in the newly launched
BizTalk is well suited as middleware. Where you wish to translate an input file into an output file and send it to some endpoint. In our case, we used it to convert and send files to SAP. In many ways, it very flexible, and you can do almost anything you want with it. In many ways, it's a better solution than your SAP XI or PI as middleware, since it's much less expensive, and allows you do interface with non-SAP systems.
It integrates fully with the other Microsoft software we use daily, and this coordination speeds up our work and gives us the agility to run easily. For example, in a purchase inquiry, the customer, after submitting a request, identifies the teams that should work on the project, and if they need further review by other people, they are added to the process, and everything is managed seamlessly rather than the sales process. Get the result as fast as possible.
It is very user friendly. Users can change rules during run time and change workflow.
Huge capacity for queueing messages. It supports all types of adapters like Oracle, Salesforce, SMTP, FTP, etc. Also users can built custom adaptors.
If users want to dynamically deploy their solution without any downtime, this is a perfect solution. BizTalk will be a good fit, especially for public-facing websites.
Well-proven in the market. I used it when developing a website for Virgin Trains, catering more than 800K user requests per day.
Microsoft Dynamics AX's scalability to meet our regional office needs provide flexibility to the team's requirements.
Combined with Citrix Xenapp, the application offers seamless access for users on high latency unreliable network connection to the application.
Application maintenance and updates are easy which makes it possible for us to manage remotely considering the servers are located in a remote Asia site.
MRP can be slow to adapt to changes in actual production or supply chain transactions.
Setting up number sequences seems a trivial matter, but these numbers ID transactions once they are in the ledger and are key--easy to miss this point in the implementation process.
Bank rec being easily automated and able to quickly plug into a bank back end to get data is not the best.
Payment processing can be 'clunky' based on checks, ACH, Wires...as some of these items are not triggered out of the box in AX, bur are easily added --talking ACH and Wires specifically.
Microsoft Dynamics continues to evolve by bringing more functionality to the customer. Also there are several independent software providers that offer a wide range of solutions for vertical markets.
Overall the product does what we need it to do in order for us to function as a company. While there are some concerns over ongoing costs, the belief is, once we have it fully acclimated to our business the cost should settle into alignment with our original expectations. The new features that are consistently being added do add value to the product as they are usually customer request directed.
Some integration and high volume ramping challenges, particularly with BizTalk and SQL Server, but getting sorted out. Outages over time appeared to be more dependent on integration complexity than AX MES.
Some integration and high volume ramping challenges, particularly with BizTalk and SQL Server, but getting sorted out. Outages over time appeared to be more dependent on integration complexity than AX MES.
BizTalk Server has been supported for more than 15 years. It is well proven in the market. Microsoft has provided excellent support with technical issues.
We use a 3rd-party Microsoft Partner for the system. They are responsive and very knowledgeable. While costs have been mentioned several times in this review they are very aware of costs and have developers who are more economical they use to help offset the level of work required to meet our changes and fix our issues.
It took a lot of work, but Microsoft ultimately did a good job with in-person training, including being onsite in multiple global locations for extended periods.
Our solution deviated from a number of key out-of-the-box standards that were included in Online training. We just used that for introduction to the general functionality.
Some rough spots, but ultimately worked out. The contract didn't appear to be structured to support the level of overlapping facility deployments required to meet timeline commitments. Merging cultures on the program was also challenging. Overall, not an easy implementation by any stretch. Everyone did the best they could.
BizTalk was selected here mainly because it is easy to integrate to a .NET application (most of them are Web Service, WCF SOAP, WCF REST and Web API) and many backend databases are Microsoft SQL Server. Another benefit is that the monitoring job is easy to set up and centralize with other .NET application monitoring jobs.
I was not part of the decision making process to select Microsoft Dynamics AX, however, I do know that an exhaustive search was done and many options were considered alongside Microsoft Dynamics AX and I feel that the right decision was made in choosing this solution.
A positive impact has been the quicker turnaround time of a part request and that part showing up in SAP using Biztalk as middleware.
A somewhat negative impact has been the somewhat insufficient error logging/message capture settings that Biztalk provide. This has caused occasional delays when attempted to create parts for the business.
A somewhat negative impact has been the need to have a specialized developer who understands Biztalk to troubleshoot issues with the Biztalk and SAP interaction when creating parts, and when adding new fields to the parts.
