Dynamics AX 2012: A common misconception about Commodity Codes

Dynamics AX 2012: A common misconception about Commodity Codes

List of new tools released for Microsoft Dynamics AX 2012

1.   Application analysis Tool (Beta): The Application Analysis tool is designed to enable developers to easily understand how the application has been constructed. The tool can analyze X++ code, create UML sequence diagrams of the data model using progressive discovery.

2.   Data Migration Framework Tool (Beta): The Data Migration Framework (Beta) is an extension to Microsoft Dynamics AX that provides a way to migrate data from external sources to source Microsoft Dynamics AX 2012.

The framework also supports exporting and importing data (for entities defined in the Data Migration Framework) from a Microsoft Dynamics AX 2012 instance to another one.

3.   Combine XPO Tool (Beta): The Combine XPO Tool (Beta) 1.0 is a command line program that combines a set of interdependent XPO files into a single XPO. For example, if a team of developers is making code changes to different aspects of an application, use this tool to merge those changed files into one file.

4.   Security Development Tool (Beta): The Security Development Tool (Beta) is intended to simplify the creation and maintenance of security artifacts such as roles, duties and privileges. It displays entry point permissions for a given role, duty or privilege and allows you to create new security artifacts on the basis of access through various entry points. The tool allows you to test newly a created\modified security role, duty or privilege from the same interface without using a different test user account. In addition, the tool also allows you to record business process flows and identify the entry points used.

5.   Code Upgrade Service Tool (Beta): The Code Upgrade Service Tool (Beta) is designed to help Microsoft Dynamics AX developers upgrade their X++ code to Microsoft Dynamics AX 2012. The service analyzes X++ code patterns and automatically fixes some patterns, provides suggestions on how to fix other patterns, categorizes upgrade tasks, and enables developers to add their own patterns to be analyzed.

6.   Security Upgrade Advisor Tool (Beta): The Security Upgrade Advisor Tool (Beta) is intended to help simplify the process of upgrading security settings from an earlier version of Microsoft Dynamics AX to Microsoft Dynamics AX 2012. It compares entry point and permissions between systems and generates a list of matching privileges that can be used a particular role. The role-to-privilege mapping is based on the user group-to-access right mapping in earlier versions of Microsoft Dynamics AX systems. The tool is designed as an aid for upgrading security settings and is not one click solution. Developers are advised to review each suggestion carefully before making any changes.

7.   Intelligent Data Management Framework Tool: The Intelligent Data Management Framework Tool is designed to help system administrators optimize the performance of Microsoft AX installations. The Intelligent Data Management Framework assesses the health of the Microsoft Dynamics AX applications, analyses current usage patterns, and helps reduce database size.

DAX – Journal posting used following tables

In DAX journal posting used following tables, ledgerJournallTable is a main table to store header information about the journal and the ledgerJournalTrans table to store line information.

After posting of journal the information is entered in the following tables.

-          If the Vendor account is used in the ledger account field then the information will be stored in vendTrans also.

-          If the Customer account is used in the ledger account field then the information will be stored in custTrans also.

-          If the bank account is used in the ledger account field then the information will be stored in bankAccountTrans also.

-          If the tax information exists on the line, it is stored in taxtrans table.

-          If there is a localization license for countries like  India, UK then the tax related information will also store in taxTrans_In, taxTrans_UK  tables

Cumulative Update 4 (CU4) Relesed

I would like to inform you that, Cumulative Update 4 (CU4) is released and this is compatible with the RTM versions and Feature Pack 1 RTM AX 2012. This cumulative update is applicable for both AX2012 RTM (6.0.947.0) & AX2012 Feature Pack 1 RTM (6.0.1108.0). It is recommended to read the release notes prior to installation of AX2012 Feature Pack Cumulative Update 4 (6.0.1108.2423).

For more information and to download CU4 accessing the link below.

Cumulative Update 4 (CU4)

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.