Dynamics AX2012: 1099 - Hotfix for Prepayments

An issue has been identified with Dynamics AX 2012 where the update 1099 process is incorrectly updating the TRANSDATE in the VENDSETTLEMENTAX1099 table on prepayments.  This will cause the vendors 1099 reportable amount to be understated.  A hotfix is available for this issue - KB 2820367. Access to partnersource/Customersource required.

Localization features in Dynamics AX

Localization features for different countries listed below including info on regulatory features, documentation, certifications, plus associated ISV solutions available on Partnersource/Customer source.

List of countries:
Australia, Austria, Belgium, Brazil, Canada, China, Czech Republic, Denmark, Eastern Europe, Estonia, Finland, France, Germany, Hungary, Iceland, India, Italy, Japan, Latvia, Lithuania, Malaysia, Mexico, Netherlands, New Zealand, Norway, Poland, Russia, Saudi Arabia, Singapore, Spain, Sweden, Switzerland, Thailand, United Kingdom, United States

Hot fixes released for AX 2012 R2

There is some good news for those struggling with the issue - User is not authorized to update a record in table 'VendTable'
This has been fixed in Hot fixes released for AX 2012 R2 on 15 Jan 2013.
Apart from fix for above issue, there are fixes for some other issues in areas like  Fixed Assets, General Ledger etc. Total 47 fixes in different areas were provided with maximum of 10 fixes for 'Client\Office Add-ins'.
For details refer link here.
Requires access to Partnersource/Customersource.

Product Area	Count
Client \ Office Add-ins	10
Financials \ Fixed Assets	3
Service Industries	3
China	3
India	3
SRM \ Purchase Requisition	2
Financials \ General Ledger	2
Public Sector \ GL \ Transactions	2
Expense Management	2
AIF	2
Public Sector \ AR \ Invoicing	1
AX Retail \ Headquarters	1
BI & Reporting	1
Global Address Book	1
Poland	1
APAC	1
Public Sector \ AR \ Reports	1
Financials \ Accounts Payable	1
Russian Federation	1
WEMEA	1
Manufacturing	1
Tax	1
Inventory Management	1
Client \ Forms	1
Inventory Management \ QMS	1
Grand Total	47

Microsoft Dynamics AX 2012 Product Guide

Download from here (requires login to Customersource/Partnersource).

This product overview is intended to convey a high-level understanding of the structure, key modules, features, and benefits of Microsoft Dynamics AX 2012 to readers that are not familiar with the product.

It highlights the value delivered to customers in our key industries including manufacturing, distribution, retail, services, and Public Sector.

It then details the horizontal application solutions including financials, human resources, supply chain management, and others. Finally, the solution describes the application foundation, system framework, and interoperability with the Microsoft productivity suite and application platform.

AX 2012 Upgrade - Troubleshooting errors

Troubleshooting steps for duplicate errors during the pre-processing phase of the Microsoft Dynamics AX 2012 upgrade process. 

The scenario being described is when one of the batch tasks has failed in the middle of the data being processed. The error message shown on the job in the Infolog would appear something like this:

Info Message (10:12:33) Run job inventJournalTransPreUpgradeProcess ordered by Admin in database XXX.

Error Message (10:12:33) Cannot create a record in Shadow_InventJournalTrans_Dimension (Shadow_InventJournalTrans_Dimension).

The record already exists.

Error Message (10:12:33) Script: ReleaseUpdateTransformDB40_Invent.inventJournalTransPreUpgradeProcess(xxx). Last control data: 00333331,1

For details on how to troubleshoot this error refer here. 

Upgrade Readiness Errors - Upgrade checks

Errors will show up when DAT company is not present. Details here.

Can be safely ignored

• validateMissingLedgerJournalName - Ledger journal name is missing (you will need to create one later on during data preparation if you skip this step here)
• projPostingPreValidate - Your Ax2009 system is missing some project ledger posting setup….(this error can be ignored only for companies not using the Project module)

Need to be addressed

• validateInventDimBlank - use the Fix button to easily create one
• Multi Site Activation errors - you will need to activate multi-site within the DAT and every company which means you will need to create a site and warehouse which can be removed later.
• validateDataAreaIds - Invalid DataAreaId found in some tables - this error is meant to let you know that there is data in a table with a DataAreaId of a specific company where the table should only show records from a virtual company. While it may not be necessary in all cases to clean this up, it would be in your best interest to address this now.
• validateCompanyInfo - There are company records without a name or country/region - the name and Country/Region ID are required values.

Any other messages that refer to invalid countries, missing LedgerTable or LedgerDimension records, etc. should always be addressed. 

Other Links:

Submit feedback to the author

Resource Page for Upgrading to Microsoft Dynamics AX 2012 (Requires login to Partnersource/Customersource)

Upgrade to AX 2012 on Technet

Upgrade to AX 2012 on MSDN

AX 2012 Cumulative Update 3

For main link on Microsoft website click here. 

Live id required for logging in to Partnersource/CustomerSource

Microsoft Dynamics AX 2012 Cumulative Update 3 release notes

Installation

Update database schema

In the following cases, we recommend that model database schema is updated to the latest version in model database instances to which Microsoft Dynamics AX 2012 Cumulative Update 3 has to be applied:

• The model database is customized.
• The environment is running SQL Server 2012
• The environment is running SQL Server 2008 without any customizations applied to avoid potential issues during update installation.

To update database schema, follow these steps:

1. Make sure that the Management Utilities component is installed by using Dynamics AX 2012 or Dynamics AX 2012 Feature Pack 1 installation package.
2. Apply the update to the Components item by using the Dynamics AX 2012 Cumulative Update 3 package.
   
   Important Note Do not apply database updates at this point.
3. Run the following command:
   
   axutil.exe schema /db:target model database name
   
   Note Axutil.exe is installed with the Dynamics AX 2012 Management Utilities to the C:\Program Files\Microsoft Dynamics AX\60\ManagementUtilities folder. You can start it by running the Administrative Tools control panel item and then clicking Microsoft Dynamics AX 2012 Management shell.
4. Apply Dynamics AX 2012 Cumulative Update 3 to the model database.

You receive SQL errors during compilation

Assume that you upgrade from Microsoft Dynamics AX 2012 or Microsoft Dynamics AX 2012 with Feature Pack 1 to Microsoft Dynamics AX 2012 Cumulative Update 3, or from Microsoft Dynamics AX 2012 Cumulative Update 2 or Microsoft Dynamics AX 2012 Cumulative Update 1 to Microsoft Dynamics AX 2012 Cumulative Update 3. After you apply the cumulative update, as a part of upgrade, you are prompted to run the software update checklist through the Model Store Modified form when you first start the client. You can also start the software update checklist directly. To do this, click System Administration, click Setup, click Checklists, and then click Software Update Checklist.When you perform compilation in the checklist, you receive the following error message that reports that update statement conflicts in the dbo.model table:

Cannot execute a stored procedure. The SQL database has issued an error.

 

To resolve this problem, follow these steps:

1. Restore a database backup of the environment.
2. Make sure that the Management Utilities component is installed by sing Dynamics AX 2012 or Dynamics AX 2012 Feature Pack 1 installation package.
3. Apply update to the Components item by using the Dynamics AX 2012 Cumulative Update 3 package.
   
   Important note Do not apply the application update at this point.
4. Run the following command:
   
   axutil.exe schema /db:target model database name
   Note Axutil.exe is installed with the Dynamics AX 2012 Management Utilities to the C:\Program Files\Microsoft Dynamics AX\60\ManagementUtilities folder. You can start it by running the Administrative Tools control panel item and then clicking Microsoft Dynamics AX 2012 Management shell.
5. Apply Microsoft Dynamics AX 2012 Cumulative Update 3 to the model database.

AX 2009 Client RU8 Silent Installation / Mass Deployment

Main link for RU8 - Description of hotfix rollup 8 for Microsoft Dynamics AX 2009 Service Pack 1

Mass Deployment steps are given in AX 2009 installation guide – page 37

Content From AX 2009 installation guide -  Page 37:

Mass deployment of clients

If you need to deploy a large number of clients, we recommend using the following process:

1. Copy the contents of the Microsoft Dynamics AX DVD to a shared directory on the network. For more information, see Copy the DVD contents to a file server.

2. Create a common configuration file in a shared directory on the AOS computer that clients will connect to.

3. Create a command (batch) file in a shared directory in the Microsoft Dynamics AX DVD shared folder, at the same level as Setup.exe.

4. Test the command file on a local computer. 5. Use a mass deployment tool such as Group Policy or Microsoft Systems Management Server to run the command file from a logon script.

For more information about using Group Policy to deploy software, see: http://go.microsoft.com/fwlink/?LinkId=92736.

For more information about using Systems Management Server to deploy software, see: http://go.microsoft.com/fwlink/?LinkId=115327.

The following procedures contain more detailed information about creating a shared configuration file and creating a command file.

Create a configuration file to share

By default, each client is installed with local configuration settings that specify which AOS to connect to. In a large deployment, we recommend creating a common configuration file in a shared directory instead. (The shared directory must always be available, or clients will be unable to start.) Using a single configuration file for multiple clients makes future configuration changes easier.

Note: You can set clients to use a shared configuration file only when you install the client from the command line. This option is not available through the Setup wizard. 1. On a client that has local configuration settings and is connected to the appropriate AOS instance, start the Microsoft Dynamics AX Configuration utility (Start > Control Panel > Administrative Tools > Microsoft Dynamics AX Configuration). 2. Verify that the settings in the configuration are those you want to distribute broadly. 3. Click Manage, and then click Export configuration to file. Name and save the configuration file. 4. Copy the saved configuration file to a shared directory. The user of each client computer must have read permissions on the shared directory.

Create a command file to install clients

This section describes how to create a command file to specify installation parameters to deploy a large number of clients.

Note:

Instead of entering all parameters directly in the command file, you can set up the command file to use a parameter file. For more information, see Silent installation. We recommend that you determine which parameters to use by installing a client on a single computer and then reviewing the Setup log file, which is located at %AllUsersProfile%\Microsoft\Dynamics AX\Dynamics AX Setup Logs\Date Time\ DynamicsSetupLog.txt. The log lists the parameters that were used in the installation.

For more information about individual parameters, see Setup parameters. 1. Create a command file named AxInstallClient.cmd in the Microsoft Dynamics AX DVD shared folder, at the same level as Setup.exe. 2. Specify installation parameters in the command file. Use the following example as a guide: X:\Setup.exe HideUI=1 AcceptLicenseTerms=1 InstallClientUI=1 ClientAosServer=Company1 ClientLanguage=en-US ClientHelpLanguages=en-US;fr-CA 3. Optional. To install clients without installing the Microsoft Dynamics AX Client Configuration utility, set the parameter ClientConfig to zero. 4. Optional. To set up clients to use a shared configuration file, set the ClientConfigFile path parameter to the file in the shared directory. ClientConfigFile="X:\.axc"

Other Links:

AX 2009 Client - Silent installation using AD

AX 2009 Client - Silent installation using batch file