AX2012 Financial Dimension Service classes.

Explaining some financial dimension Classes that used to validate,Build dimensions.

Validate LedgerAccount against account structure.
FinancialDimensionService class:- ValidateLedgerAccount(LedgerAccountValidationContract)

DimensionServiceProvider: This class provides multiple methods to build DimensionStorage object based on our dimension values list with different combinations ex: buildDimensionStorageAttributesAndValues(List _values, Map _dimensionSpecifiers),buildDimensionStorageForLedgerAccount( LedgerAccountContract   _ledgerAccount,    boolean                 _createForDefaultAccount = false)

DimensionValidation: this class manages the validation for dimension combinations.ex: validateByTreeForCombination(Validates the specified combination against the constraint trees and also validates the ledger    account rules).validateByTree(dimcombinationRecid).

Cumulative Update 5 for Microsoft Dynamics AX 2012

Guys,

Missing from long time from blogging....with loads of loads of work in AX2012 implementations for multiple customers...

Here we have an update for AX2012 released  CU5

Cumulative Update 5 (CU5) contains hotfixes for Microsoft Dynamics AX 2012 that were fixed since the release of Microsoft Dynamics AX 2012. This cumulative update is applicable to both Microsoft Dynamics AX 2012 (6.0.947.0) and Microsoft Dynamics AX 2012 Feature Pack 1 (6.0.1108.0). 

 Follow the below link of Customer sourcer/ Partnersource

AX2012 CU5 release


Enjoy AX2012 folks.....

Data Partition in AX2012 R2

AX2012 R2

AX2012 R2 release extends the concept of sharing data and processes across legal entities to streamline business processes and simplify the management of 'master data'.

AX2012 R2 release can support 36 country versions in one single installation of Dynamics AX2012, international companies that are represented in many countries to increase IT and operational efficiency. You can support all divisions in one installation, and it is the precondition to share master data and efficiently manage 'master data'.

Data partitioning

Data Partitioning can provide efficiency gains, because installation and system data is still shared.And data partitioning makes it possible to divide the application data into partitions of organizations.You will be able to share application data and processes between organizations within a partition, but not across .

Please see the below figure to understand the datapartitioning.

Please see the  below installation types for AX2012R2-

Entities	A single installation	A single installation of partitioning	Several installations
Application data and processes	Shared between legal entities	Shared between legal entities within a partition. Isolated between legal entities in different partitions	Shared between legal entities in the same installation. Isolated between installations
Master Data Management	Global master data shared between legal entities	Global master data shared between legal entities within a partition	Global master data shared between legal entities within the installation. Isolated between installations.
Meta data and adjustments	Applies to all entities	Applies to all entities	Unique for each installation
IT infrastructure	Single	Single	More
Database	Single	Single	More

A data partition helps sharing the Ax install base but not the data.

There can be companies with the same name in multiple partitions.

E.g Every partition will have the default company ‘DAT’.

- Intercompany doesn’t work across partitions

Mircosoft Recommends: Implementation choice must be made carefully as the companies between two partitions cannot be merged and Intercompany features cannot be used. The only option is to use Data migration tool kit for data export import between partitions and AIF for inter company operations.

Technical:-

A new partition table is introduced with a Key and the Recid field

- There is a new field called ‘PartitionRecid’ in everytable and as the dataareaid was by default applied to all contexts(Forms
queries) the partition key will also be added.

Select * from custTable where data areaid = ‘Dat’ and Partion key = ‘Initial’

- No cross company query on partitions are allowed like the cross company query

- You can know the current partition through ‘getcurrentpartitionrecid()’ similar to ‘curext()’

- Batch servers work across partitions

- AIF works across partitions

New table property like “SaveDataPerPartition” has been introduced as like “SaveDataPerCompany”. 

So for AIF, Batch tables – Save data per partition is set to “No”,because those are shared across partitions.

so get ready folks for AX2012 R2.

Dynamics AX2012 Road Map

The Microsoft Dynamics AX Roadmap shows current product plans through calendar year 2014.

The following sections include detailed information about the current release, functionality for Microsoft Dynamics AX 2012, and the Microsoft Dynamics vision for future releases.

DECEMBER 2012 - MICROSOFT DYNAMICS AX 2012 R2

Microsoft will continue to provide new capabilities through the release of Microsoft Dynamics AX 2012 R2. The planned general availability for this release is December 2012. This release includes key themes that are important to a broad set of customers across the footprint of the solution.

Ax2012 R2 release enhanced and added SQL Server Analysis Services (SSAS) cubes that enable business users to gain insight into the organization more quickly. Simply access Key Performance Indicators and compelling charts from within a role center, drill through to more details or use powerful ad-hoc analysis tools such as Microsoft Excel or Power View, to get additional business insights.


Lifecycle Services:
o Design phase: the Microsoft Dynamics AX Code Analyzer will help analyze the performance of custom code in Microsoft Dynamics AX based on rules.
o Deploy phase: the Microsoft Dynamics AX Data Migration Framework is planned to support import, export and migration of data to/from Microsoft Dynamics AX 2012, and covers over 20 scenarios including customer, vendor, product, employee, BOM, open sales and purchase order data. The framework is utilizing Microsoft SSIS and partners & customers can extend the scenarios provided.
o Maintain phase: diagnose your Microsoft Dynamics AX environment(s) using the Microsoft Dynamics AX Diagnostic Framework by analyzing data collected from the installation’s servers based on rules. A central dashboard highlights key issues that need immediate attention. These server types are planned to be supported: SQL Server, SQL Server Reporting Services, SQL Server Analysis Services, Application Object Server, Internet Information Server, and Microsoft Dynamics AX Help Server.


CALENDAR YEAR 2013 – MICROSOFT DYNAMICS AX 2012 R2

In calendar year 2013, we will continue to release new capabilities for Microsoft Dynamics AX 2012 R2 with a specific focus on the following areas:

 H1 we plan to release new out-of-the-box BI content for the Power View technology introduced in Microsoft SQL Server 2012. This is in line with our commitment to enable our Microsoft Dynamics AX customers to fully utilize the investments Microsoft is making in leading BI technology.
 H2 of 2013 we’re planning to provide more functional enhancements for our focus industries, of which details will be released at a later stage.
 Master Data Management (MDM) – this first planned release of Master Data Management targets sharing and managing master data in specific scenarios across multiple Microsoft Dynamics AX instances. This release plans to supports scenarios for: Customer, Vendor, Product, Employee and GL Account data.



I hope you all guys are ready go into AX2012 and start swim into the depth.
Enjoy AX2012 folks......

AX2012 Build using TFS Version Control System

Create a build when AX2012 integrated with TFS .

The version control system contains .xpo files and not a model file, a build process is required
to generate the model file from the .xpo files. The following procedure provides a high-level overview
of the build process:

1. Use the CombineXPOs command-line utility to combine all .xpo files into one. This step makes
the .xpo file consumable by Microsoft Dynamics AX. Microsoft Dynamics AX requires all
referenced elements to be present in the .xpo file or to already exist in the AOT to maintain
the references during import.

2. Import the new .xpo file by using the command-line parameter -AOTIMPORTFILE=<FileName.
xpo> -MODEL=<Model Name> to Ax32.exe. This step imports the .xpo file and compiles
everything. After this step is complete, the new model is ready in the model store.

3. Export the model to a file by using the axutil command-line utility: axutil export /
model:<model name> /file:<model file name>.
As I explained in my previous post how to export and import Models
http://krishhdax.blogspot.dk/2012/10/ax2012-axutil-commands-to.html

4. Follow these steps for each layer and each model that you build.

The build process doesn’t apply to MorphX VCS.

AX2012 SSRS reports,Cubes Videos of BI

Guys when I am going through the Youtube I found some link which was very helpful for Dynamics AX BI videos where it shows how to create the reports,Cubes using SSAS in AX, It was really very useful who wants to know how to create reports in AX2012

http://www.youtube.com/dynamicsaxbi

Different layers between AX4.0 vs AX2009 vs AX2012

Layers of AX in different versions
The layer-based application object files (AOD files), Some of them have been renamed with a new prefix in different versions of Microsoft Dynamics AX.

The four layers DIS / DIP / LOS / LOP from Microsoft Dynamics AX 4.0 have been renamed to HFX / SL1 / SL2 / SL3in Microsoft Dynamics AX 2009.

The six layers DIS / DIP / LOS / LOP / BUS / BUP from Microsoft Dynamics AX 4.0 have to be renamed to FPK / FPP/ SLN / SLP / ISV / ISP in Microsoft Dynamics AX 2012.

AX 4.0 Layer AX 2009 Layer AX 2012 Layer axbup.aod axbup.aod axisp.aod axbus.aod axbus.aod axisv.aod axlop.aod axsl3.aod axslp.aod axlos.aod axsl2.aod axsln.aod axdip.aod axsl1.aod axfpp.aod axdis.aod axhfx.aod axfpk.aod
Modules in AX2012 vs AX2009 AX 2009 Modules AX 2012 Modules General Ledger General Ledger Fixed Assets (New) Bank Cash and bank management Accounts Payable Accounts Payable Procurement and sourcing (New) Accounts Receivables Accounts Receivables Sales and Marketing (New) Inventory Management Product information (New) Inventory and warehouse management Expense management Travel and expense management Production Production control Project Project management and accounting Compliance and internal control (New)

Step By Step Video Tutorial on Microsoft Dynamics AX 2012....!!!!

I think this videos are good for ItemCreation,Production,Bom.
http://blogax2012.wordpress.com/?goback=%2Egde_36052_member_133056251

AX2012 Methods on Queries and Forms Cannot Compile to CIL

Classes, tables, and enums are types in the X++ language. X++ types can be compiled to CIL. The queries and forms in the AOT are not X++ types, and they cannot be compiled to CIL. This means there are a few minor cases where calls from CIL to X++ p-code can cause an exception.

Suppose a method that is running as CIL calls a method on a query. The query method calls the ClassFactory system class of Microsoft Dynamics AX. This case causes an exception to be thrown. The problem is that the CIL session does not have access to all the system classes, yet the query method makes a call to a system class.

X++ Functions that are Not Supported in CIL

X++ language functions that run strings of dynamically written X++ code are not supported when compiled to CIL. The following X++ functions are not supported when compiled to CIL:

• evalbuf
• runbuf
  
  
  

Dynamics AX2012 Terms and Explanation about Models

Dynamics AX2012 Terms and Explanations for each term.

Term	Definition
Metadata	Information about the properties or structure of data in the Application Object Tree (AOT) that is not part of the data values. Everything in the AOT is metadata.
Application layer	A single layer of the Microsoft Dynamics AX 2012 application within a model store. Elements in higher layers override elements in lower layers.
Model	A named set of elements in a given application layer. Each layer consists of one or more models, of which one is a system-generated layer model.
Model element	A single piece of metadata. For instance, a table definition is a model element. Any one element in a layer belongs to exactly one model; that is, no element can belong to two different models nor can it belong to any model.
Model file (.axmodel)	A model that has been exported from a model store. This file is the chief vehicle of metadata deployment in Microsoft Dynamics AX 2012.
Model store file (.axmodelstore)	A complete model store that has been exported from the database. The file includes all metadata, compiled artifacts, CIL code, and security artifacts. The file is used for moving consistent metadata between environments with minimum downtime.
Model store	A collection of tables in the Microsoft Dynamics AX 2012 database that house the application metadata. The model store is analogous to the AOD file share in Microsoft Dynamics AX 2009.
Generated data	Data that is generated by Microsoft Dynamics AX during development.
Transactional data	Data that describes business transactions and the state of the business.
Configuration data	Data concerning how Microsoft Dynamics AX 2012 is configured. This data includes the following subcategories: Environment: Computer-environment–specific data. An example of environment data is the list of servers running Microsoft SQL Server® Reporting Services that Microsoft Dynamics AX 2012 is configured to use. If this data is moved, it needs to be corrected to account for new server locations. System: Parameter settings for the Application Object Server (AOS) such as which database to connect to, or for Enterprise Portal forms. Application: Number sequences, invoicing profiles, or other data that relates directly to the application.
Reference data	Data that is characterized by shared read operations and infrequent changes. Examples of reference data include flight schedules and product catalogs. Windows Server® AppFabric offers the local cache feature for storing this type of data.
Master data	The critical data of a business, such as customer, product, location, employee, and asset. Master data falls generally into four groupings: people, things, places, and concepts. It also can be further categorized. For example, within people, there are customer, employee, and salesperson categories. Within things, there are product, part, store, and asset categories. Within concepts, there are categories like contract, warrantee, and licenses. Finally, within places, there are office location and geographic division categories.
Definition group	A collection of tables that defines what will be exported by using the data export feature.
Common Intermediate Language (CIL)	The Common Intermediate Language instruction set is part of the specification of the Common Language Infrastructure from Microsoft and is more widely known as .NET. An older name for CIL was Microsoft intermediate language (MSIL).

Microsoft Dynamics AX 2012 White Papers: Code Upgrade

This series of white papers is related to Microsoft Dynamics AX 2012 code upgrade.

You can download these 

http://www.microsoft.com/download/en/details.aspx?id=20864