About Layers and Difference between Layers

Layer: a layer system is used to manage elements.
The USR layer is the top layer and the SYS layer is the bottom layer, and each layer has a corresponding patch layer above it.

USR: The user layer is for user modifications, such as reports.
CUS:The customer layer is for modifications that are specific to a company.
VAR:Value Added Resellers (VAR) can make modifications or new developments to the VAR layer as specified by the customers or as a strategy of creating an industry specific solution.
ISV:When an Independent Software Vendor (ISV) creates their own solution, their modifications are saved in the ISV layer.
SLN:The solution layer is used by distributors to implement vertical partner solutions.
FPK:The FPK layer is an application object patch layer reserved by Microsoft for future patching or other updates.
GLS:When the application is modified to match country or region specific legal demands, these modifications are saved in the GLS layer.
SYS:The standard application is implemented at the lowest level, the SYS layer. The application objects in the standard application can never be deleted.

Patch Layers:Each layer in Microsoft Dynamics AX has a corresponding patch layer that can be used to incorporate updates to your application or to store conflicts when you import models into a layer.

Microsoft only:

• SYS/SYP: System Layer
• GLS/GLP: Globalization Layer
• FPK/FPP: Future Pack Layer

Partners and ISV:

• SLN/SLP: Solution Layer
• ISV/ISP: Independent Software vendor Layer
• VAR/VAP: Value Added reseller

Partners and customers:

• CUS/CUP: Customer Layer
• USR/USP: User Layer 

Differences between Layers in Axapta 4.0, 5.0 and 6.0 :

 

 

 

 

 

Error and Warning Messages

List of Errors and Warning Messages in Axapta Ax 4.0, 2009 & 2012

http://msdn.microsoft.com/en-us/library/bb530207(v=ax.10).aspx in Ax-4.0

http://msdn.microsoft.com/en-us/library/bb530207(v=ax.50).aspx  in Ax-2009

http://msdn.microsoft.com/en-us/library/bb530207.aspx  in Ax-2012

Traditional Core (Since Axapta 2.5)

Traditional Core Since Axapta 2.5

1. General Ledger, composed of ledger, sales tax, currency and fixed assets features
2. Bank Management, where cash is received and paid out
3. Customer Relationship Management (CRM), where Business Relations (customers, vendors, and leads) are contacted and maintained
4. Accounts Receivable, where orders are entered, shipped and invoiced
5. Accounts Payable, where purchase orders are issued and goods received into inventory
6. Inventory Management, where Inventory is valued and managed
7. Master Planning, where purchase and production planning takes place
8. Production, where bill of materials is defined and manufacturing is tracked
9. Product Builder, where product models are created and maintained
10. Human Resources, where employee information is kept
11. Project Accounting, where projects are created and tracked primarily from an accounting perspective
12. Basic, where data configuration is performed
13. Administration Module, where system configuration is performed

Extended core:
The following modules are part of the core of AX 2009 (AX 5.0) and available on a per-license basis in AX 4.0 :

  14. Shop Floor Control
  15.Cost Accounting
  16.Balanced Scorecards
  17.Service Management
  18.Expense Management
  19.Payroll Management
  20.Environmental Management

Hardware & Software Requirements for Microsoft dynamics Axapta 2009 or 2012

Minimum Hardware required to install and run  Service:

Software components required to install and run:

License Requirements :

Handhelds require the following minimum hardware and software in order to run  Client:

Network requirements:

Domain requirements:
The barcode systems draw all permissions and user information from Dynamics AX. Handheld units can, but do not need to be on Active Directory. To support e-mail/SMS alert notifications in  Productivity Console, an SMTP (Simple Mail Transfer Protocol) server must be present in the environment.

Before you begin install Microsoft dynamics axapta verify the required the permission have or not:

http://technet.microsoft.com/EN-US/library/aa496457.aspx

Architecture of Dynamics Axapta

Microsoft Dynamics AX has a 3 tier architecture consistng of a client, application object server(AOS) and database server. Client contains forms, reports, AOS is used to execute application objects such as classes, queries etc and the last one is the database, which is used to store data for the ERP.



 High-level overview of the system architecture of Microsoft Dynamics AX:

History of Microsoft Dynamics Axapta

http://en.wikipedia.org/wiki/Microsoft_Dynamics_AX

Some Client/Server ERP Software Applications:

Epicor
Infor
Microsoft Dynamics
Oracle
SAP