AX2012install
ax2012 导入客户信息的方法
Data Model Diagram: Global Address BookVSD: https:///open?id=0B3rbAZy5q2ExZjI2ZmQwNTctMzZjMi00MDViLThi M2EtZDY3YjQ5OGJlNDA0Red area highlights tables forming Address book – Person data modelGreen area highlights tables forming Address book – Organization data modelsYellow area highlights tables implementing Electronic Address data model Blue area highlights tables implementing Postal Address data model CustomersWalkthrough:ConnectionAdd DataDynamics AX ErrorAdd TablesField ChooserName.Party IDCustomer account – Number sequenceDisplay asAddress book ID – Number sequencePostal addressPostal addressrelationships.Location IDExpiration:Expiration:Sequence:1.DirPartyTable – Publish Selected2.LogisticsLocation – Publish Selected3.DirPartyLocation – Publish Selected4.DirPartyLocationRole – Publish Selected5.LogisticsElectronicAddress – Publish Selected6.LogisticsPostalAddress – Publish Selected7.CustTable – Publish SelectedResult:Dynamics AX – Address bookDynamics AX – Address book AddressDynamics AX – Address book Contact informationDynamics AX – CustomerDynamics AX – Customer AddressDynamics AX – Customer Contact informationSQL Trace:Summary: For the purposes of small or medium data migration (data conversion) where performance is not a concern Excel can be used for import of customers into Microsoft Dynamics AX 2012. Although Customer AIF Web Service (CustCustomerService) can’t be used at the moment in Excel for import of customers, appropriate tables can be used instead. Excel template can be created and used for import of customers.Author: Alex Anikiev, PhD, MCPTags: Dynamics ERP,Dynamics AX 2012, Excel, Dynamics AX 2012 Excel Add-in, Data Import, Data Conversion, Data Migration, Application Integration Framework, Customers.Note: This document is intended for information purposes only, presented as it is with no warranties from the author. This document may be updated with more content to better outline the concepts and describe the examples. It’s recommended that all Data Model changes introduced as a part of this demonstration will be removed once you complete data import exercise.。
3ds max2012-安装教程
安装步骤：
1.鼠标右键，选择解压到“3Ds Max 2012”
2.双击打开【安装包】文件夹
3.找到并选中Setup，鼠标右键选择“以管理员身份运行”
4.点击“安装”
5.勾选我接受，再点击“下一步”
6.输入序列号：666-66666666，产品密钥：128D1，点击“下一步”
15.双击打开【注册机】文件夹
16.选中xf-adesk2012，鼠标右键选择“以管理员身份运行”
＜温馨提示：若打开没有注册机，说明被电脑杀毒软件隔离了，关闭杀毒软件重新解压即可。
17.将申请号复制到Request输入框中
注意：复制和粘贴只能用快捷键"Ctrl+C"和”Ctrl+V”
18.点击“Mem Patch”，再点击“Generate”
7.选择软件安装路径，点击“安装”
8.软件正在安装，耐心等待即可
9.点击“完成”
10.双击电脑桌面上的3ds Max2012图标，运行软件
11.点击“激活”
12.勾选我已阅读.......，再点击“继续”
13.如果出现以下这种提示，点击“关闭”，重复步骤11
14生成的激活码复制到激活码输入框，点击“下一步”
注意：复制和粘贴只能用快捷键"Ctrl+C"和”Ctrl+V”
20.点击“完成”
21.安装结束
AutoCAD ARX2012开发环境搭建
AutoCAD ObjectARX2012开发环境搭建网上教材对于AutoCAD老版本的教材比较多，就算是ObjectARX自带的Samples也是这样。
本文就ACAD2012及以后版本做详细讨论，计划做成一个系列，后续还会有更多精彩内容尽请期待。
首先准备好以下内容：1.安装VS2008,安装SP1补丁。
2.访问Autodesk下载ObjextARX2012和ObjARXWiz（向导程序ArxWizards.msi）在Autodesk官网可以看到如下兼容信息：按照下面步骤新建测试程序：1.配置VC++目录选择好你的平台，我用的是64位操作系统和64位AutoCAD所以这里是x64。
添加包含文件目录：添加库文件目录：2.新建工程下一步下一步下一步下一步下一步最后点完成。
3.添加命令和测试代码新建命令的按钮没有图标，所以有点奇怪。
但你用鼠标移动到上面会有提示。
在对话框上右键新建命令的名字都改成“Hello”完成后确认。
找到arxEntryPoint.cpp文件添加下面语句：AfxMessageBox(L"Hello ARX");4.编译测试编译好后找到.arx文件，启动AutoCAD2012，输入命令appload进行加载。
加载成功后，输入Hello命令进行测试5.代码分析1.CArxProject1App是应用程序对象，父类是AcRxArxApp，在这里完成了大部分主要的工作。
2.静态函数GGPArxProject1Hello和AutoCAD中相应命令做关联，能在输入命令后调用该方法。
3.ACED_ARXCOMMAND_ENTRY_AUTO(CArxProject1App, GGPArxProject1, Hello, Hello,ACRX_CMD_TRANSPARENT, NULL)完成了上述命令的关联。
Microsoft Dynamics AX 2012安装文档_中文
目录1. 系统环境 (2)2. 配置基本环境 (2)a) 配置域环境 (2)b) 还原测试数据库 (3)3. 安装AX2012基本框架DB+AOS+Client (3)a) 运行autorun (3)b) 安装必需的补丁和插件 (4)c) 开始安装 (4)d) 继续安装，安装补丁包CU7 (6)e) 登录系统，同步和编译 (7)4. 安装Office扩展 (12)5. 安装Visual Studio (13)6. 安装Report Services扩展 (14)7. 安装Analysis Services 配置 (17)8. 安装企业门户EP (19)a) 安装SharePoint (19)b) 安装企业门户EP (19)9. 安装帮助服务器 (22)Microsoft Dynamics AX 2012安装文档1.系统环境Windows2008R2SP1+SQL2008R2SP2因为使用的是云计算机，就直接从映像中还原一个系统，默认已经配置好SQL2008R2SP22.配置基本环境a)配置域环境如果已经有域环境，只需要将当前主机加入域即可，现在是单机安装就自己安装一个域服务器管理-角色-添加角色选择Active Directory域服务进行安装，具体过程就不介绍了，不懂问度娘。
安装完成后创建两个用户BCAdmin和AXAdmin，用来运行BC和AOS（其实单机使用可以不用域帐户，但安装AX时要求必须要域帐户，可以安装完后到服务配置中修改成其他帐户）注：安装完域服务后，可能会造成SQL服务无法启动，只需要将运行SQL服务的用户改成域帐户或者本地帐户就可以b)还原测试数据库本次安装是为了测试使用，所以就直接使用微软发布的测试数据库测试数据库备份文件：/s/1eRj0h将下载的Bak文件通过SSMS进行还原，共两个Bak文件不懂数据库还原的，请自觉找度娘…3.安装AX2012基本框架DB+AOS+ClientAX2012R2安装包：/s/1cPrPq最好的解压出来在安装，不建议用虚拟光驱，安装时会提示找不到diska)运行autorun选择安装Microsoft Dynamics AX 组件选择自定义安装b)安装必需的补丁和插件点击错误项的下载链接就可以从MS官方下载对应的补丁和插件，强烈建议使用迅雷下载，你懂的这是一个十分漫长的过程…当你将这些一个个下载好，一个个安装完，你会觉得想骂一句：XX的MS，就不能在安装包里一次性安装？？！！将这些都安装完，就可以继续下一步这是我安装时用到部分补丁和插件：/s/1y3XwXc)开始安装XXX！这才开始啊…选择你之前还原的数据库，别选到Model上去！接下来就是Next，Next…到选择运行AOS的帐户，自己看着办…继续Next，Next…终于出现安装了接下来就没你事了，等吧…终于等到了她不动了，只留下一个完成的按钮给你，等你来终结这次的安装。
AX2012开发规范
Class is packing element IDs instead of element names. The form must include a grid that contains ValidFrom and ValidTo fields when that form has a data source with ValidTimeStateAutoQuery set to DateRange. Table is using CreatedDateTime or ModifiedDateTime, RecId index needs to be created. The class %1 is obsolete. Instead, use the Class %2 Do not use braces around the case blocks in a switch statement. Do not use the <syntax> tag in XML documentation. The syntax is derived from the method declaration, and must not be explicitly provided. Line item workflow '%1' event handler does not reference a valid class implementing the '%2' interface Line item workflow relation '%1' not found on workflow document query '%2’ Line item workflow relation '%1' is invalid. Relation must be configured with a fetch mode of 1:n on workflow document query '%2'
AX2012安装步骤
哪些支持软件及补丁或者该如何配置系统以符合安装要求。
AX2012插件）、VisualStudio 2010以及IIS相关服务。
需要安装sharepoint服务需要安装Projects服务2、需要安装windows的相关服务。
（下面会详细介绍）通过单击Error或者Link弹出的信息中描述了如何解决问题。
这些补丁都已经下载了，安装后，应该不会再有这些错误信息。
里两项Roles。
这里显示已经安装的角色。
6、上述Roles安装完成之后，需要安装一些相关的Features，单击Server Manager左侧的WCF Activation b、Web Servers IIS Tools c、Windows Process Activation Services。
）注意红色方框内的项目都必须安装。
红色方框中的项目如果已安装就不需要再安装了。
7、上述Features安装完成后，在ServerManager中能看到如下图所示的Web Service（IIS）下拉列表，单击WebService(IIS)后，单击右侧的AddRole Services。
8、单击Add Roles Server后弹出如下图所示的Select Role Services对话框，选择红色方框的项目后，单击Install按钮进行安装。
安装完成后，RoleService列表中应该显示右侧红色方框所示的服务项目。
databasename 可以使用默认值，如下图所示。
如果没有问题，安装程序就正式开始安装了。
New Development Workspace菜单来启动如下图所示。
1)AX2012里配置Report Server，并验证OK，下图；2)报表发布输入命令Publish-AXReport –ReportName *3)如何在Win 7上发布报表。
ax2012 导入产品的方法
Data Model Diagram:Products and Released ProductsVSD: https:///open?id=0B3rbAZy5q2ExMWUzOGM4ZDEtNzE2OS00Yzk2L WIxYzEtOTkzNTU3M2RiZTMwRed area highlights tables forming Products and Product Masters data modelGreen area highlights tables forming Released Products data models Blue area highlights tables implementing Product Dimensions data modelWalkthrough:ConnectionAdd DataDynamics AX ErrorSolution-Add replacement key to DocuValue tableDynamics AX ErrorNo Solution yet Add TablesField Chooser1.EcoResProduct – Publish Selected2.EcoResProductIdentifier – Publish Selected3.EcoResProductDimensionGroupProduct – Publish Selected4.InventTable – Publish SelectedResult:Dynamics AX – Released ProductSQL Trace:Product-EcoResProduct (INSERT)-EcoResDistinctProduct (INSERT)-EcoResProductIdentifier (INSERT)-EcoResProductTranslation (INSERT)Product Master-EcoResProduct (INSERT)-EcoResProductMaster (INSERT)-EcoResProductIdentifier (INSERT)-EcoResProductDimensionGroupProduct (INSERT)-EcoResProductMasterModelingPolicy (INSERT)-EcoResProductTranslation (INSERT)Product Master – Product Dimension (Size) -EcoResProductMasterDimensionValue (INSERT)-EcoResProductMasterSize (INSERT)-EcoResSize (INSERT)Product Master – Product Variant-EcoResProduct (INSERT)-EcoResDistinctProduct (INSERT)-EcoResDistinctProductVariant (INSERT)-EcoResDistinctProductTranslation (INSERT)-EcoResProductVariantDimensionValue (INSERT)-EcoResProductVariantSize (INSERT)Released Product – Product-EcoResProduct (INSERT)-EcoResDistinctProduct (INSERT)-EcoResProductIdentifier (INSERT)-EcoResProductTranslation (INSERT)-InventItemSalesSetup (INSERT)-InventItemInventSetup (INSERT)-InventItemPurchSetup (INSERT)-InventTable (INSERT)-InventTableModule [Sales] (INSERT)-InventTableModule [Invent] (INSERT)-InventTableModule [Purch] (INSERT)-InventItemLocation (INSERT)-InventItemSetupSupplyType (INSERT)Released Product – Product Master -EcoResProduct (INSERT)-EcoResProductMaster (INSERT)-EcoResProductIdentifier (INSERT)-EcoResProductDimensionGroupProduct (INSERT) -EcoResProductMasterModelingPolicy (INSERT) -EcoResProductTranslation (INSERT)-InventItemPurchSetup (INSERT)-InventItemInventSetup (INSERT)-InventItemSalesSetup (INSERT)-InventTable (INSERT)-InventTableModule [Sales] (INSERT)-InventTableModule [Invent] (INSERT)-InventTableModule [Purch] (INSERT)-InventItemLocation (INSERT)-InventItemSetupSupplyType (INSERT)Released Product – Product Dimension-EcoResProductMasterDimensionValue (INSERT)-EcoResProductMasterSize (INSERT)-EcoResSize (INSERT)Release Product – Released Product Variant-EcoResProductVariantDimensionValue (INSERT)-EcoResProductVariantSize (INSERT)-EcoResSize (INSERT)-InventDim (INSERT)-InventDimCombination (INSERT)Summary: For the purposes of small or medium data migration (data conversion) where performance is not a concern Excel can be used for import of products into Microsoft Dynamics AX 2012. Although Item AIF Web Service (InventItemService) can’t be used at th e moment in Excel for import of products, appropriate tables can be used instead. Excel template can be created and used for import of products.Author: Alex Anikiev, PhD, MCPTags: Dynamics ERP,Dynamics AX 2012, Excel, Dynamics AX 2012 Excel Add-in, Data Import, Data Conversion, Data Migration, Application Integration Framework, Products.Note: This document is intended for information purposes only, presented as it is with no warranties from the author. This document may be updated with more content to better outline the concepts and describe the examples. It’s recommended that all Data Model changes introduced as a part of this demonstration will be removed once you complete data import exercise.。
dynamics ax 2012操作手册
《深度挖掘：Dynamics AX 2012操作手册》一、引言Dynamics AX 2012是一款功能强大的企业资源规划（ERP）软件，被广泛应用于各种规模的企业中。
作为企业管理者或IT从业者，熟练掌握Dynamics AX 2012的操作技巧对于提高工作效率、优化企业管理流程具有重要意义。
在本文中，我们将深度挖掘Dynamics AX 2012的操作手册，为您带来全面而深入的学习体验。
二、初识Dynamics AX 20121. 系统概述Dynamics AX 2012是由微软（Microsoft）开发的一套集成管理软件系统，旨在实现企业资源的综合管理和效率优化。
它包括了财务、采购、生产、销售、仓储等多个功能模块，为企业提供了一站式的解决方案。
2. 操作界面Dynamics AX 2012的操作界面简洁直观，主要分为主菜单、导航栏、工作区域和详细信息四大部分。
用户可以通过简单的点击和拖放操作来实现复杂的业务流程。
3. 操作手册Dynamics AX 2012的操作手册是用户学习的重要工具，它详细介绍了系统的功能和操作步骤，对用户的学习和使用起到了重要的辅助作用。
三、深度挖掘Dynamics AX 2012操作手册1. 功能模块Dynamics AX 2012的操作手册详细介绍了各个功能模块的操作方法和使用技巧。
在财务模块中，可以学习到如何设置会计科目、录入凭证、生成报表等操作；在采购模块中，可以学习到如何创建采购订单、进行验收入库、付款等操作。
2. 操作技巧操作手册不仅介绍了系统的基本操作，还深入探讨了一些高级的操作技巧。
在生产模块中，可以学习到如何进行生产订单的排程和跟踪、如何进行生产成本的核算和分析等高级技术。
3. 定制化开发Dynamics AX 2012的操作手册还介绍了系统的定制化开发方法。
通过学习操作手册，用户可以掌握系统表单的设计方法、报表的设计方法、工作流的配置方法等，从而实现系统与企业实际业务的无缝对接。
3dmax2012官方中文版安装图文教程
第一步：准备3dsmax2012 32/64位中文版安装包(图一)(图二)(图三)选择安装产品。
如图三。
(图四)国家或地区选择中国，勾选接受相关协议，点击下一步。
如图四。
(图五)在这个界面，最上面一栏是许可类型，这里有两种，一种是单机许可，另外一种(图六)3dsmax2012 32/64位中文版默认的安装路径是在c盘里，大家都清楚，c(图七)3dsmax2012 32/64位中文版正在安装中~~~~~~~。
3dsmax2012 64中文版正在安装中~~~~~~。
注意：在win8系统下安装3D MAX 2012提示安装程序检测到monitor.exe正在运行，要完成安装，必须关闭monitor.exe。
正常情况的话，在任务管理器里直接找到monitor.exe进程关闭就可以了，但在任务管理器里没有找到monitor.exe这个进程，，这时我们只要关闭这个进程就可以，win8系统下在哪里关闭monitor.exe这个进程呢。
具体关闭这个进程的方法如下两种：1，monitor.exe这个进程是是Microsoft服务器操作系统硬件监视服务相关程序。
我们可以在任务管理器上点性能选项卡，底部会有一个资源监视器的链接。
在资源监视器里cpu和内存两个选项卡里都有monitor.exe这个进程，只要关闭这个进程。
就可以进行3DMAX的下一步安装。
2，控制面板-管理工具那就可以找到资源监视器。
或者直接在右侧系统磁贴直接搜索就可以找到。
如图七。
8第八步：3dsmax2012 32/64位中文版安装完成(图八)3dsmax2012 32/64位中文版安装完成，点击完成。
如图八。
(图十)3dsmax2012 32/64位中文版后，提示激活3dsmax2012 32/64位中文版，点击激活。
如图十。
(图十一)勾选已阅读相关保护政策，点击继续如图十一。
第十二步：关闭激活界面(图十二)到这步时，有些教程选择断网激活，这里提供另一种激活方式。
微软动态AX2012R3服务器 客户端许可证模型指南说明书
SummaryMicrosoft Dynamics AX 2012 R3 is available under the Server/CAL licensingmodel. Under this model, a Server license is required for the server(s) runningthe solution, and Client Access Licenses (CALs) are required for accessing theservers.Licensing a Server to Run the Microsoft Dynamics AX 2012 R3 Solution Before you run any instance of the Microsoft Dynamics AX 2012 R3 Server software under a Server license, you must assign that license to one of your servers. That server is the licensed server for that particular license. You may assign other Server licenses to the same server, but you may not assign the same license to more than one server. A hardware partition or blade is considered to be a separate server. For each Microsoft Dynamics AX 2012 R3 Server license you assign, you may run, at any one time, one instance of the server software in one physical or virtual operating system environment (OSE) on the licensed server. The Server license includes one application object server. If you want additional application object servers or additional server instances, you must purchase additional Microsoft Dynamics AX 2012 R3 Server licenses. Licensing Access to the Microsoft Dynamics AX 2012 R3 SolutionAccess to the Microsoft Dynamics AX 2012 R3 solution’s functionality is licensed through CALs. Any time a user directly or indirectly accesses the solution functionality, that user must be licensed by a User CAL (which licenses a specific user for access via multiple devices) or the device being used must be licensed by a Device CAL (which licenses access through a specific device by any user).There are four available CAL levels for Microsoft Dynamics AX 2012 R3, each of which grants an increasingly wider spectrum of use rights. This gives customers the flexibility to license the solution based on how their users will use and derive value from the solution.As you progress from the lowest level CAL (Self Serve) to the highest level (Enterprise), the user is licensed to use the solution in ways that will provide more value. Customers therefore have the flexibility to decide the level of investment to make based upon the functions a certain group of users is performing on behalf of the organization.Access by External UsersExternal (third party) users do not require licenses. Third party users are usersthat are not either (i) your or your affiliates’ employees, or (ii) your or youraffiliates’ contractors or agents. In this sense, the definition of third party usersdoes not extend to onsite contractors, vendors and users performing businessprocesses on your behalf.MultiplexingMultiplexing is the use of hardware or software to reduce the number of devices or individuals that access or use the Microsoft Dynamics AX 2012 R3 solution by pooling connections. Multiplexing does not reduce the number of licenses required to access Microsoft Dynamics AX 2012 R3 solution. Any user that accesses the Microsoft Dynamics AX 2012 R3—whether directly or indirectly —must be properly licensed.Note : Licensed users may manually rekey information (when coming from non-licensed users) into the Microsoft Dynamics AX 2012 R3 solution. This scenario is not considered to be multiplexing.Licensing Additional SoftwareLicenses for additional software that may be required for the solution, such as Windows Server, Microsoft SQL Server, and Microsoft SharePoint Server and their corresponding CALs are not included with the Microsoft Dynamics AX 2012 R3 licenses. They must be acquired separately in accordance with licensing models for those products. These licenses may be purchased through traditional volume licensing channels.The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, this document should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. ©2014 Microsoft Corporation. All rights reserved.。
微软动态AX2012R3零售与电子商务许可指南说明书
Using This GuideUse this guide to improve your understanding of how to license Microsoft Dynamics AX 2012 R3 for Retail and eCommerce scenarios. It is not intended to guide you in choosing Microsoft Dynamics products and services. The examples presented in this guide are illustrative. Microsoft Corporation reserves the right to review and/or update the existing version without previous notice.In order to understand this document, is essential that you first read and understand the Microsoft Dynamics AX 2012 R3 Licensing Guide.For help determining the right technology solution for any given organization, including the license requirements for a specific product or scenario, consult with your Microsoft Dynamics Certified Partner or your Microsoft account team. This guide does not supersede or replace any of the legal documentation covering use rights for Microsoft products. Specific product license terms are detailed in the Software License Terms document, which is available on the on the Microsoft Dynamics AX website.ContentsLicensing the Microsoft Dynamics AX 2012 R3 Solution (3)Types of Licensing Models (3)Retail Licensing Scenarios (5)Scenario 1: Traditional Store (Brick and Mortar) (5)Scenario 2: Mobile POS (6)Scenario 3: eCommerce (6)Licensing the Microsoft Dynamics AX 2012 R3 Solution Microsoft Dynamics AX 2012 R3 introduces new capabilities for retail and eCommerce configurations. Below is a summary of some of these great improvements, additional product details can be found here.∙Modern Point of Sale (POS), assisted sales and centralized store management∙eCommerce and Social integration∙Omni-channel management∙Order management, processing and payment∙Merchandizing and catalog managementThis new release provides the perfect opportunity to introduce a new and simplified pricing and licensing model specifically designed for retail and eCommerce configurations. We are providing guidance for three separate licensing configurations, recognizing that some customers may have a mix of these configurations.∙Traditional Store (Brick and Mortar stores)∙Mobile POS∙eCommerceThis brief focuses on the required licenses for such Retail and e-Commerce specific configurations. In any of these scenarios, you must still be properly-licensed for the underlying Microsoft Dynamics AX 2012 R3. For additional Microsoft Dynamics AX 2012 R3 licensing details, please refer to this link.T YPES OF L ICENSING M ODELSThe Microsoft Dynamics AX 2012 R3 licensing utilizes the Server + Client Access License (CAL) model. This same model will be used for the Traditional Store and Mobile POS solutions. With the Microsoft Dynamics AX 2012 R3 eCommerce solution we will be introducing a Per Core licensing model. Below are high level descriptions of these two licensing models.Server + CAL Licensing ExplanationFor the Microsoft Dynamics AX 2012 R3 solution you need to license Server plus CALs: ∙Microsoft Dynamics AX 2012 R3 solution functionality is licensed through the Microsoft Dynamics AX 2012 R3 Server license. Each running instance of the Microsoft Dynamics AX 2012 R3 Serversoftware requires a Server license.∙Direct or Indirect Access to the Microsoft Dynamics AX 2012 R3 solution functionality by users or devices is licensed through CALs. Every user or device accessing the solution functionality—whether directly or indirectly—must be covered by a CAL.Figure 1: Server + CAL LicensingPlease note that this traditional Server/CAL model will be utilized for the Traditional Store and Mobile POS scenarios. See below for specific scenario descriptions.Per Core Licensing ExplanationeCommerce Servers are licensed based on computing power, as measured by processing cores. Core-based licensing provides a more precise measure of computing power than processors and a more consistent licensing metric, regardless of whether solutions are deployed on physical servers on-premises, or in virtual or cloud environments.Under the Per Core licensing model, each eCommerce Server must be assigned an appropriate number of Microsoft Dynamics AX 2012 R3 Standard Commerce Core licenses. The number of core licenses needed depends on whether you are licensing the physical server or individual virtual Operating System Environments (OSEs).Note: Microsoft Dynamics AX 2012 R3 Standard Commerce Core licenses are sold in packs of two.You have the following two options for licensing under the per core licensing model: ∙Individual Virtual Operating System Environment (OSE). You can license based on individual virtual OSEs within the servers that are running the server software. If you choose this option, for each virtual OSE in which you run the server software, you need a number of licenses equal to the number of virtual cores in the virtual OSE, subject to a minimum requirement of four licenses per virtual OSE. In addition, if any of these virtual cores is at any time mapped to more than onehardware thread, you need a license for each additional hardware thread mapped to that virtual core. Those licenses count toward the minimum requirement of four licenses per virtual OSE.∙Physical Cores on a Server. You can license based on all of the physical cores on the server. If you choose this option, the number of licenses required equals the number of physical cores on the server multiplied by the applicable core factor located in the Core Factor Table.For more information about this licensing model, refer to the “Introduction to Per Core Licensing and Basic Definitions” Volume Licensing Brief.Retail Licensing ScenariosThe scenarios below help to illustrate of how to license Microsoft Dynamics AX 2012 R3 in three common retail scenarios: a Traditional Store, Mobile POS and eCommerce site. While we are providing guidance for three separate licensing configurations, we recognize that some customers may have a mix of these configurations.Note that these illustrations are intended to provide a conceptual understand of the licensing policies. They do not serve as actual deployment diagrams. For instance, where a single server is shown to illustrate the need for Server licenses, an actual solution deployment will like require multiple servers running instances of the software, and thus requiring licenses.S CENARIO 1:T RADITIONAL S TORE (B RICK AND M ORTAR)In this scenario, the Microsoft Dynamics AX 2012 R3 solution is being run on central servers at headquarters. Any servers running instances of the Microsoft Dynamics AX 2012 R3 software require one Server license per running instance.Each store locations will need to license a Microsoft Dynamics AX 2012 R3 Store Server which provides access to the following new Microsoft Dynamics AX 2012 R3 capabilities:∙Local caching for offline use of data∙Centralization of POS in the store∙Local management of items such as promotionsStore devices and employees accessing the Microsoft Dynamics AX 2012 R3 solution functionality require CALs as defined in the Microsoft Dynamics AX 2012 R3 Product Use Rights (PUR).Figure 2: Traditional Store ConfigurationS CENARIO 2:M OBILE POSIn this scenario, a retail company has Mobile POS devices directly connect to the central Microsoft Dynamics AX 1012 R3 solution running at the company headquarters. As always, any servers running instance of the Microsoft Dynamics AX 2012 R3 software require one Server license per running instance. These users and devices require CALs to access the solution functional and should be licensed in accordance with the Product Use Rights (PUR).Figure 3: Mobile POSS CENARIO 3: E C OMMERCEIn this scenario, the Microsoft Dynamics AX 2012 R3 solution is being run on central servers at headquarters. Any servers running instance of the Microsoft Dynamics AX 2012 R3 software require one Server license per running instance.The Microsoft Dynamics AX 2012 R3 Standard Commerce Core Server should be licensed for all eCommerce scenarios. Each Microsoft Dynamics AX 2012 R3 Standard Commerce Core Server must be assigned an appropriate number of Microsoft Dynamics AX 2012 R3 Standard Commerce Core licenses as explained above.Store devices and employees accessing the Microsoft Dynamics AX 2012 R3 solution functionality require CALs as defined in the Microsoft Dynamics AX 2012 R3 Product Use Rights (PUR).External users (customers) do not require CALs.Figure 4: eCommerce© 2014 Microsoft Corporation. All rights reserved.This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. This information is provided to help guide your authorized use of products you license; it is not your agreement. Your use of products licensed under your volume license agreement is governed by the terms and conditions of that agreement. In the case of any conflict between this information and your agreement, the terms and conditions of your agreement control. Prices for licenses acquired through Microsoft resellers are determined by the reseller.。
Microsoft Dynamics AX 2012 R3 运输管理（TMS）引擎实现与部署指南说明
Microsoft Dynamics AX 2012 R3Pawel Kruk May 2014This document describes the typical steps for building Transportation management (TMS) engines and utilizing them in Microsoft Dynamics AX.Implementing anddeploying Transportation management enginesContentsImplementing and deploying Transportation management engines 3 Prerequisites 3 Architectural background 3 Tutorial: Construct a Hello-World rate engine 4 Tutorial: Enable a Hello-World rate engine 7 More about TMS engine implementation 8Implementing and deploying Transportation management enginesThe Transportation management (TMS) module includes a number of extension points that let you implement custom algorithms to perform tasks that are related to the rating of transport and freight reconciliation. The implementations of the algorithms are called Transportation management engines (also referred to as TMS engines or engines). The engines are delivered as implementations of specific .NET interfaces and deployed on the Microsoft Dynamics AX Application Object Server (AOS) tier. Each Transportation management engine can be switched on and off, and it can also be tuned at runtime, based on Microsoft Dynamics AX data. Some of the most important objectives of these engines are as follows:•Calculation of transportation rate•Calculation of travel distance from point to point•Calculation of the time it takes to travel from point to point•Zone identification of addresses•Distribution of transportation charges for shipments across source document lines (also referred to as apportionment of charges).Microsoft Dynamics AX 2012 R3 includes a number of fully functional engines that are available out of the box. However, in many cases, new engines might be required in order to satisfy contract requirements. For example, there is no engine that calculates freight charge by using a particular algorithm, or an engine might be required to retrieve rating data directly from a web service provided by the carrier.This document explains the typical steps for building Transportation management engines and utilizing them in Microsoft Dynamics AX. It is targeted to engineers who want to learn how to implement and deploy custom Transportation management engines.PrerequisitesMicrosoft Visual Studio Tools for Microsoft Dynamics AX must be installed. For more information, see/en-us/library/gg889157.aspx.Architectural backgroundThe following illustration shows a simplified view of the TMS system.Within TMS, a number of operations might require some kind of data processing that is specific to a particular carrier, such as transportation rate calculation. Typically, this kind of calculation requires a lot of input data, such as the origin and delivery addresses, the size, weight, and number of packages, and the requested delivery date. For a rate shopping operation, you can track this information from the Rate route workbench form. When you initiate a rate shoppingrequest, request XML is constructed in TMS by using one of the X++ classes that are derived from TMSProcessXML_Base. The request XML is passed to the processing system encapsulated in the .NET assembly named Microsoft.Dynamics.Ax.TMS (also referred to as the TMS managed system). The further processing involves instantiation and utilization of one or more Transportation management engines. The final response from the TMS managed system consists of XML, which is interpreted into a result that is persisted in the Microsoft Dynamics AX database.The source code of the TMS managed system is available in the Microsoft Dynamics AX Application Object Tree (AOT), under the following path: \Visual Studio Projects\C Sharp Projects\Microsoft.Dynamics.AX.Tms.All of the engines that are available out of the box in AX 2012 R3 are defined within the TMS managed system itself. We recommend that all custom engines be implemented in a stand-alone assembly. This assembly should be constructed by using Visual Studio Tools for Microsoft Dynamics AX, and its project should be hosted in the AOT. The Microsoft Dynamics AX server infrastructure ensures that the actual project output is deployed to a server-binary location upon AOS startup. Microsoft Dynamics AX models are the recommended vehicles for distributing the TMS engine implementations to customers. For more information about Microsoft Dynamics AX models, see/en-us/library/hh335184.aspx.Tutorial: Construct a Hello-World rate engineFollow these steps to implement a simple rate engine.1.Follow these steps to enable debugging and hot-swapping of assemblies on the Microsoft Dynamics AX server:1.Open the Microsoft Dynamics AX Server Configuration Utility.2.Create a new configuration.3.Select the Enable breakpoints to debug X++ code running on this server and Enable the hot-swapping ofassemblies for each development session check boxes.The following illustration shows the new configuration.4.Click OK to restart the AOS service.2.From the AOT, follow these steps to open the source of Microsoft.Dynamics.Ax.TMS in a new instance of VisualStudio:1.Navigate to \Visual Studio Projects\C Sharp Projects\Microsoft.Dynamics.AX.Tms.2.On the context menu, click Edit to open Visual Studio.3.Follow these steps to add a new C# Class Library project to the solution:1.In Solution Explorer, right-click your solution node, and then click Add > New Project.2.In the C# project templates, select Class Library.3.Enter HelloWorldEngines as the project name.4.Click OK.4.In Solution Explorer, right-click the HelloWorldEngines project node, and then click Add HelloWorldEngines to AOT.5.Follow these steps to add a project-to-project reference from your project to Microsoft.Dynamics.AX.Tms:1.In Solution Explorer, right-click the HelloWorldEngines project node, and then click Add Reference.2.On the Projects tab, select Microsoft.Dynamics.AX.Tms.3.Click OK.The following illustration shows what your solution should now look like in Solution Explorer.6.Follow these steps to enable deployment of the project output to the Microsoft Dynamics AX server:1.In Solution Explorer, select the project node.2.In the Properties window, set the Deploy to Server property to Yes.The following illustration shows the project properties after this change has been made.7.Follow these steps to implement a rate engine called HelloWorldRateEngine:1.In Solution Explorer, rename Class1.cs to HelloWorldRateEngine.cs.2.Implement the HelloWorldRateEngine class.The following example shows how to implement this class.namespace HelloWorldEngines{using System;using System.Xml.Linq;using Microsoft.Dynamics.Ax.Tms;using Microsoft.Dynamics.Ax.Tms.Bll;using Microsoft.Dynamics.Ax.Tms.Data;using Microsoft.Dynamics.Ax.Tms.Utility;/// <summary>///Sample rate engine class using rating formula of quantity * factor./// </summary>public class HelloWorldRateEngine : BaseRateEngine{private const string RATE_FACTOR = “RateFactor”;private decimal rateFactor;/// <summary>///Initializes the engine instance./// </summary>/// <param name=”rateEngine”>Rate engine setup record.</param>/// <param name=”ratingDto”>Rating data transfer object.</param>public override void Initialize(TMSRateEngine rateEngine,RatingDto ratingDto){base.Initialize(rateEngine, ratingDto);RateEngineParameters parameters =new RateEngineParameters(TMSEngine.RateEngine,rateEngine.RateEngineCode);// Try to retrieve decimal value of RateFactor parameter specified// on engine setup Parametersif (!Decimal.TryParse(parameters.RetrieveStringValue(RATE_FACTOR),out rateFactor)){// Throw TMS Exception. The exception message is shown in infolog.// Additional exception data is recorded in// “Transportation system error log”throw TMSException.Create(“HelloWorldRateEngine requires definition of RateFactor parameter with valid decimal value”,TMSExceptionType.TMSEngineSetupException);}}/// <summary>///Calculates rate./// </summary>/// <param name=”transactionFacade”>The request transaction facade.</param>/// <param name=”shipment”>Rated shipment element.</param>/// <param name=”rateMasterCode”>Rate master code.</param>/// <returns>Updated rating data transfer object.</returns>public override RatingDto Rate(TransactionFacade transactionFacade,XElement shipment,string rateMasterCode){// Use extension method to sum down the item// quantity from the shipment XML elementdecimal quantity = shipment.SumDown(ElementXmlConstants.Quantity);// Retrieve or create rating elementXElement rateEntity = shipment.RetrieveOrCreateRatingEntity(this.RatingDto);// Use extension method to record rate// This method does not record additional information// like unit counts, currency etc.rateEntity.AddRate(TmsRateType.Rate, quantity * rateFactor);return this.RatingDto;}}}8.In Solution Explorer, select the HelloWorldEngines project node, and then click Add HelloWorldEngines to AOT.9.Follow these steps to deploy the engine assembly:1.In Solution Explorer, right-click your project node, and then click Deploy.2.Restart AOS.Your engine assembly is now available for use in Microsoft Dynamics AX. You can verify that HelloWorldEngines.dll is available in the following folder: [AOS installation location]\bin\VSAssemblies.Tutorial: Enable a Hello-World rate engineFollow these steps to enable the engine that you implemented and deployed in the previous tutorial.1.Follow these steps to create a rating engine in Microsoft Dynamics AX:1.Click Transportation Management > Setup > Engines > Rate engine to open the Rate engine form.2.Create a new record that refers to the engine that you created in step 4 of the previous tutorial:•Rate engine: HelloWorld•Name: Hello World Rate Engine•Engine assembly: HelloWorldEngines.dll•Engine type: HelloWorldEngines.HelloWorldRateEngineThe following illustration shows the new record.Note: Because your engine does not source any data from Microsoft Dynamics AX, you don’t need to construct andassign a rate base type for it.2.Follow these steps to specify a value for the RateFactor parameter:1.In the Rate engine form, click Parameters.2.Create a parameter record for RateFactor, and assign a value of3.Your engine is now ready for use.To test the engine, assign it to the rating profile of an active carrier, and run the rating, based on a source document that includes at least one line with a specific quantity. The total rate is computed as (Total lines quantity) * (RateFactor value). The Hello-World engine implementation is not currency-sensitive.For more information about how to associate shipping carriers with rate engines, see Set up shipping carriers and carrier groups.More about TMS engine implementation•Extension types– The following table enumerates the most important interfaces and abstract classes for building engine extensions. All these base types are defined in the Microsoft.Dynamics.Ax.Tms.Bll namespace.•User messages– To format a language-specific user message, use the Microsoft.Dynamics.Ax.Tms.TMSGlobal class that is defined in the TMS managed system. This class contains an overloaded method, called getLabel, that lets you retrieve a Microsoft Dynamics AX label in the current user language.•Language-sensitive data– The input and output XML can contain elements that carry language-sensitive data, such as dates or decimal numbers. The TMS managed system enforces that the current language of the thread is set to invariant. Use System.Globalization.CultureInfo.CurrentCulture to serialize and de-serialize XML data. •Accessing data from Microsoft Dynamics AX– A rate engine might require read or write access to the Microsoft Dynamics AX database. We highly recommend that you use proxy classes for .NET interop for interaction with tables in Microsoft Dynamics AX. For more information about proxy classes, see /en-us/library/gg879799.aspx.If you use proxy classes to interact with the Microsoft Dynamics AX database, consider using LINQ to Microsoft Dynamics AX to build and run queries. For more information about LINQ to Microsoft Dynamics AX, see/en-us/library/jj677293.aspx.Out of the box, the TMS managed system provides access to interaction with some of the TMS-specific tables by using proxy classes for .NET interop and LINQ to Microsoft Dynamics AX. You can use theMicrosoft.Dynamics.Ax.Tms.Data.AXDataRepository class to retrieve IQueryable objects for these tables.•Using the common engine data infrastructure– All the engines that are shipped out of the box with AX 2012 R3 require Microsoft Dynamics AX data in order to do the actual calculations. To reduce the cost of building engines that must source data from Microsoft Dynamics AX, the TMS system includes an implementation of a common engine data infrastructure. This feature enables the recording of engine-specific data, without the need to add new Microsoft Dynamics AX tables and build additional Microsoft Dynamics AX forms to maintain data. For more information about how to set up engine metadata, see “Transportation management engines” and “Set uptransportation management engines” under Rating setup in online Help.The TMS system defines a number of tables and Microsoft Dynamics AX forms that enable the recording of engine-specific data. This data is stored in physical table records that contain a number of generic table fields that can be reused for different purposes, depending on the specific engine implementation. For proper UI interpretation of data at runtime, metadata is recorded. For each group of data records that are used by a particular engine, a number of metadata records are required. These metadata records describe the caption, data type, lookup type, and a few other properties for each generic field that the engine is using.Use the following table to find the Microsoft Dynamics AX table that contains data and metadata for a particular type of engine.Send feedback.Microsoft Dynamics is a line of integrated, adaptable business management solutions that enables you and your people to make business decisions with greater confidence. Microsoft Dynamics works like and with familiar Microsoft software, automating and streamlining financial, customer relationship, and supply chain processes in a way that helps you drive business success. United States and Canada toll free: (888) 477-7989Worldwide: (1) (701) 281-6500/dynamics。
AX2012工具AxUtil
AX2012命令行工具AxUtil AXUtil 6.0农民锅AXUtil 6.0 - Microsoft Dynamics AX Admin Utility (6.0.947.0)(c) Copyright, Microsoft Corporation, 2011. All rights reserved.Example: axutil export /model:Test /config:DynamicsAx1:CoreDevelopment (5)Example: axutil exists /model:Test /db:axmodelstore /server:axserver (5)Example: axutil delete /layer:var /db:axmodelstore /server:axserver (5)Example: axutil import /file:newname /replace:oldname (6)Example: axutil set /noInstallMode (7)Example: axutil import /file:test.axmodel /db:axmodelstore (7)Example: axutil schema /aosaccount:"NT AUTHORITY\NETWORK SERVICE" /db:ax (7)Example: axutil create /model:Test /manifest:Version="1.0.0.0" (7)Example: axutil importstore /file:new /schemaname:TransferSchema (8)Example: axutil importstore /file:new /backupschema:dbo_backup (8)Example: axutil schema /drop:dbo_backup. (9)Example: axutil importstore /apply:TransferSchema (9)Example: axutil view /file:test.axmodel /verbose (9)Usage: AXUtil.exe command command-parameter <model-store> Supported commands:export - Export a model to an .axmodel file.import - Import a model from an .axmodel file.delete - Delete one or more models in a layer.create - Create a new blank model.move - Move a model to another same-layer model.view - View the content of a model or an .axmodel file.edit - Edit the model manifest properties of a model in the model store.list - Display a list of models in the model store.exists - Verify if one or more models in a layer contains model elements. schema - Create or update the model store schema.optimize - Optimize the model store for runtime performance.manifest - Retrieve the manifest for a model, model file, or template.set - Set model store settings.grant - Set permissions for creating model store schema.exportstore - Export the model store to an .axmodelstore file.importstore - Import the model store from an .axmodelstore file.genLicense - Generate a license file.Supported command-parameters:axutil export {/model:<model> | @modelxml} /file:filename [/key:SNK-file] axutil import /file:filename{,filename}[/conflict:{reject|push|overwrite} [/targetlayer:name]][/replace:<model>{,<model>}] [/createparents][/verbose] [/noOptimize] [/noPrompt]axutil delete {/model:<model> | @modelxml | /layer:name}[/noPrompt] [/verbose]axutil create {/model:<model> /layer:name <manifest>} | @modelxmlaxutil move {/model:<model> | @modelxml /targetModel:<model>}axutil view {/model:<model> | @modelxml | /file:filename} [/verbose]axutil edit {/model:<model> | @modelxml} <manifest>axutil list [{/model:<model> | @modelxml}] [/layer:name] [/verbose]axutil exists {/model:<model> | @modelxml | /layer:name}axutil manifest [/model:<model> | /file:filename] [/xml]axutil set {/installmode | /noinstallmode}axutil schema [/aosaccount:account] [ [/schemaname:name] | [/drop:name] ] [noprompt]axutil optimizeaxutil grant /aosaccount:account [/schemaname:name]axutil exportstore /file:filename [/verbose]axutil importstore {/file:filename [/idconflict:{reject|overwrite}][[/schemaname:name] | [/backupschema:name]]| /apply:schemaname [/backupschema:name] }[/verbose] [/noPrompt]axutil genlicense /file:licensefile /certificatepath:filepath/licensecode:name /customer:name/serialnumber:number /password:value [/expirationdate:date][/usercount:count]where<model-store> = [/db:database] [/s:server] | [/config[[:aosinstance]:name]<model> = model-name | '(' model-name , publisher ')' | model-id<manifest> = {@modelxml | /manifest:<property>=<value>}Parameters:/db:databaseSpecifies the database name for the model store on the server.The database must exist before the connection. It cannot be used withthe /config parameter. Default: tempdb.If no <model-store> parameters are used at all, /config is the default./s:serverSpecifies the server name for the model store database.This parameter cannot be used with /config parameter. Default: "(local)".If no <model-store> parameters are used at all, /config is the default./config[[:aosinstance]:name]Specifies an Application Object Server (AOS) configuration to use todetermine the model store database and server name. The default for AOSinstance is the name of the "01" AOS instance on the local computer. Thedefault for name is the name of the current configuration on the specifiedinstance. This parameter cannot be used with the /db or /s parameters. Ifno <model-store> parameters are supplied, /config is used by default.Example: axutil export /model:Test /config:DynamicsAx1:CoreDevelopment/noPromptDo not prompt for confirmation before completing the selected command.Default: Do prompt./model:{model-name | '(' model-name , publisher')' | model-id}Specifies one model in the model store. The model can be identified by:* Name - name that uniquely identifies exactly one model in the store.* Two-part unique name - values must be contained in parentheses,and comma separated.* ID - the model store specific number which can be found using thelist command.Example: axutil exists /model:Test /db:axmodelstore /server:axserver/layer:nameSpecifies one of the 16 supported layers.Example: axutil delete /layer:var /db:axmodelstore /server:axserver/conflict:{reject|push|overwrite}Specifies the action to take on import when a model element existsin the destination model.* Reject stops the import process.* Push duplicates the model element into the next higher layer.* Overwrite replaces the existing model element with the imported modelelement.Default: /conflict:reject./idconflict:{reject|overwrite}Specifies the action to take on importstore when a model element existsin the destination model store with the same origin but different ID.* Reject stops the import process.* Overwrite replaces the existing model element with the imported modelelement.Default: /idconflict:reject./targetlayer:nameUsed with the import command and /conflict:push parameter. Specifieswhich of the 16 supported layers to create a conflict model in./targetmodel:nameUsed with move command for moving the content from one model to thetarget model./replace:<model>{,<model>}Specifies one or more models to be physically replaced by imported model.Example: axutil import /file:newname /replace:oldname/createparentsUsed with the import command to create parents. If a child-element isimported, but its parent element is not in the model store, a fake parentis created in the model store. Default: Off./noOptimizeWhen used with the import command, the program will not optimize the model store automatically for optimal runtime performance.Default: Additional optimization actions done./noInstallMode, /installmodeImpacts the model store install mode, which, if set, triggers a promptinside Microsoft Dynamics AX to complete certain actions. Notice thatimport, delete and move commands implicitly set the install mode.Example: axutil set /noInstallMode/file:filename{,filename}Specifies the name of the .axmodel file or .axmodelstore file.Example: axutil import /file:test.axmodel /db:axmodelstore/aosaccount:accountSpecifies the AOS account used to set permissions for the modelstore and stored procedures. Use this parameter only with grant and schemacommands.Example: axutil schema /aosaccount:"NT AUTHORITY\NETWORK SERVICE" /db:ax@modelxmlSpecifies the name of a model XML file that follows the appropriateschema, and contains the manifest properties of a model. The schema ofthe file must follow the documented schema. Use axutil manifest /xml tooutput a sample manifest./manifest:<property>=<value>Specifies a model manifest property setting. Any value described in themodel XML file schema can be used with valid values. For more than oneproperty consider using the @modelxml variant.Example: axutil create /model:Test /manifest:Version="1.0.0.0"/key:SNK-fileSpecifies a key file generated with the Strong Name utility. The modelfile will be delay signed if the key file only contains a public key./file:licensefileSpecifies the name of the generated license file./certificatepath:filepathSpecifies the path to the certificate used to generate the license file./licensecode:nameSpecifies the name of the licencode code used to generate the license file./customer:nameSpecifies the customer name used to generate the license file./serialnumber:numberSpecifies the serial number used to generate the license file./password:valueThe value of this parameter must match the password of the givencertificate when generating a license file./expirationdate:dateSpecifies expiration date of the generated license.This parameter is optional./usercount:countSpecifies the number of simultaneous users for the the generated license.This parameter is optional./schemaname:nameSpecifies a valid SQL schema name. Default: dbo.Example: axutil importstore /file:new /schemaname:TransferSchema/backupschema:nameSpecifies a valid SQL schema name and is used to backup dboschema if provided.Example: axutil importstore /file:new /backupschema:dbo_backup/drop:nameUsed with the schema command to drop a backup schema that is populated by the importstore command. The schema must be a valid existing schema and cannot be [dbo].Example: axutil schema /drop:dbo_backup./apply:schemanameUsed with importstore command to apply a new model store alreadyimported in a staging schema.Example: axutil importstore /apply:TransferSchema/verboseSpecifies that extended information be output. Default: Non-verbose.Example: axutil view /file:test.axmodel /verbose/?Displays help for all parameters.References：Help of AXUtil 6.0。
AX2012产品功能介绍
图 3：根据财务维度部门轻松创建组织层次结构，以便从不同角度查看您 的企业并进行报告。
模块 角色中心 总帐 银行管理
描述
会计、会计经理、应付帐款协调员、应收帐款管理员、记帐员、首席执行官 (CEO)、首席财务官 (CFO) 、财务主管、出纳员、预算经理、环境经理、信用和收款经理。
财务会计记录管理，具备配置多栏式日记帐和经常性日记帐、成本和收入分配以及支持创建平仓交易 （包括准备平仓前单据和平仓簿记）的功能。使用无限财务维度和高级会计结构和规则获得洞察。
固定资产 管理从获得到贬值再到转移/处置的整个资产会计生命周期。
成本会计 跟踪、记录和分析与产品或活动（包括正常、吸收和标准成本法）相关的成本。
Microsoft Dynamics AX 2012
产品概述
6
Microsoft Dynamics AX 2012
概述：Industry and Core ERP Capabilities
Microsoft Dynamics® AX 2012 是 是一种 Microsoft 企业资源规划解决方案，企业可采 用它来让员工预见并迎接变革，从而实现企业的蓬勃 发展。它支持组织内的所有人访问关键业务信息和流 程，提高了员工的生产力并增加了信息的价值。 Microsoft Dynamics AX 2012 在一个全球解决方案中 包含了丰富的行业和核心 ERP 功能，缩短了实现价值 的时间。它简单易用，为您提供了扩展业务机会、修 改流程并让自己的企业与众不同所需的灵活性。凭借 广泛的互操作性，您可利用已有的投资，节省总体拥 有成本 (TCO) 并支持组织内的创新。
根据职位描述分析技能（差距）并搜索技能（包括技能筛选和权重）。 设立、提供和分析培训课程。
[AX]AX2012帮助服务
![[AX]AX2012帮助服务](https://img.taocdn.com/s3/m/e00647771fd9ad51f01dc281e53a580216fc5010.png)
[AX]AX2012帮助服务在AX2012使⽤F1快捷键获取上下⽂帮助时需要有安装Help server，Help server是⼀个web服务，部署在IIS站点上，web服务URL记录在Systemadministration>Setup>System>Help system parameters>Help service URL。
需要注意的是Help server不能和Sharepoint 2010运⾏在同⼀个站点上，所以你可能需要创建⼀个单独端⼝的IIS站点宿主Help server站点。
在Client程序中F1时Client查找到帮助服务web service url后调⽤Help view程序中查看，Help view随Client程序⼀起安装。
帮助Web服务默认安装在C:\inetpub\wwwroot\DynamicsAX6HelpServer，帮助内容相关的⽂件在C:\inetpub\wwwroot\DynamicsAX6HelpServer\Content可以找到，在Help view中左边的树形列表来⾃于content⽬录下TableOfContents.xml⽂件中定义的主题页⾯链接，右边内容则是来⾃于content⽬录下众多HTML⽂件。
编写帮助⽂件我们可以创建新的帮助⽂件，也可以修改已有的html帮助⽂件。
html帮助⽂件必须遵循⼀些固定的格式，⼀个典型的⽂件类似这样：<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "/TR/xhtml1/DTD/xhtml1-transitional.dtd"[]><html dir="LTR" xmlns:xlink="/1999/xlink" xmlns:dynHelp="/dynamicsHelp/2008/11" xmlns:dynHelpAx="/dynamicsHelpAx/2008/11" xmlns:MSHelp="http://msdn.micro <head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/><meta NAME="save" content="history"/><title>temp testing </title><link rel="stylesheet" type="text/css" href="../local/presentation.css"/><link rel="stylesheet" type="text/css" href="../local/AX.css"/><script type="text/javascript" src="../local/EventUtilities.js"></script><script type="text/javascript" src="../local/Dropdown.js"></script><script type="text/javascript" src="../local/script_manifold.js"></script><script type="text/javascript" src="../local/script_feedBack.js"></script><script type="text/javascript" src="../local/CheckboxMenu.js"></script><script type="text/javascript" src="../local/CommonUtilities.js"></script><meta name="Title" content="temp testing"/><meta name="Microsoft.Help.Id" content="D88E71BE-19A0-41F8-91C1-75F7675097AB"/><meta name="ms.locale" content="EN-US"/><meta name="publisher" content="Contoso"/><meta name="documentSets" content="UserDocumentation"/><meta name="Microsoft.Help.Keywords" content=""/><meta name="suppressedPublishers" content=""/><meta name="Microsoft.Help.F1" content="Forms.CustTable"/><meta name="description" content="Insert introduction here. "/></head><body><input type="hidden" id="userDataCache" class="userDataStyle"/><input type="hidden" id="hiddenScrollOffset"/><img id="collapseImage" style="display:none; height:0; width:0;" src="../local/collapse_all.gif" alt="" title=""/><img id="expandImage" style="display:none; height:0; width:0;" src="../local/expand_all.gif" alt="" title=""/><img id="collapseAllImage" style="display:none; height:0; width:0;" src="../local/collapse_all.gif"/><img id="expandAllImage" style="display:none; height:0; width:0;" src="../local/expand_all.gif"/><img id="dropDownImage" style="display:none; height:0; width:0;" src="../local/dropdown.gif"/><img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="../local/dropdownHover.gif"/><img id="copyImage" style="display:none; height:0; width:0;" src="../local/copycode.gif" alt="" title=""/><img id="copyHoverImage" style="display:none; height:0; width:0;" src="../local/copycodeHighlight.gif" alt="" title=""/><div id="header"><table id="topTable"><tr><td><span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage, event)" tabindex="0"><img ID="toggleAllImage" class="toggleAll" src="../local/collapse_all.gif"/><label id="collapseAllLabel" for="toggleAllImage" style="display: none;">Hide all</label><label id="expandAllLabel" for="toggleAllImage" style="display: none;</td></tr></table><table id="bottomTable"><tr id="headerTableRow1"><td align="left"><span id="runningHeaderText"/></td></tr><tr id="headerTableRow2"><td align="left"><span id="nsrTitle">temp testing </span></td></tr></table><hr class="title-divider"/></div><div id="mainSection"><div id="mainBody"><div id="allHistory" class="saveHistory" onsave="saveAll()" onload="loadAll()"/><div class="introduction"><p>Insert introduction here.</p></div><h1 class="heading"><span onclick="ExpandCollapse(sectionToggle0)" style="cursor:default;" onkeypress="ExpandCollapse_CheckKey(sectionToggle0, event)" tabindex="0"><img id="sectionToggle0" class="toggle" name="toggleSwitch" src="../local/collapse_all.gif"/>Section Heading</span></h1><div id="sectionSection0" class="section" name="collapseableSection" style=""><p>Insert section body here.</p><h3 class="subHeading">Subsection Heading</h3><div class="subsection"><p>Insert subsection body here.</p></div></div></div><div id="footer"><div class="footerLine"><img width="100%" height="3px" src="../local/footer.gif" alt="" title=""/></div><p /><p class="build-date">Build date: 2011-06-08 [13:05]</p></div></div></body></html>第⼀⾏和第⼆⾏原封不动的拷贝就⾏了，需要注意的是“<html”开始的第⼆⾏，必须完整的添加xmlns引⼊的多个命名空间，在测试中发现这些内容必须在⼀⾏上，中间不能有换⾏，否则帮助服务⽆法解析此⽂件。
AX2012产品整体新增功能q
《农民锅文集》
Table 可继承
配置禁用的 table 仍然在 DB 中保留
集成在线销售，在线商店
授权，结算，退款，地址验证，Level 2 and 3 processing，在线付款结 算 导航更直观， 列表页面界面改进，自动刷新数据 筛选功能，跨字段筛选，筛选所有字段 先进的审计披露表格， 表单界面改进 搜索数据，附件... 升级指导 升级框架 升级后数据验证 简化管理和配置：可以使用费 XML 格式文件，新增集成端口配置，简化配置 AIF：直接使用系统服务获取信息，支持 WCF 弃用 MSMQ,BizTalk，加入 SOAP headers,简化数据库接口，服务分组，X++容器和 X++Collections，business operations framework 部署：WCF 在 AOS，Services 在 IIS，单一 WSDL 对所有文档服务，IIS 管理多 站点，AOS 和 IIS 网络负载均衡 安全/隐私：WCF 管理服务权限 故障检查：集成端口层检查，支持大数据量操作时多服务操作故障检查 导入导出：大数据量导入导出 基础：简化安装配置，通过客户端或 AxUpdatePortal 工具部署到 web Server，更多域用户验证模式，客户端管理远程 EP，增强页面主题 财务角色中心 搜索 用户界面：快速筛选，快速完成常用任务，预览重要相关信息，增强列表数 2|Page
维度转移规则预算转移分摊和循环的简化预算报表和查询强化webservice接口xml格式导入第三方预算的结果ledgersubledgerlinesdistributions账目子账目和分摊过账前预览凭证分摊模板用于财务维度值非主科目按金额百分比数量或均分来分摊按原文档类型批处理分摊原文档记录产生时立即分摊采购申请分摊定义自动用于以后流程的分摊支持公司间交易支持项目管理可以基于分摊信息来进行预算控制的验证和预留预算taxes税率支持5位小数过账前保存税值信息
saber2012安装教程
saber2012安装教程Saber2012具体安装步骤本安装步骤是在win732位电脑上进行演示：1.务必注意：安装前关闭杀毒软件、安全卫士、鲁大师、QQ电脑管家和断开电脑网络2．右击Windows文件下的“install”应用程序（win7系统以管理员身份运行）3．点击Next4．默认安装路径：C:\Synopsys\Saber\H-2012.12，点击Next5．勾选上Component Library，点击Next6.点击Install7.接下来就是漫长的安装过程…….8.点击No.9.点击Done.Saber2012破解步骤破解之前，请确保网络已断开且杀毒软件、安全卫士、QQ管家、鲁大师等已退出1、破解文件在license文件夹中，将整个license文件夹复制到C 盘2、运行license\Synopsys SSS Feature Keygen文件夹中KeyGen.exeHOSTID中其余的删除，只保留前12位数字字母，如：0026c789731d得到HOSTID0026c789731d将0026c789731d这串数字复制…（备注：每台电脑的HOSTID 均不同）3、运行EFA LicGen0.4b目录内LicGen.exe按打开…\EFA LicGen0.4b\packs\Synopsys.lpd文件点选Custom项，并将第2步得到的HOSTID粘贴到文本框内点击点击保存为synopsys.dat到sssverify.exe所在目录【备用】4、运行cmd：开始>搜索栏输入cmd，回车出现DOS窗口A.输入C:，按回车(C:是sssverify.exe所在盘符，根据你license 文件实际位置而定)B.输入sssverify.exe文件的所在路径,输入CD C:\license\Synopsys SSS Feature Keygen，按回车；（也可将路径复制，然后先输入CD，空格1个，再右击粘贴路径，这样就不用打字了）C.输入sssverify synopsys.dat，按回车得到SECRET DATA：00f4000084d600008d005、再次运行KeyGen.exe，将之前得到的HOSTID和上一步得到的SECRET DATA输入点击会在KeyGen.exe所在文件下生成一个License.dat文件，如图：此文件内synopsys.dat和license.dat就是我们需要的6、用记事本打开上述两个文件将license.dat的这部分（最尾部分）复制后追加到synopsys.dat的最尾部分然后保存synopsys.dat(最终注册文件)，拷贝synopsys.dat到C:\Synopsys文件夹下7、最后一步WIN7系统：右击桌面上计算机图标→属性→高级系统设置→高级→环境变量→新建<用户变量>变量名：LM_LICENSE_FILE变量值：C:\Synopsys\synopsys.dat(为synopsys.dat保存位置)点击《确定》点击《确定》这样就OK了………注意:有防火墙的要放行：Aim.exet和aimsh.exe访问网络，否则不能启动…。
Saber_H-2012.12 安装激活详细步骤
Saber_H-2012.12安装激活详细步骤1.双击Saber_H-2012.12安装软件。
注：exe后缀是自解压文件，如果在你电脑不能自解压安装包一般是文件路径放得太深或是有中文路径造成，还有就是跟操作系统有关系。
如果实在自解压不了就手动解压吧！解压文件相信这个人人都会用winrar和好压等工具。
下面是两种解压方式和进入安装界面截图。
2.等待出现以下界面时点NEXT。
3.再点NEXT。
4.更改好自己需要安装的路径，点NEXT。
安装路径不可含有中文！5.选择需要的组件，点击NEXT。
一般默认即可。
6.确认安装路径和硬盘剩余空间是否足够，点击NEXT。
7.等待安装过程。
8.如果提示安装C++等，只需按提示NEXT即可。
9.选择I have，点Install,最后点Finish。
10.继续安装中。
11.出现以下界面点“NO”就可以了。
12.再Done,结束软件安装。
到此软件已经安装完成，后面是破解。
以下是破解步骤，实际上前面的步骤过于啰嗦，主要是考虑到初次安杀毒软件进行的，Vista/win7/8用户记得要以管理员方式运行文件。
注：我的破解是放在E:\ saber2012crack 目录。
a. 双击E:\saber2012crack\Keygen文件夹中的KeyGen.exe生成 HOSTID号码，注意保存好这一个号码。
装和学习软件的人，所以算是做个傻瓜教程吧。
破解软件是需要关掉b.使用E:\saber2012crack目录下的Synopsys.src替换E:\saber2012crack\EFA LicGen 0.4b\packs目录下的Synopsys.src。
c.运行E:\saber2012crack\EFA LicGen 0.4b目录下的LicGen.exe，生成synopsys.dat。
1.点击Open打E:\saber2012crack\EFALicGen0.4b\packs\Synopsys.lpd2. 在Select Host ID中选择 Ethemet选项，会自动出现计算机的host ID号码，注意要与第一步产生的HOSTID号码对比，看是否相同，理论上是相同的。
DynamicsAX2012R2安装ReportingServices扩展
DynamicsAX2012R2安装ReportingServices扩展123今天在VS中部署SSRS报表时，接到以下错误：部署因错误⽽被取消。
在报表服务器上，验证：-SQL Server Reporting Services 服务是否正在运⾏。
接着，进⼊到AX中，检查系统的报表服务器配置是否正确。
不知道怎么配置的同学可以查看之前的博⽂。
检查发现，报表服务器中的配置也正确。
点击了⼀下验证设置按钮，收到以下错误：124根据错误提⽰，进⼊到报表服务器，检查SSRS服务是否启动。
检查发现，报表服务没有启动。
将其启动后，再次点击验证设置按钮，⼜收到以下错误：判断，报表服务器上很有可能没有安装AX的 Reporting Services 扩展。
到服务器上检查了下，果然没有装。
接着， Reinhard就开始安装126该扩展吧。
点击下⼀步，进⼊必备项验证，验证通过后继续下⼀步，⼜收到以下错误：这是因为的AOS和报表服务器不在⼀台服务器上，并且报表服务器的BC没有指向AOS所在服务器。
进⼊到AX配置实⽤程序，将BC指向AOS所在服务器。
128修改完记得点击应⽤按钮。
重新回到AX组件安装程序，继续安装，录⼊BC账号的密码，进⼊下⼀步。
选择本机的数据库实例，记得把部署报表的CheckBox选中，点击下⼀步。
这⾥我们选择AX的数据库服务器的名称，和数据库名称。
这⾥Reinhard收到以下错误：129安装程序⽆法连接到数据库服务器“MSDynAX”。
猜测可能是BC账户没有AX数据库的权限。
检查后，发现BC账户的权限没有问题。
那究竟问题出在哪⾥呢？Reinhard突然想到刚刚只是将BC指向了AOS，没有将本地客户端指向AOS。
重新运⾏AX配置⼯具，将本地客户端指向AOS，应⽤设置。
接着，重新运⾏AX组件安装⼯具，这次可以获取到AX数据服务器的数据库名称了。
点击下⼀步，必备项检查完毕。
Image(2)接着点击下⼀步，开始安装。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Dynamics AX2012安装，是在煎熬AX2009实践后的心血来潮，看到一群人才研究AX2012的业务和技术，心里充满着无尽的好奇感，于是乎找到AX2012 R2+demo data+license 开始漫长的安装之旅...
一.安装环境
Windows 2008 R2(AD)+SQL 2008 R2(DB)+IIS7+Office2007/2013+VS2008/2010,然后就是打完一大堆补丁。
检测环境，结果如下。
选择自定义安装组件
点validate,获取环境检测的结果
接下来，就开始安装一大堆垃圾，抱怨呀！微软怎么不会一步到位，免去用户的烦恼....
下载地址可以到这里获取: AX2012环境验证前需选择安装项目检验通过后，开始安装AX2012吧
点下一步
点下一步
点下一步继续
点下一步
点下一步
点下一步
一步一步往下走
点下一步，系统开始安装，进度条像蜗牛一样爬行..............
终于安装完成了，现在开始配置AX2012。
开始->所有程序->ax2012 server配置
先apply然后点OK。