Dynamics AX Users Changing Course in How They Manage EDI Requirements

With most any Microsoft Dynamics AX project, a focus around EDI needs for such projects is always a hot topic. In the past, there have been a slew of ways to solve the challenges that EDI represents for customers. Like most things, the entire drive is towards value and the act of reducing time to value for customers.

With this in mind, I thought it was time we visited back with Data Mason's own Glenn McPeak, to get their feedback on the trends they are seeing in the market place. Being the leader for EDI within the Dynamics Ecosystem, it would make sense that they have the most to share around this topic. With that, the following is the information Glenn sent me on the matter.


Glenn McPeak - Principal of Data Mason's

We’ve been seeing a rapidly growing trend in the Dynamics community when it comes to how companies want to manage EDI. Up until now, it seemed that companies were selecting one of numerous options to meet their EDI mandates, but now we’re seeing a shift in what they are looking for when it comes to EDI for Dynamics AX.

Here’s What’s Trending:

#1 – End to end automation
Pushing a button to integrate a transaction used to be great as it saved time over manual entry. But now users are asking, “Why do I have to push a button and who is going to do it at 2am?” They want automation of key EDI process that gives them the flexibility and security they’re looking for.

#2 – Manage EDI by exception
Dynamics users don’t want to deal with every transaction, only the issues that need attention. Managing by exception lets the transactions without discrepancies continue without interruption and eliminates unnecessary manual touch points.

#3 – Leverage standard Microsoft integration framework
Writing directly to tables and bypassing business logic is not best practice. By leveraging integration tools such as Microsoft’s e-Connect, Application Integration Framework(AIF) and XMLports/Web Services, users can avoid custom routines that populate data and bypass standard business logic.

#4 – Deeper and broader integrations
Users need more advanced logic, such as touching specific values in a sales order or handling advanced three-way matching logic. They also need broader document integrations so they can get new documents integrated quickly and easily to avoid jeopardizing trading partners relationships.

#5 – Avoid transaction fees
EDI data is a lot like email – would you pay to send an email? Right, then why pay for transactions when you don’t need to, especially when your trading partners support direct connect?

#6 – Audit the transactions
Too many companies complain about the lack of tools available that can identify issues before they become problems. They wonder why they can’t find out that an invoice was not transmitted and/or received by a partner before it is overdue. They would rather receive an email alerting them when a document has failed.

#7 – Guaranteed support turn-around times
In the world of EDI where delays and errors in transacting data can result in unnecessary and costly expense, organizations don’t have the flexibility of waiting for support responses.

Answering the Trends Responding to these trends is an innovative EDI technology model that Dynamics users are rapidly adopting. Users are looking to an EDI solution that is based on leveraging the native integration framework of the ERP platform while providing all of the EDI transaction functionality outside the application¸ not inside like other EDI technologies. With this approach, companies can:

• Implement a plug-and-play, truly integrated solution that doesn’t utilize 3rd party translator tools;
• Leverage a fully-automated EDI solution with predictable ownership costs; and
• Benefit from a non-embedded design and XML data storage within SQL that avoids ERP requirements and customizations, simplifying daily use and providing flexibility when managing ERP update/upgrade projects.

The Next Step with EDI Learn more about this growing trend in Dynamics EDI and what your EDI solution should deliver. Read how other companies have successfully implemented a new strategy to increase the impact EDI has on their business and how they have exceeded their expectations in simplifying EDI integration and compliance.

I would like to thank Glenn, and the Data Mason's team for being sponsor's of this blog and for always helping add great value added information, content & solutions around EDI to the Dynamics Ecosystem at Large.

That's all I have for this post, make sure and check back soon as we continue our dive into the Dynamics filled world, and further drive towards value! Till Next Time!

Follow Me @:
       

"Visit the Dynamics AX Community Page today!"

AX 2012 - Leveraging EDI Technology to Eliminate Unnecessary Platform Customizations

Here we are coming up on Convergence 2012, nearly a year since Steve Ballmer and Kiril Tatarinov delivered the message loud and clear that Microsoft Dynamics AX 2012 is the ERP for everyone with its commitment to "simplicity". From installation through deployment, implementation, customization, user experience, and upgrade, this release’s design bares the mark of simplicity. And with Microsoft’s theme of power, agility and simplicity around this release, doesn’t it make perfect sense that Microsoft’s ISV partners follow suit?



When considering an upgrade to Microsoft Dynamics AX 2012, it’s best practice to work with your VAR and ISVs to analyze all customizations and create a precise plan to manage your code and data upgrades. It’s a given that some customizations will still be required in AX 2012, but when it comes to accommodating EDI, you can forget about customizations – it’s that simple. Customizations to handle EDI requirements are an unnecessary hassle and without them you can avoid EDI roadblocks that can potentially disrupt your business and delay your AX 2012 upgrade project.
While evaluating the code customizations currently required to accommodate your EDI mandates, it’s important to understand the three most frequent approaches to integrating EDI with Microsoft Dynamics AX:

• Customization – the client / partner has decided to develop a one-off, non-commercial solution using a tool such as BizTalk or Gentran with custom ERP code;


• Commercial solution within Microsoft Dynamics – (i.e. built inside Dynamics via customization by an Independent Software Vendor) – EDI solution is built within inside Microsoft Dynamics AX;


• ISV built outside Microsoft Dynamics – solution is built outside of Microsoft Dynamics but augments the native functionality and integration framework of the Dynamics AX platform.

The first approach has its challenges: understanding how to construct the solution to meet the challenges of an unpredictable environment; how you’ll cope with future service packs or even upgrades beyond AX 2012; who writes and manages the customization when trading partners change their requirements; and where is all the EDI information held that is passed back and forth, even if that information is not needed for internal requirements?

The second option – using a commercial ISV solution that is fully-built inside Microsoft Dynamics – can also run into challenges: how do you and the ISV manage patches, service packs, external mandates and AX version upgrades; how do they coexist with other solutions or customizations that are vital to your business?
Neither option provides a simple approach. By using a well architected solution that tightly integrates EDI without customization – you don’t have to worry about unpredictable costs in development and updating from one Microsoft Dynamics AX version to another. But beware – many companies claim integration without customization but very few actually deliver.

An EDI solution that seamlessly integrates with Microsoft Dynamics AX 2012, offers a non-embedded design and has XML data storage within SQL will deliver integration without customization, keeping EDI simple. As a result, organizations can be EDI-ready with AX 2012 in a matter of days, not weeks or months, with the ability to implement virtually any new compliance initiative without the need for costly AX customizations.

You can also check out a 3-minute demo video of their Vantage Point EDI solution.:


Microsoft has committed to simplifying their Dynamics AX platform and, in planning your upgrade, continue the simplification process by applying business case justification to customizations, applying them only when absolutely necessary. In the case of integrated EDI, AX code customizations can be eliminated when applying the right technology – one that supports EDI Made Simple®, from Data Masons, a proud sponsor of this blog.

That's all for this post, but check back soon as more to come! Till Next Time!

Follow Me @:
    

"Visit the Dynamics AX Community Page today!"