Saturday, October 20, 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:

Friday, October 19, 2012

History of Microsoft Dynamics Axapta

Some Client/Server ERP Software Applications:

Epicor
Infor
Microsoft Dynamics
Oracle
SAP

Overview of the ERP

ERP:
Enterprise Resource Planning (also known as ERP) is an effective approach that most businesses implement to enhance their productivity and performance. Before implementing this system, it is necessary that business owners and board members have an extensive look at the benefits and risks associated with the use of the ERP system.

Characterstics:
  1. An integrated system that operates in real time (or next to real time), without relying on periodic updates.
  2. A common database, which supports all applications.
  3. A consistent look and feel throughout each module.
  4. Installation of the system without elaborate application/data integration by the Information Technology (IT) department.
Advantage:
Some of the benefits from ERP are enhanced productivity and corporate financial performance, improved business forecasting as well as organized work flows.

Functional areas:
1.Financial accounting.
2.Managemnt accounting
3.Human Resource.
4.Manufacturing.
5.Project Management
6.Supply Chain Management(SCM).
7.Customer Relationship Management(CRM).
8.Data Services.
9. Access control.


Enable/Disable form control based on multiple rows select

 class PurchTableFormEventHandler {      [FormDataSourceEventHandler(formDataSourceStr(PurchTable, PurchTable), FormDataSourceEventType::Act...