Dynamics AX 2012 R2 new features

 

 

 

 

 

 R2 Data partitions

 

 

 

 

Note: There are some new cubes are added but they support for new power view capabilities which is Adhoc analysis tool which is only avaiable for SQL Server 2012 version not prior versions.

 

 

How to Cancel Sales/ Purchase order

I would like to share about how to cancel Sales or Purchase order. If a Sales order or Purchase order status needs to update as “Cancelled” status then follow the below steps.

Sales/ Purchase order cancellation process

Select a Sales/Purchase order and have one sales/Purchase line(s).

Go to Sales/Purchase order à select Sales/Purchase lines àclick Update line as shown in the below screenshot à select Deliver remainder

It opens-up “Update remaining quantity” window àClick on Cancel quantity button as shown in below screenshot.

Once you perform this for a single line where no items are not delivered then automatically Sales/Purchase line status will be updated to “Cancelled” as shown in below screenshot.

Once you perform this for all lines which are not processed (means no items were delivered from all the lines) then automatically Sales/Purchase order header status will be changed to Cancelled as shown in below screenshot.

Microsoft Dynamics AX 2012 Architecture

Understanding the internal architecture of Microsoft Dynamics AX 2012 can help you make decision when planning and developing a Microsoft Dynamics AX 2012 system. Here are some pointers on DAX 2012 architecture primarily for DAX 2012 architects & solution developers.
System architecture
This diagram provides a high-level over of a Microsoft Dynamics AX 2012 system with all components installed, and describes how communications flow between the components.

Model store architecture

The model store is the part of the Microsoft Dynamics AX database where all application elements for Microsoft Dynamics AX are stored. Customizations are also stored in the model store. The model store replaces the Application Object Data (AOD) files that were used in earlier versions of Microsoft Dynamics AX.

Layer information and model information are integral parts of the model store. The Application Object Server (AOS) has access to the model store. The AOS manages layer flattening or overshadowing at runtime. That is, when you make an object modification in one layer, the modification overshadows the object on a lower layer at runtime. You could, for example, decide to change a caption on a standard form. The change is saved on your layer only, and the revised—or flattened—form replaces the standard form at runtime. The AOS also provides all the Microsoft Dynamics AX subsystems with model data, such as form rendering, report rendering, and X++ code.

Microsoft Dynamics AX contains sixteen layers. Each layer consists of one or more logical parts called models. A model is generated for each layer. For example, VAR Model is the model that the system generates for the VAR layer. The system-generated models let you install and work with the base Microsoft Dynamics AX system. When you customize the Microsoft Dynamics AX program, you can take advantage of the capabilities of models.

   

The following table describes the application object layers in Microsoft Dynamics AX 2012:

Layer	Patch Layer
USR	USP
CUS	CUP
VAR	VAP
ISV	ISP
SLN	SLP
FPK	FPP
GLS	GLP
SYS	SYP

Application Object Server (AOS) architecture

This diagram describes the functionality with the AOS windows service, and describes how communications flow within it.

Note: Clients communicate with an AOS by using remote procedure calls (RPCs), Windows Communication Foundation (WCF), or AOS services. In previous releases, other components and third-party programs could communicate with an AOS by using either .NET Business Connector or Application Integration Framework (AIF). For this release, we recommend that third-party programs use AOS services to communicate with AOS.

Client architecture

This diagram describes the functionality within the client, and describes how communications flow within it.

Client/server communication

The client communicates with various Microsoft Dynamics AX components in the following ways:

·         The client uses the remote procedure call (RPC) protocol to communicate with Application Object Server (AOS). The client never accesses the database or metadata directly. AOS sends the application objects and data to the client.

·         The data layer that the client uses is based on data sources that are specified in metadata for forms and queries. In addition, any X++ code that is required to retrieve data can use the built-in language support to query and adjust data.

·         The client uses a report Web Part to interact with the report server. By calling the web services that are exposed by the report server, the report control in the Web Part displays information that is contained in Reporting Services reports. These reports can include either transactional data from the Microsoft Dynamics AX application or OLAP cubes from Microsoft SQL Server Analysis Services. Cubes provide business analytics and key performance indicators (KPIs).

·         The client provides workflow forms, alerts, and controls so that users can participate in the business process by using the Workflow system. The Workflow system is a Microsoft Dynamics AX component that enables workflow processes by using Windows Communication Foundation classes.

·         The client provides a Help viewer, which is an application that displays context-sensitive Help topics. The Help topics are retrieved from a Help server that is located on-premises.

·         The client also provides Role Centers, or role-based home pages, for users. Role Centers provide role-specific tasks, activities, alerts, reports, and business intelligence that help users increase their productivity. To interact with the Role Centers that are provided by Enterprise Portal and hosted on Internet Information Services (IIS), the client uses a browser control.

Services and AIF architecture

 This topic describes the high-level architecture of services and Application Integration Framework (AIF).

Enterprise Portal architecture

This diagram provides a logical overview of a Microsoft Dynamics AX 2012 system with an Enterprise Portal server, and also describes the various components of the Enterprise Portal architecture.

Security architecture

This following diagram provides a high-level overview of the security architecture of Microsoft Dynamics AX 2012.

Workflow system architecture

This following diagram provides a high-level architecture of the workflow infrastructure.

Analytics architecture

The following diagram shows the Microsoft SQL Server Analysis Services cubes that are included with Microsoft Dynamics AX, and the components that are used to access them.

Reporting architecture

The following diagram illustrates the architecture of the reporting functionality in Microsoft Dynamics AX.



Innovation Is Everyone's Job

Innovation Is Everyone's Job

Six Basics of Preventing Pain in Your ERP Implementation

"Simplicity is the ultimate sophistication." -Leonardo DaVinci

Over the last decade of being involved with customers and implementation partners for ERP projects, I simply cannot overstate the above sentiment - if you keep everything simple, you make an ERP project smooth and constructive.

Let me explain further. I remember hearing multiple horror stories related to heavy solutions like SAP and Oracle including implementation failures, busted budgets, law suits, and other negativity. It is contrary that the ERP project is aimed at easing organization's way of working ends up being another pain itself.

I don't wish to paint a simplistic picture that the ERP journey is necessarily tough and complex. Things have changed with the advent of more user friendly ERP products like Microsoft Dynamics AX 2012. But even with the best tools, if you are involved in an ERP implementation you can avoid repeating the mistakes of those who walked before you by heeding these important points:

1. Did you check your expectations from the project? Are they realistic and timely? If not, get down to drawing board and write down what you want to achieve. One simple exercise would involve business shareholders discussing their pains before finding a solution. E.g. Is high inventory cost your problem or lack of supply chain visibility bothering your business? Do you get your payments on time and your profitability ratios remains green? Information Technology is definitely an enabler and the journey to implement business solution should start from the business issues.
2. Once you know your problems, you can begin your journey for solutions. The next step is finding the right solution and the partner. Did your solution partner devote time to exploring your problem further before jumping to conclusions? An have they done similar projects? It's a clear analogy to when you fall sick - you go to a specialist and highlight your pain areas. Would you like to go to a doctor who wouldn't have time to explore your problem, has never treated your illness before, and jumps to prescribing the cure?
3. Once you select your solution and the partner, please ensure that their team remains in place. You cannot invest time and effort sharing your business problems with one consultant and expect a replacement to have the same understanding. Ensure continuity of the team involved right from start till the end of the project.
4. Break the project into more and smaller milestones. Create 10 milestones instead of 4 or 5. It will create better control and accountability of project stakeholders. Remember the time management principle of taking realistic and smaller targets and achieving them. It creates positive energy in the implementation teams as the smaller targets are easier to achieve. Plus, celebrate your each milestone to compound this positive energy.
5. A carrot and stick approach works well. Keep the stick around to push your implementation teams - internal and external team members - to achieve the milestones. Dangle lot of carrots too, you need to create a motivated and committed energy around the project. Did you provide any bonus to project team for putting in extra hours?
6. Customisations - the most evident hurdle to any ERP success. Did you weigh the risks for any customizations to the product? I think this is one area where customers should definitely meet other existing customers of the same product. How has their experience been with customizing the product? Did you evaluate all the options to the customized approach and their benefits?

Beyond these points, the customer users need to love the solution. It is going to be part of their daily routine of activities. I favor the user centric design of ERP products like AX 2012, since historically most ERPs fail in ‘connecting with the users'. Microsoft's entry into business applications market has changed the rules of the game in the last decade. It has brought more customers into the ERP fold and has introduced more customers to user friendly ERPs.

Simplicity should rule - both in the product and the implementation process!!

by Raman Dhooria, IT Consultant, Microsoft India

http://msdynamicsworld.com/story/six-basics-preventing-pain-your-erp-implementation

Tips for becoming successful Entrepreneurs

http://www.entrepreneur-inspiration.com/2011/02/09/tips-for-becoming-successful-entrepreneurs/

Watch Steve Jobs brainstorm with the NeXT team in this fascinating video

Watch Steve Jobs brainstorm with the NeXT team in this fascinating video