layers

hi, please explain the use of layers concept in ax 2009

in a nut shell ( and this is a very simple explanation ), each layer represents an encapsulated area where system objects exist. Each layer has an update layer with it. Each layer, typically, builds on the layer beneath it. at the core is the sys layer ( with update layer of syp ). this article gives a greater explanation of the system layers: http://development.meritsolutions.com/matters/layers-in-dynamics-ax-2009/. you can think of the sys layer as the lowest layer and usr as the highest. think of the layers as floors of a building. floor 1 is sys, floor 2 is syp, and so on up to USP

in 2009, we, as a VAR or end user, have access to var, vap, cus, cup, usr and usp. in 2012 this is different. specifically for for 2009 for stuff we can change, vap override var, cus overrides vap, cup overrides cus, and so on up the chain. this unique architecture allows different groups to do different things in each layer. for instance, if you have code in the VAR layer but you want to revert it back to the SYS layer version, (can you can’t modify VAR), you can export the system layer code and import it into the CUS layer. Do keep in mind this is a very simple explanation and there are much more detailed documents available from MS. below are some additional articles.

http://msdn.microsoft.com/en-us/library/aa851164(v=ax.50).aspx

http://www.sqldb.in/?p=152

HI sreelatha,

please go through the fllowing link.the layer structure is the basic to ax.

http://msdn.microsoft.com/en-us/library/aa851164%28v=ax.50%29.aspx