Dynamics AX for Retail Architecture
Dynamics AX for Retail Architectural Guidance Written by: Jay Manley Dynamics Principal Technologist Microsoft Corporation
Vic Miles Retail Technology Strategist Strategist Microsoft Corporation
Published: June 1, 2011 Version 1.0
© 2011 Microsoft Corporation. All rights reserved. reserved. This whitepaper is for informational purposes only and is provided “as-is.” MICROSOFT MAKES NO WARRANTIES, WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples depicted herein are provided for for illustration purposes only and are fictitious. No real association or connection is intended or should be inferred. This whitepaper does not provide you with any legal rights to any intellectual property in and to any Microsoft product. You may copy and use this document for your internal, reference purposes.
Table of Contents 1 Introduction .........................................................................................................................................................4 1.1 Purpose ..........................................................................................................................................................5 1.2 Audience ........................................................................................................................................................5 1.3 Retail Stack for a Connected System .....................................................................................................6 1.3.1 Why is this lack of connected retail systems a concern? ..................................................................6 1.3.2 Retail ERP Suites Differ from Traditional ERP Systems ..................................................................6 1.3.3 What is the business value of the Microsoft connected retail system? ..........................................6 1.3.4 What functionality does a good retail system support? .....................................................................7 2 Dynamics AX for Retail Overview ..................................................................................................................8 2.1 Centralized Store Management ................................................................................................................8 2.2 Flexible POS ..................................................................................................................................................8 2.3 Powerful Merchandising ............................................................................................................................9 2.4 Global Reach and Scalability ...................................................................................................................9 2.5 Multichannel Enablement ..........................................................................................................................9 2.6 Hardware and Payment Compliance ................................................................................................... 10 2.7 Centralized Store Management ............................................................................................................. 10 3 Components of Dynamics AX for Retail ................................................................................................... 11 3.1 Dynamics AX for Retail – Retail – Back Back Office ................................................................................................. 12 3.2 Dynamics AX for Retail – Retail – Front Front Office ................................................................................................ 13 3.2.1 Retail Headquarters ............................................................................................................................. 14 3.2.2 Retail Scheduler ................................................................................................................................... 17 3.2.3 Retail Store Inventory .......................................................................................................................... 17 ................ ................................... ................................... ................................... .................... 18 4 Dynamics AX for Retail Deployment Hardware .................................
5 Dynamics AX Back-Office Architecture Guidance ................................................................................. 20 5.1 Development Environment Features ................................................................................................... 20 .................. ................................... ................................... ................................... ...................... .... 20 5.2 Elements of Dynamics AX Development ................................... 5.3 Dynamics AX Layered Architecture .................................................................................................... 23 5.4 Tools for Customization ......................................................................................................................... 25 6 Dynamics AX Front-Office Architecture Guidance ................................................................................ 26 7 Summary ........................................................................................................................................................... 31 A Appendix ........................................................................................................................................................... 32 .................. .................................. ................................... ......................... ....... 32 A.1 OS, CPU, Memory and Hard-Disk Requirements ................................... ................ ................................... ................................... .................................. ................................... ............................ .......... 34 A.1 Links to External Resources .................................
1 Introduction Microsoft® recognizes that the solutions that underpin modern retail businesses require integration throughout the entire operation, with intent intent to deliver value to the target consumer. This white paper is a continuation in a series of guidance to retail architects and service providers. The core guidance on the architectural considerations within retail are in a document titled: Microsoft Architecture Guidance for the Enterprise Retail Store (appendix A.2). This document will cover the Microsoft software offering for the retail industry. Microsoft Dynamics® AX for Retail builds on the foundation of a solid enterprise resource planning (ERP) system and adds retail-specific capabilities to integrate business processes across locations with a single solution. The important distinction between the Microsoft core guidance and the Microsoft Dynamics AX guidance is the comprehensive “solutions” nature of Dynamics Dynamics AX for Retail that can simplify implementation for retailers. When a retail solution is considered, especially one t hat implements both back-office headquarters functionality as well as front-office POS functionality, one should consider the entire technical stack that builds out a complete, connected, connected, end-to-end solution. What do we mean by that? that? The solution needs to have components that by by nature are integrated tightly to each other. Today, many retail systems don’t have a long -term vision, and true Retail suites haven’t generally been available. Microsoft bridges
all those gaps with our Dynamics AX for Retail solution capping the stack of platform products and business solution products.
1.1 Purpose The purpose of this white paper is to provide an architectural overview of Dynamics AX for Retail. We will discuss the relevant points of both Dynamics AX for Retail Front Office (known more commonly as POS System), Dynamics AX for Retail B ack Office (known more commonly as ERP or ERP w ith Headquarters functionality), and the link between both Front and Back Office (commonly known as Dataflows). This white paper does not cover on the entire architecture of the Dynamics AX ERP system, as that is well-documented by other means. Rather, it highlights those portions that make up the Dynamics AX for Retail functionality. Only a brief discussion of the ERP system is covered, as it is applicable applicable in the needs of developing an overall integrated system. The main purpose of the document is to describe a set of functional points that our product provides as a basis for the unique intellectual property of our partners as well as how it provides the flexibility for innovative solutions to establish competitive differences in the market.
1.2 Audience The primary audience for this document includes each of organizations that collaborate to execute an effective ERP implementation. Microsoft Dynamics AX for Retail is generally delivered by an implementation partner who will build relationships with peripheral application owners (retail IT) as well as Microsoft certified ISVs who may build custom solutions. The audience for this guide may also include the following positions:
Technical decision makers who determine the appropriate technology solutions for their businesses. IT infrastructure architects who design systems to meet the business needs of their organizations. IT application architects who specify the software and hardware used in POS-store environments and back-office implementations. IT operations managers who manage the services that are provided to the stores. Consultants and partners who recommend or implement distributed-architecture best practices to achieve a successful, dynamic infrastructure for their customers.
In addition, original equipment manufacturers (OEMs), value-added resellers (VARs), and independent software vendors (ISVs) may find this guide useful in helping to deliver packaged hardware or software solutions to retail customers.
1.3 Retail Stack for a Connected System 1.3.1 Why is this lack of connected retail systems a concern?
Architectural inflexibility – Existing merchandising systems were never designed to enable critical consumer-centric initiatives, such as integrated planning, local market assortments, global-inventory visibility, price and promotion optimization, and r eal-time demand sensing.
Lack of an enterprise application strategy – Most retailers developed or purchased applications to solve individual business problems as they arose.
High legacy-software-maintenance costs – Functional gaps and poor integration in legacy applications force retailers to spend more.
Limited returns from new software investments – 75% of companies have not re alized full benefits from these systems because of cumbersome integration between outdated merchandise-management applications.
Increased risk to the business – Reliance on a complex mix of old and custom-built applications exposes retailers to an unacceptable level of risk.
Legacy enterprise applications don’t support modern retail needs .
1.3.2 Retail ERP Suites Differ from Traditional ERP Systems
Offers retail-centric components.
Supports store systems.
Provides segment-specific expandability.
Provides support for advanced functionality.
Provides configuration and scalability.
Provides support for a phased implementation strategy.
Provides workflow automation and enterprise-process management.
Provides the technology and application integration foundation.
1.3.3 What is the business value of the Microsoft connected retail system? Microsoft is one of the only companies that c an bring to the market place a completely integrated and interoperable solution built to provide single version visibility, manageability and usability of a retailer ’s data. The Microsoft stack starts at the operating-system level, with Windows® and Windows Server® products, then we move to the SQL Server™ database as well as Commerce Server where needed. We follow the stack with Microsoft Office, SharePoint ® Server and PerformancePoint® Server, and then cap the stack with Microsoft Dynamics AX and Dynamics AX for Retail.
Microsoft Dynamics AX for Retail can connect cr itical point-of-sale (POS) and headquarters processes with enterprise resource planning (ERP) and financials right “out-of-the box” for a comprehensive solution that delivers value in every area of the organization. You can maximize your current IT investments for fast return on investment (ROI) bec ause Microsoft Dynamics AX for Retail is built on Microsoft products and tec hnology. You can also innovate by adding functionality at a faster pace and more cost-effectively, enabling you to scale your operations, add locations, and change processes as new retail opportunities arise.
1.3.4 What functionality does a good retail system support?
2 Dynamics AX for Retail Overview Microsoft Dynamics AX for Retail is a full-featured back-office ERP system with store-headquarters functionality and front-office POS functionality. The following documents some of the primary features of our fully-integrated solution.
2.1 Centralized Store Management
Manage POS terminals centrally, including visual profiles, functional profiles, user interface layouts, and employee permissions.
Consistent data model and business rules between store and ERP processes provide accurate, timely, and consistent data.
Powerful data replication helps ensure critical updates across the organization: configurable, flexible inventory and financial updates, sales-order payments, gift-card usage, and issuance and usage of loyalty points.
2.2 Flexible POS
Purpose-built POS components are integrated into Microsoft Dynamics AX for Retail.
Continue to capture transactions and serve customers even when store connectivity to headquarters is down with fault-tolerant, resilient POS.
Optimize the user interface for store roles with graphical “drag -and-drop” designer for improved
productivity and customer service.
Powerful POS capabilities include: On account, global voucher, returns management, Infocodes, returns/voids/markdowns, and inventory receipt/lookup/counts.
2.3 Powerful Merchandising
Optimize for profitability with pricing flex ibility, including: flexible discounts, group/item/customer discounts, mix and match, and “buy-one-get-one” scenarios.
Optimize purchasing and replenishment: Purchase quantities based on size, color, and style; and use replenishment processes, including cross-docking, to suggest item distribution between stores with immediate updates to transfer journals.
Flexible four-level item hierarchy drives valuable reporting insight to improve assortment planning and product mix, including special-item groups, location-specific pricing, customer-specific pricing, and promotions.
2.4 Global Reach and Scalability
Adapt quickly to changing business requirements with POS add-ins and extensible headquarters software that can be tailored to meet specific retail needs.
Scale your solution as your business grows and add stores and distribution centers t o help you compete—locally and internationally. Easily add users and sites with three-tier architecture and integration with other Microsoft technology such as SQL Se rver 2008.
Easily operate your business across geographies and locations with flexible deployment options and built-in support for 38 countries in 40 language versions.
Capitalize on new opportunities with a Web-services framework t hat makes it faster, easier, and more affordable to build expanded, profitable partner relationships.
2.5 Multichannel Enablement
Reduce TCO with “out-of-the-box” support for critical-payment integration, including debit and credit through Payment Services for Microsoft Dynamics ERP.
Enhance the customer experience by managing payments across c hannels—including mixing and matching payment providers by channel; buying online and returning to a physical store; and leveraging support for shopping carts.
Create and publish catalogs and manage offers across multiple channels.
2.6 Hardware and Payment Compliance
Support retail-industry standards, including OPOS, which enables maximum flexibility in POS hardware and peripherals choice.
Manage PCI data-security standards compliance and ongoing support.
2.7 Centralized Store Management
Increase the value of Microsoft Dynamics AX throughout the life of the solution with the Business Ready Enhancement Plan, a global maintenance plan with benefits that include product upgrades, predictable pricing, online support through CustomerSource and Knowledge Base, and unlimited elearning.
Extend the value of your solution through integration with other Microsoft business applications and technologies, including: Microsoft Office Project Server, Windows Workflow Foundation, and Microsoft unified-communications tools.
Enhance security, reliability, and scalability though integration with SQL Server 2008. For example, Microsoft Dynamics AX 2009 running on SQL Server 2008 and Windows Server 2008 can compress the database size by 40 to 60 percent, which can lead to lower hardware and data-maintenance costs.
Learn more about Microsoft Dynamics AX for Retail at:
www.microsoft.com/dynamics/en/us/products/ax-retail.aspx
3 Components of Dynamics AX for Retail Microsoft Dynamics AX for Retail is made up of several sub-systems.
A back-office ERP system
A front-office POS system.
A connection between the two systems sy stems for both routine data updates as well as one -time transactional information.
3.1 Dynamics AX for Retail – Back Office Microsoft Dynamics AX is a comprehensive enterprise resource planning (ERP) solution for midsize and larger organizations that empowers people to work effectively, manage change, and compete globally. It makes it easy to operate across locations and countries by standardizing processes, providing visibility across your organization, and helping to simplify compliance. With Microsoft Dynamics AX, you can be confident your business management solution is —and will continue to be—relevant to the needs of your people and the demands of your industry and business. Microsoft Dynamics AX can provide your organization with business value in a single ERP solution that extends into every area of o f your operations to help you: Improve productivity - Familiar, easy-to-use tools and access to Role Tailored information and tasks
enable people to work quickly and make smart, proactive decisions. Manage change and growth - Scale your business systems and adapt processes easily with a single ERP
solution that can support your strategic initiatives and help manage c hange in the marketplace, such as new product launches and mergers and acquisitions. Compete globally - Manage the complexities of a global organization with one centralized ERP solution
that helps you standardize processes and gain visibility across your organization while staying on top of changes in local regulations. Simplify compliance - Stay ahead of re gulatory compliance and reduce risk and liability associated with
corporate governance and customer initiatives. Microsoft Dynamics AX provides unique and powerful features within functional areas and the development environment. The features of Microsoft Dynamics AX are summarized below:
Single-database architecture is used for all companies in the or ganization.
A highly-integrated design between functional areas such as resource planning, sales, and manufacturing.
Dimension-based system for manufacturing and financial modules.
Advanced features such as Forecasting and Master P lanning are available.
Multicurrency and Multilanguage capabilities.
Using Microsoft Dynamics AX 2009: Refer to this link for installation, upgrade, and administration
documentation. http://go.microsoft.com/fwlink/?LinkID=146837
3.2 Dynamics AX for Retail – Front Office Microsoft Dynamics AX for Retail is an integrated retail solution designed for Microsoft Dynamics AX. Microsoft Dynamics AX for Retail provides midmarket and large retailers a complete head-office and point-of-sale solution. It can help retailers achieve higher financial returns, provide better service, manage operations for growth, and streamline efficiencies. This solution controls the fundamental aspects of a retail business from the head office to the stores, and links the point-of-sale (POS) registers and Microsoft Dynamics AX. Microsoft Dynamics AX for Retail includes the following subsystems:
Microsoft Dynamics AX for Retail Headquarters: Retail Headquarters is a module for Microsoft Dynamics AX that retailers use to manage a chain c hain of stores as one enterprise. It is designed to run at the head o ffice, centrally managing daily operations and tracking sales information for every store in t he chain. Retail Headquarters includes Retail Scheduler (a feature that orchestrates orchestr ates communication between the head office and the store s) and Retail Inventory (a feature for managing movement o f inventory). Retail Headquarters can be used with any point-of-sale system that is able to receive and transmit necessary data from Microsoft Dynamics AX.
Microsoft Dynamics AX for Retail POS: Developed especially for Microsoft Dynamics AX, Retail POS is an optional feature that brings speed, power, flexibility, dependability, and ease of use to the point-of-sale. Retail POS has a dynamic interface that can be fully customized for your type of business and store procedures. In addition, Retail POS can work offline, ensuring that your stores remain fully operational during network interruptions. All data is automatically updated when the connection is restored.
Microsoft Dynamics AX for Retail Store Connect: Retail Store Connect is the integr ated service that periodically sends data between t he head office, stores, and individual Retail POS terminals. Communications via Retail Store Connect are managed through distribution locations and Retail Scheduler in Retail Headquarters.
Microsoft Dynamics AX for Retail Transaction Service: Together with Retail Store Connect and Retail Scheduler, Retail Transaction Service completes the communications mechanism of Microsoft Dynamics AX for Retail by providing real-time, synchronous communication. It can be used to authenticate cashier logon cre dentials, send loyalty requests, and exchange “up-to-the-minute” physical inventory information between the head office and the stores, and more.
3.2.1 Retail Headquarters When you install Microsoft Dynamics AX for Retail Headquarters, the following modules are added to Microsoft Dynamics AX:
Retail Headquarters – Use this module to configure and manage stores, terminals, retail items, and the other records that make up the Microsoft Dynamics AX for Retail implementation. Also use this module to generate reports, perform inquiries, and complete other daily business processes.
Retail Scheduler – Use this module to manage the distribution of data from the head office to stores and terminals. You can also use this module to create distribution locations, set up up table distribution, and schedule the jobs and sub-jobs that send information to stores.
Retail Store Inventory – Use this module to send store inventory documents to stores to use for receiving inventory for a purchase order, picking or receiving inventory for a transfer o rder, or counting stock for a count order.
Retail Headquarters forms and fields
In addition to the forms included in the t hree modules of Microsoft Dynamics AX for Retail Headquarters, installing Microsoft Dynamics AX for Retail Headquarters adds fields to certain forms t hat already exist in core Microsoft Dynamics AX. For example, several new fields are added to the Item and Employee forms. Retail Headquarters Headquarters is the primary module of Microsoft Dynamics AX for R etail Headquarters. It is use
to enter the information and settings that are used in the” day-to-day” operations of your retail organization. It is also the area w here you can view “up-to-the-minute” information about your inventory, revenues, and more. Microsoft Dynamics AX for Retail POS is the point-of-sale program for Microsoft Dynamics AX for Retail. It can be used to perform sales, operate the cash drawer, scan bar codes, and print customer receipts. Retail POS adds up the sales total, calculates the tax, calculates the change c hange back from the amount paid, and adjusts the store's inventory levels to r eflect the amount of inventory sold. Primary transactions include activities such as sales, refunds, suspend, advance, loyalty, credit voucher issue, gift-card issue, bar-code scanning, receiving payment, and receipt printing. Retail POS includes the ability to track customer orders, proce ss credit and debit cards, connect to o ther systems in a network, and check inventory. Each point-of-sale register is uniquely identified by a re gister number. Retail POS, built on the Microsoft .NET Framework, uses a unique and easy-to-use graphical user interface (GUI) that can be set up according to various business needs, such as food, fashion, grocery, and so on.
Staff
The Retail Headquarters staff setup describes how to create staff members for stores and assign privileges for performing operations in Retail POS. Retail Headquarters staff information is linked to employee master records in Microsoft Dynamics AX. The program keeps record of staff details such as employee number, Retail POS logon password, address, and contact numbers, and so on. Each staff member is assigned Retail POS privileges, such as voiding transactions, performing tender declaration, overriding price, and maximum discount to give. A staff member can be assigned only to o ne store. If you have set up Enterprise Enter prise Portal for Microsoft Dynamics AX, you must set up User Profiles for the employees who will access the Enterprise Port al. These profiles define each user's role and specify the store information that the user will have access to. Infocodes
Infocodes are a powerful tool that c an be used to capture data at the point-of-sale. They capture additional information when a cashier performs various actions at point-of-sale such as an item sale, item return, or customer selection. Retail POS prompts the cashier for input that can be selected from a list or entered as a code, a numeric, a date, or as text. Infocodes can be assigned to predefined store actions, retail items, tender types, customers, or specific point-of-sale activities.
Infocodes make it possible for a business to get additional information needed at the transaction time, such as a flight number, reasons for returns, and so on.
Infocodes can be set up for specific item prices that prompt the register cashier to select one of a number of prices.
Infocodes can have a sub-code linked to t hem that prompts the register cashier for input while performing a specific activity.
Items can be sold through an I nfocode as a normal sale, discounted sale, or fr ee item.
Inquiries and reports
Retail Headquarters provides extensive reporting capabilities in addition to the standard Microsoft Dynamics AX reports. Retail Headquarters provides a number of reporting options, both in the form of online analysis, also called inquiries, or in the form of reports. Both reports and online inquiries in Retail Headquarters support specific features such as filtering and sorting. This allows for the quick filtering of the data on which the reports should be based. Custom date filtering is also supported. Transaction and statistics-level reporting can also be generate d on a time basis, which enables the analysis of the sales flow throughout the day. In addition to this capability, sales by item and store can be displayed in graphical format.
Retail Headquarters adds to your ability to extr act accurate sales information by providing numerous statistical windows and reports that build on statistic tables, item-value entries, and t ransactions from the registers. This ability can help to de termine which items or variants are selling best and which stores, registers, and staff are performing best. All standard sales reports in Microsoft Dynamics AX can be used to analyze sales information. Items in unposted statements are not included. Processes
Retail Headquarters supports retail-specific processes such as the following:
Statement calculation and posting
Label printing
Vendor item import
Replenishment (cross docking or buyer's push)
Contract concessions
These periodic activities are carried out w hen required. Some of these periodic activities are: post physical Inventory, financial- ledger entries, Inventory journals, and purchase or ders. Replenishment
Optimizing inventory levels at the distribution center is necessary for removing excess costs from the customer-driven value chain. To invest inventory dollars more effectively, retailers must be able to blend both the art and science of purchasing and inventory management. Effective location/warehouse replenishment helps retailers, manufacturers, and wholesaler-distributors to increase revenue and ensure high levels of customer satisfaction by sustaining this balance. By providing accurate visibility into the location or warehouse, replenishment helps buyers to create accurate demand forecasts and order project ions, as well as table order patterns. Replenishment assists the purchasing department in creating purchase orders and also to assist the warehouse with making suggestions about what items must be transferred to the stores. Replenishment in Microsoft Dynamics AX for Retail offers the option to replenish warehouses or stores using the purchase order or transfer t ransfer order. The replenishment processes run at the head office. It is possible to manually allocate quantities to be distributed to the stores. Re tail Headquarters provides the three distribution methods listed below:
Location weight
Replenishment rules
Fixed quantity to all
Location replenishment is also used when items are distributed automatically to stores. If the item that needs to be distributed has variants, the combination of the location replenishment curve and the size or color curve determines the quantity that is allocated to each location or store.
3.2.2 Retail Scheduler Retail Scheduler manages the distribution of data through Microsoft Dynamics AX for Retail Store
Connect, from the head-office database to the appropriate store and terminal databases. It also manages updates of the head-office database with sales and inventory data from the stores. This guide discusses the day-to-day operations that you might perform in Retail Scheduler, including adding a new store or terminal t erminal to the data-distribution structure, running jobs, and viewing the status of jobs and data packets. Data distribution is the system of settings and records that control how data in the head-office database is sent to the store and terminal databases. Data distribution is store-specific, meaning you can specify that certain records are sent only to the locations where they are useful. Data distribution is also tablespecific, meaning you can customize the way that changes to certain tables are distributed. Jobs are the mechanism for distributing data to your locations. Each job is made up of one or m ore subjobs. The include list or exclude list for a job filters the locations that data is sent to. There are four types of jobs which are listed below:
Action (A) jobs – “A” jobs send data that has changed (tr acked as actions) from the head office to stores. The locations that receive the jobs are determined by the distribution settings for the changed records (or their parent records).
Custom (C) jobs – “C” jobs run a specified custom class. Two “C” jobs are included in Retail Scheduler by default, C-1000 (Send email receipts) and C-1020 (Convert Preactions).
Normal (N) jobs – “N” jobs are not dependent on ac tions. They delete all existing data in the destination tables and then insert updated data. “N” jobs send data from the head office to stores.
Pull (P) jobs – “P” jobs pull data —such as sales and inventory data — from the distribution location specified in the job and insert it into the head-office database. You need one “P” job for each terminal or store database.
3.2.3 Retail Store Inventory With Retail Store Inventory, you can manage the store- inventory documents that provide an interface between stores and the purchasing, tr ansfer, and counting features in Microsoft Dynamics AX. A store inventory document is a form that is associated with a purchase order, transfer order, or counting journal. The document is typically created at the head office, used at the store to enter inventory data, and then reviewed and posted at the head office.
4 Dynamics AX for Retail Deployment Deplo yment Hardware
A typical deployment involves the types of computers listed in the following table. Deployment location Head office
Types of Computers
Database server Microsoft Dynamics AX Application Object Server (AOS) Communications server Microsoft Dynamics AX client computers
Each store
Database server (if used) Communications server Register computers
Depending on the needs of your organization, a particular computer can be used for more than one of the purposes listed above. It is recommended that you perform load balancing across multiple computers wherever possible.
Store Database Deployments Each store must have its’ own database, and a single database can be used for multiple registers. However, you will probably want to set up one database on each register, depending on store traffic and likely database growth.
Each of the deployment topologies shown has advantages and drawbacks. For example, if the store's network is down, the POS terminals with a database at each registe r can continue to process transactions because each register has its own database. This configuration can affect performance, though, because updates from Retail Headquarters must be sent to each register rather than just to the store. Multiple registers can use a single database, but no offline database functionality is available. Also, a central database can grow too quickly for the capacity of SQL Server 2008 Express, in which case either SQL Server 2008 Standard or SQL Server 2008 Enterprise is required. You must weigh the advantages and disadvantages in light of your particular deployment; no one solution is right for every retail organization. One of the challenges retailers face is the installation of hardware peripherals. It is important to find peripherals that are suitable and to gain familiarity with them.
Supported peripheral devices
Microsoft Dynamics AX for Retail supports the following types of OLE for Retail (OPOS) devices for registers: Cash drawers
Receipt printers
Line or pole displays
Dual displays (second monitor facing customer)
Magnetic stripe readers (MSRs)
Bar code scanners
Scales Keylocks (keyboard locks for manager override keys) Keyboards PIN pads
Important OPOS Common Control Objects, version 1.12, are required. After using an installation utility provided by a hardware manufacturer, confirm that the Common Control Objects have not been overwritten by an earlier version. To help avoid performance issues, verify that you are using the correct service objects for the hardware devices that you are using.
Certain service objects require re quire the installation of Microsoft Visual C++® 2008 Redistributable Package.
5 Dynamics AX BackBack-Office Architecture Guidance This document is in no way meant to re present the entirety of what w hat is involved when working with the Dynamics AX architecture. Instead we will cover it topically in relation to Dynamics AX for Retail. This chapter will cover some of the foundational components of the Back-Office Architecture. It is intended to allow you to understand the breadth o f the solution and the flexibility to meet the needs of various retail implementations. To find out more about Dynamics AX development development and architecture, please visit the following links. http://msdn.microsoft.com/en-us/library/cc602654.aspx http://msdn.microsoft.com/en-us/library/aa654810(AX.10).aspx http://msdn.microsoft.com/en-us/dynamics/ax/cc546579.aspx
5.1 Development Environment Features
Microsoft Dynamics AX® MorphX® is an integrated development environment (IDE) for developing code in Microsoft Dynamics AX.
The .NET Business Connector provides access to the complete Microsoft Dynamics AX application interface allowing for easy integration of third-party and We b applications.
The Application Object Tree (AOT) provides a uniform and compact-programming framework and viewing repository.
Drag-and-Drop functionality is supported for many programming tasks.
Projects help organize and track customized applications in Microsoft Dynamics AX.
5.2 Elements of Dynamics AX AX Development The Microsoft Dynamics AX Object Server (AOS) is the second-tier application server in the Microsoft Dynamics AX three-tier architecture. The 3-tier environment is divided as follows:
First Tier – Intelligent Client
Second Tier – AOS
Third Tier – Database Server
The AOS executes Microsoft Dynamics AX business logic that provides for scalability, flexibility, and better performance. In a 3-tier solution, the database runs on a server as the third tier and the AOS handles the business logic in the second tier. The t hin client is the first tier and handles the user
interface and necessary program logic. The figure below illustrates the interaction between the thr ee tiers.
The AOS architecture is highly scalable. As a business grows and the number of Microsoft Dynamics AX users increase, you can expand the capacity of Microsoft Dynamics AX by adding an additional AOS to the second tier. The additional server provides load balancing and introduces failover safety into the environment.
The Application Object Tree (AOT) is a tr ee view of all the application objects within Microsoft Dynamics AX. The AOT contains everything you need to c ustomize the look and functionality of a Microsoft Dynamics AX application. Use the drag-and-drop features of the AOT to create and modify application objects without writing any code.
IntelliMorph® is the technology that controls the user interface in Microsoft Dynamics AX. The user interface is how the functionality of the application is prese nted or displayed to the user. The same functionality can be displayed on multiple platforms or devices that use the same application code. For example, through the Web or through Mobile devices, IntelliMorph controls the layout of the user interface and makes it easier to modify forms, reports, and menus.
The MorphX Development Suite is the integr ated development environment (IDE) in Microsoft Dynamics AX used to develop and customize both the Windows interface and the Web interface. An IDE integrates development functions such as designing, editing, compiling, and debugging within a common environment. With MorphX, common operations such as building or modifying forms, menus, and reports are done using drag-and-drop techniques with little or no coding.
A core concept of MorphX is inheritance. Think of inheritance as a child object receiving propertie s from a parent object. Characteristics of inheritance include the following:
What is defined at a higher level in the system is automatically inherited by lower levels.
Microsoft Dynamics AX is flexible and modifiable on many levels because of this hierarchical structure.
You can modify a single parameter for the whole system to inherit the change. For ex ample, if the length of a database field changes from ten to twenty characters, the change is automatically reflected on all forms that contains the field.
The concept of inheritance is used in all obje ct-oriented programming languages. Their definition differs slightly –the object-oriented programming concept of inheritance refers to one class inheriting methods from a base class.
X++ is the object-oriented programming language that is used in the MorphX environment. When you work with X++, reference the Microsoft Dynamics AX Developer Help, which is available from the Help system.
5.3 Dynamics AX Layered Architecture Application Object Layers
The method used by Microsoft Dynamics AX to se parate and control the updates and modifications made in the application is known as "layering." Layers are a hierarchy of levels in the application-source code that make sure you can make modifications and additions without interfering with the application objects on the level lower than your own. When you modify an object on one level, the modified object overshadows the object on a lower level. Layering is one of the most attractive features for developers and businesses because it enables software to "fit business needs." The advantages to the layered arc hitecture of Microsoft Dynamics AX include the following:
Any user of the Microsoft Dynamics AX application can customize the Microsoft Dynamics AX application.
The standard application is never overwritten.
Deleting an object removes it in the current layer only. Every time an object is opened, the system automatically searches for and uses the object files needed in highest layers first.
The three groups below have an interest in adding or modifying application objects:
Microsoft Business Solution Developers who create the standard application.
Business partners and developers who want to enhance Microsoft Dynamics AX.
Microsoft Dynamics AX end users.
System Application Layers (From Lowest to Highest)
The three innermost layers (SYS, GLS, and DIS) are used by Microsoft Dynamics AX. The four outermost layers (BUS, VAR, CUS, and USR) listed below are modified by developers or end users:
BUS − Business partners can develop and distribute vertical vertical and horizontal solutions to other
partners and customers using the Business Solution or BUS layer. Solutions in the BUS layer are protected by the same license-code framework the standard application uses. The BUS layer is reserved for the Add-on Solution program and requires a signed agreement to use for development and distribution.
t he Value Added Reseller or VAR V AR layer without VAR − Business partners access a separate layer, the business-related restrictions. This means that any developments can be added to this layer. The business partner must keep a catalog of application functionality and VAR configurations customers have implemented to update installations correctly.
CUS − Corporate enterprises and business partners can modify their installations using the Customer
or CUS layer. If a corporate enterprise has an internal IT department with Microsoft Dynamics AX programming skills, use this layer to add generic e nterprise modifications. The Customer layer supports in-house development without jeopardizing modifications made by the business partner. This means that application code created in the VAR layer cannot be changed.
USR − The USR layer enables individual companies or companies in an enterprise to use this layer to
make customizations that are unique to the customers' installation that includes reports by using the report wizard.
5.4 Tools for Customization There are three main tools which can be used to customize Microsoft Dynamics AX depending on the complexity of the customization. These tools are described below:
IntelliMorph – Is used for the automatic layout generation of forms, reports, and me nus.
MorphX – When customization requirements are beyond the basics of IntelliMorph, the next tool of choice is MorphX. Use MorphX to fulfill customization requirements, such as adding new fields to a report or form.
X++ – Is the development language Microsoft Dynamics AX is built upon. This white paper does not go into detail on the X++ environment. There are other training offerings available to learn more about X++.
Certifications for deeper knowledge
Microsoft offers a range of courses for your development staff in order to not only certify your staff, but also allow your staff to get a deeper understanding of our development environment and architecture. Microsoft Certified IT Professional: Professional: Developer for Microsoft Dynamics Dynamics AX 2009 Note You Note You must pass two required exams and two elective exams to obtain a certification. Exam title
Exam number
Required: Development Required: Development Introduction in Microsoft Dynamics AX 2009
Exam MB6-819
Required: MorphX Required: MorphX Solution Development in Microsoft Dynamics AX 2009
Exam MB6-821
Elective: Trade Elective: Trade and Logistics in Microsoft Dynamics AX 2009
Exam MB6-817
Elective: Financials Elective: Financials in Microsoft Dynamics AX 2009
Exam MB6-818
Elective: Installation Elective: Installation and Configuration in Microsoft Dynamics AX 2009
Exam MB6-820
Elective: Production Elective: Production in Microsoft Dynamics AX 2009
Exam MB6-822
Elective: Enterprise Elective: Enterprise Portal Development in Microsoft Dynamics AX 2009
Exam MB6-825
To find out more about Dynamics AX development and architecture:
http://msdn.microsoft.com/en-us/library/cc602654.aspx http://msdn.microsoft.com/en-us/library/aa654810(AX.10).aspx http://msdn.microsoft.com/en-us/dynamics/ax/cc546579.aspx
6 Dynamics AX FrontFront-Office Architecture Guidance
.Net Business Connector
Retail Store Connect
Dynamics AX 2009 Database SP1
Dynamics AX 2009 Database SP1
Retail Transaction Services
Dynamics AX AOS
Dynamics AX Retail POS
Retail Store Connect Dynamics AX Retail POS Database
Dynamics AX Retail POS Terminal
Dynamics AX Client Dynamics AX 2009 Client Using RDC (Remote
Retail for Dynamics AX has a slightly different architecture on the POS-side of the product c ompared to standard Dynamics AX. We have started with a flexible flexible architecture that will allow the customer to implement Dynamics AX for Retail in a variety of configurations which are listed below:
Utilizing Dynamics AX for Retail POS.
Utilizing third-party POS.
Utilizing Dynamics AX ERP for Back Office Financials.
Utilizing third-Party ERP for F inancials.
This type of architecture allows you, the customer, to decide the optimal way to implement the Dynamics Retail stack—giving you, the ultimate choice in flexibility. The following diagram of Dynamics AX for Retail provides you with an overview of this flexible product.
This diagram provides you with a good view of both the Headquarters side of the software, as well as the Store side, with the indicated two-way connection between the POS and the Head Office. The Headquarters side of the software is built on t he core functionality of Dynamics AX and was created utilizing the development platform toolset that is native native to Dynamics AX. But what differentiates Dynamics AX for Retail is the Store and POS applications. These applications were developed with standardized Microsoft platform toolsets and therefore allow additional additional options to handle change. The Store side has the following flow. The interesting option that we offer is on the services side. side. We have several services services that are “plug -andplay” so that if we aren’t providing the correct interface, we can either consume third-party services
and/or a VAR can create their own services to replace replace our DLLs. The following diagram diagram illustrates this concept:
This diagram also illustrates this concept by showing that a Discount.dll that a partner has created is implemented and that the tax rules are swapped out in support of a European implementation.
Dynamics AX Front-Office Typical Integration Points
Retail for Dynamics AX POS is a C#-based and has several typical integration points.
Customizable External Modules
Services – Changing or extending the default functionality.
Triggers – Adding to the default functionality.
Blank operations – Implementing custom operations.
For more information on customizable external modules, please read “Interfaces for Services and Triggers”, which goes into depth on customization of these modules.
https://mbs.microsoft.com/downloads/customer/AX2009Retail/Interfaces https://mbs.microsoft.com/downloads /customer/AX2009Retail/Interfaces for Service s and Triggers.pdf
User Interface:
One of a kind user interface: o
Employing dynamic functionality of user interface components.
The POS’s appearance can be customized : o
Different layouts of user-interface components.
o
Different configuration of user-interface components.
o
Different hardware within one store/chain:
Touch / Keyboard
Terminal peripherals
Printers – POS printer; normal printer
Customizable settings for each employee: o
Role-based access rights
o
User-interface profiles
o
Language settings
For more information on the POS user interface and options, please read “POS Technical Reference”.
https://mbs.microsoft.com/downloads/customer/AX2009Retail/POS https://mbs.microsoft.com/downloads /customer/AX2009Retail/POS Technical Reference.pdf
7 Summary To summarize the guidance on the Microsoft Dynamics AX for Retail solution there are various choices that a retail organization must make to achieve the goal of a comprehensive end -to-end solution that connects point-of-sale, store operations, merchandising and ERP functions. The choices that will need to be considered with an implementation partner include:
Which retail functionality is required
Deployment model (central vs distributed data)
Existing system migration/integration needs
Implementation partner selection – including expertise, experience and use of a proven implementation methodology such as SureStep
Relationship of the implementation partner with other Microsoft Certified IS Vs who can be part of the solution as needed
Microsoft Dynamics AX for Retail simplifies the solution by providing end-to-end capabilities and deployment choices to meet the needs of retailers. Migration and integration are also critical to achieving a seamless business business operation for retail users. Microsoft has a delivery-partner-certification program that enables partners to fully explore the capabilities of Dynamics AX for Retail. Microsoft recognizes that this partner ecosystem e cosystem is best suited to explore the unique needs of each retail business.
A Appendix
A.1 OS, CPU, Memory and HardHard -Disk Requirements The supported operating systems, minimum and recommended processor (CPU), memory (RAM), and hard-disk space requirements for each type of computer are listed in the following table. Important note: Unless otherwise indicated, you must install the latest service pack (SP) for each operating system.
Home editions of the Windows ® 7, Windows Vista ®, and Windows XP operating systems are not supported. Each computer must have at a minimum, m inimum, an Intel Pentium or Celeron family or compatible processor. Each registered computer that will be used to process card payments must have Internet access. Fees may apply.
Type of computer
Supported operating systems
Application Object Server
Windows Server 2008 R2 Windows Server 2008 (x86 or x64) Windows 7 (x86 or x64) Windows Vista (x86 or x64) Window XP SP2 or SP3 See Hardware and Software Requirements for Installing SQL Server 2008 or SQL Server 2005 System Requirements. Windows Server 2008 R2 Windows Server 2008 (x86 or x64)
Dynamics AX client computer Head-office database server
Head-office communications server (see the note following this table).
Store database computer
Store communications server
See Hardware and Software Requirements for Installing SQL Server 2008. Windows Server 2008 R2 Windows Server 2008 (x86 or x64) Windows 7 (x86 or x64)
Minimum processor speed, RAM, and hard-disk space See Microsoft Dynamics AX 2009 System Requirements.
See Microsoft Dynamics AX 2009 System Requirements. See Hardware and Software Requirements for Installing SQL Server 2008 or SQL Server 2005 System Requirements. Minimum: 1.1 GHz (x86) or 1.4 GHz (x64), 1 GB RAM, 1.5 GB available hard-disk space Recommended: 2 GHz, 2 GB RAM See Hardware and Software Requirements for Installing SQL Server 2008. Minimum: 1.1 GHz (x86) or 1.4 GHz (x64), 1 GB RAM, 1.5 GB available hard-disk space Recommended: 2 GHz, 2 GB RAM
Windows Vista (x86 or x64)
Retail POS register (with or without database)
Windows 7 (x86 or x64) Windows Vista (x86) Windows XP SP2 or SP3 (x86) POSReady 2009 (x86)
Minimum: 1.4 GHz, 1 GB RAM, 1.5 GB available hard-disk space Recommended: 2 GHz, 2 GB RAM
NOTES:
On a head-office communications server where Retail Sto re Connect is installed but not Retail Transaction Service, Windows 7 and Windows Vista are also supported. SQL Server 2005 is supported only for the head-office database. For Retail Store Connect message databases and Retail POS databases, SQL Server 2008 Standard, Enterprise, or Express is required.
Other Hardware Requirements
As described in earlier in the Deployment scenarios section, it is recommended that you have a minimum of four computers at the head office: the Application Object Server computer, the database server, a communications server, and at least one client computer. At the store, it is recommended that you have a communications server, one computer for each register and in stores where it is appropriate, a database server. Each store m ust also have enough peripheral devices—such as receipt printers, cash drawers, MSR devices, PIN pads, and the like—for each register in the store, and each register should be equipped with a Super VGA (1024x768) or higher-resolution monitor or a touch-screen monitor and a Microsoft mouse or compatible pointing device. Throughout the organization, you must have enough hardware to support the network infrastructure.
A.2 Links to External Resources Microsoft Architecture Guidance for the Enterprise Retail Store whitepaper
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=E9CEC4E9-029A-4E8C-A8858E9F58373226&displaylang=en Microsoft Dynamics AX for Retail Website
https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUI D={30D63E76-32C1-4C06-915120C63CD0F522}&NRORIGINALURL=/partnersource/deployment/resources/productreleases/microsoftdy namicsaxforretailps.htm?printpage=false&NRCACHEHINT=Guest&prin namicsaxforretailps.htm?printpage=fal se&NRCACHEHINT=Guest&printpage=false&wa=wsignin1.0 tpage=false&wa=wsignin1.0 Dynamics AX for Retail Landing Page
https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUI D={30D63E76-32C1-4C06-915120C63CD0F522}&NRORIGINALURL=/partnersource/deployment/resources/productreleases/microsoftdy namicsaxforretailps.htm?printpage=false&NRCACHEHINT=Guest&prin namicsaxforretailps.htm?printpage=fal se&NRCACHEHINT=Guest&printpage=false&wa=wsignin1.0 tpage=false&wa=wsignin1.0 Microsoft Dynamics AX for Retail R2 VPC Website
https://mbs.microsoft.com/partnersource/support/selfsupport/productreleases/AXRetailR2VirtualPC Dynamics Sure Step Website
https://mbs.microsoft.com/partnersource/partneressentials/serviceplans/surestep/ Role Tailored Learning Plans for Microsoft Dynamics AX for Retail Website
https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUI D={88918F31-5F41-45D6-96ABD6BF0EBE10FB}&NRORIGINALURL=/partnersource/partneressentials/partnerreadiness/partneracademy /msdax2009retailpartreadiness.htm?printpage=false&stext=AX&NRCACHEHINT=Guest&printpage=false &stext=AX&wa=wsignin1.0 Microsoft Dynamics AX 2009 Benchmarks Website: Refer to this link for benchmark documentation.
http://go.microsoft.com/fwlink/?LinkID=146838
