Microsoft Axapta – Dynamics AX Customization Notes
By Andrew Karasev
Alba Spectrum Technologies
USA 1-866-528-0577, 1-630-961-5918, São Paulo 55-11-3444-4949, help@albaspectrum.com
Microsoft has several ERP, supported by it business systems subdivision – Microsoft Business Solutions: Microsoft Axapta, Microsoft Navision, Microsoft Great Plains, Microsoft Solomon, Microsoft CRM. We are talking here about MRP platforms for mid-size and corporate businesses. Looking at the Microsoft campaign at the American, European and Latin American markets, we can mention, that on such ‘emerging’ market as Brazil, Axapta is positioned as crucial application, where a lot of efforts were invested into the localization and advertisement. We believe that Axapta will play one of the leading (if not the overall leading role) in Microsoft Dynamics project. In this small article we will give you highlights on Microsoft Dynamics AX (this is the new name, give to Axapta in Microsoft Dynamics project in September 2005) customization.
There are two layers that are used by business partners:
1. BUS - When a business partner creates a generic solution, the modifications are typically saved in the BUS layer and – again – Axapta ensures that these top-level application objects are used.
2. VAR - Value Added Resellers may make their own, customer specific modifications to the business partner solution. Such modifications are typically saved in the VAR layer.
There are two layers that are used by customers:
1. CUS - The supervisor or administrator of an end user installation may wish to make modifications generic to the company. Such modifications are typically saved in the CUS (short for Customer) layer.
2. USR - Lastly end users may wish to make their very own modifications. These modifications are typically saved in the USR (short for User) layer.
· System Layer. Similar as you have it for another product in MBS family – Great Plains, where you can not do direct change to the production DYNAMICS.DIC – SYS layer is for Microsoft core Axapta developers only
· Patch Layer. This is additional layer for each of the eight layers – Patches.
· Code Isolation. When you are facing customization upgrade – Axapta gives you the opportunity to isolate questionable portion of custom code.
· Customization in action. Let’s say – you have customization in the customer screen and master record logic. Axapta kernel will first check if your specific custom piece is in the USR (the external layer) and then if not found – kernel will look inside and go level-by-level up to the core SYS layer.
· MorphX. This is Axapta IDE (Integrated Development Environment). X++ is the programming language of Axapta – it is object oriented and based on incapsulation, inheritance, classes, objects, methods, and properties. The language has Java-like syntax, and incorporates SQL data manipulation statements.
Please do not hesitate to call or email us: USA 1-866-528-0577, 1-630-961-5918 help@albaspectrum.com
Andrew Karasev is Chief Technology Officer at Alba Spectrum Technologies ( http://www.albaspectrum.com ) - Microsoft Business Solutions Great Plains, Navision, Axapta, MS CRM, Oracle Financials and IBM Lotus Domino Partner, serving corporate customers in the following industries: Aerospace & Defense, Medical & Healthcare, Distribution & Logistics, Hospitality, Banking & Finance, Wholesale & Retail, Chemicals, Oil & Gas, Placement & Recruiting, Advertising & Publishing, Textile, Pharmaceutical, Non-Profit, Beverages, Conglomerates, Apparels, Durables, Manufacturing and having locations in multiple states and internationally.
We are serving USA Nationwide: CA, IL, NY, FL, AZ, CO, TX, WI, WA, MI, MA, MO, LA, NM, MN, Europe: Germany, France, Belgium, Poland, Russia, Middle East (Egypt, Saudi Arabia, OAE, Bahrain), Asia: China, Australia, New Zealand, Oceania, South & Central America: Mexico, Peru, Brazil, Venezuela, Columbia, Ecuador, Chili, Paraguay, Uruguay, Argentina, Dominican Republic, Puerto Rico
