Axapta the basis for the MS's consolidated ERP program?

AccountingforNothing

Is there any truth to the assertion that Axapta is going to be the system that MS will be basing it's consolidated ERP product on?

I have heard this from various sources.

It is going to be an incredibly complex project if the consolidated product has to support all the native customizations to NAV, GP, SL, and AX all wrapped up in the AX system.

What about time frame 5, 7, 10 years???

Any comments out there?

ara3n

David S. is going to Convergence next week. Maybe he can get us an answer. here is the thread.

http://www.mibuso.com/forum/viewtopic.php?t=14490&highlight=


My perspective, It's just too early. Event MS doesn't know it.
The internal language will be c#, which means X++, which what axapta Business logic is written in will be gone.
It will be customized in Visual Studio, which means the MorpheX dev environment will gone from Axapta.
So what is left, the 3 tierd system. IIS will be second tier.

What I see is that the business Logic in AX is easier to transfer to C#. Since x++ was based on Java. Since the business Logic will be transfered to .NET, so will the table structures.

What will happen to the products, is that they will look closer and closer to each other.

At some point all the legacy Bussiness logic of all the 5 product will be dropped. MS is just dragging this longer because they don't have the Dynamics product, so they could just create upgrade path.
If you are making a decision on what product to purchase, don't base you decision on what Dynamics will be 5? years from now.

David_Singleton

I think Ahmed's comments are much more accurate that your comment "Axapta is going to be the system that MS will be basing it's consolidated ERP product on"

Variaously I have heard rumours that it will be based on AX, NAV, GP etc. But in the end it needs to be a product that combines the strengths of all three and SL (I have never heard that SL would be the base). I would feel that you should pick the product that suits your current needs, knowing that Microsoft are going to want to keep you as a custoemr, and make sure there is a path for you.

Andreas_Gunawan

If in the future (5, 7, 10 years from 2day) AX business logic will be changed to be C# based on .NET that is expressed by Ahmed, it sounds pretty good let alone if AX has native database rather than depends on SQL server. Most of all, they produce localised AX previously before combine AX, GL, SL and NAV into a single product named Microsoft Dynamics ERP.


Rgds,

mel_sadek

What Microsoft has stated is that the Microsoft Dynamics client will be based on the Axapta model. However, in no way shape or form have they endorsed one ERP system over the other. In fact, they have stated that the notion that all MS ERPs will be rolled up into one is not true either. The official line is that they will introduce the Microsoft Dynamics client using a "best of" method. What that means is still a mystery, but they have repeatedly denied that they will melt all ERPs into one.

Also, the compilable objects will be interpreted into C#, which are then compiled into CLR. They never stated that they will be moving to C# for development. I believe this is a good thing, because a lot of partners have invested their time and money in learning ERP languages, like C/AL or X++ for example, and so Microsoft does not want to alienate the large partner base by forcing them into learning something else.