mardi 10 avril 2012

Microsoft Dynamics AX 2009 Architecture

With Microsoft Dynamics AX 2009, the full range of functionality is delivered in
the first installation. Unused functionality remains hidden until needed and is
enabled by entering the appropriate license code into the system. Companies buy
appropriate licenses and only pay for modules they use. With Microsoft
Dynamics AX 2009, there is no need for integrating and managing multiple
systems.
Sophisticated customizations can be made without special IT or programming
knowledge. Frequently, this process can cost companies significant time and
money because changes must be made to multiple forms and reports. But with
the Microsoft Dynamics AX 2009 configuration system, the unused features are
hidden, not removed, and the process is simple.


• The standard Microsoft Dynamics AX 2009 application components
are stored in the core layer called the system layer which is
controlled and maintained by Microsoft Dynamics.
• Country-specific, industry-specific, and customer-specific
modifications are created and stored in the layers stacked on top of
the core layer.
• The outermost layer is where the individual end user can store
personal modifications, for example a report layout.
• Although the top layers can be changed, the standard Microsoft
Dynamics AX functionality remains the same and you can return to
the original version without running a new installation.

There are ten separate layers in the Microsoft Dynamics AX 2009 application
hierarchy. The first four are used by Microsoft Dynamics AX developers:
Layer Description
SYS The standard application is implemented at the lowest
level, the SYS layer. This layer includes country/region
specific features developed for the United States,
Western European and African countries..
GLS The GLS layer includes features developed for all
countries that have not been implemented in the SYS
layer.
HFX HFX is the application layer used for on-demand
hotfixes. A hotfix is a single code package composed of
one or more files used to address a problem in the
product.
SL1, SL2, or SL3 A layer where the distributor can implement vertical
partner solutions. SL is an abbreviation for SoLution.

There are two layers used by Microsoft Dynamics AX business partners:
Layer Description
BUS When a business partner (BUS) creates a generic solution, the
modifications are saved in the BUS layer.
VAR Value Added Resellers (VAR) can make customer-specific
modifications to the business partner solution. These are saved in
the VAR layer.

There are two layers used by Microsoft Dynamics AX customers:
Layer Description
CUS The supervisor or administrator of an end user installation may
want to make modifications generic to the company. Such
modifications are typically saved in the Customer (CUS) layer.
USR End users may want to make their own modifications. These
modifications are typically saved in the User (USR) layer.



• When partners or users change the application, the modified objects
are stored in different files. Therefore, the standard version of
Microsoft Dynamics AX 2009 does not change, but the objects will
be copied to a higher level in the layer structure from which the
modifications will be executed.
• Partners and the customers always have the chance of comparing or
even reverting to the standard version before the modification.



o Single database architecture is used for all companies in the
organization.
o A highly integrated design between functional areas such as
resource planning, sales, and manufacturing.
o Dimension-based system for manufacturing and financial
modules.
o Advanced features such as Forecasting and Master Planning.
o Multicurrency and Multilanguage capabilities.
o Intercompany financial and trade & logistics transactions.
o Consolidation of subsidiary with parent company.



Microsoft Dynamics AX MorphX is an integrated development
environment (IDE) for developing in Microsoft Dynamics AX.
o The .NET Business Connector provides access to the complete
Microsoft Dynamics AX application interface enabling easy
integration of third-party and Web applications.
o The Application Object Tree (AOT) provides a uniform and
compact programming framework and viewing repository.
o Drag-and-Drop functionality is supported for many
programming tasks.
o Projects help organize and track customized applications in
Microsoft Dynamics AX.


Users are also presented with several information panels they can view such as:
• Corporate news relevant to their role
• Weather information
• Traffic reports
• Stock market reports
• Microsoft Outlook® calendar and task list
• Live reports from other modules
All information is organized according to personal preferences. Users can do the
following:
• Move and hide elements
• Select the layout, colors and text preferences
• Select any one of many languages

Aucun commentaire:

Enregistrer un commentaire