Reply To: Upgrading a Retail system in MS Dynamics AX

#20969

Locus IT
Participant

Hello Lee,

The upgrade process for Retail installations of Microsoft Dynamics AX 2012 is based on the Microsoft Dynamics AX 2012 upgrade framework, and uses procedures that are common to both Retail and non-Retail deployments.

Steps:

1. Supported Retail upgrade paths
Retail upgrade paths are a subset of general Microsoft Dynamics AX 2012 upgrade paths.
The terms source and target refer to stages of the AX 2012 upgrade framework. The goal of the upgrade framework is to reduce the downtime that is required during code and data upgrade. Upgrade administrators and business application experts can prepare data upgrade fixes on the existing production system, or source system, without interrupting business operations.
While this work is in progress, the AX 2012 system, or target system, is installed and configured on a separate computer. Code upgrade is performed on the target system while that system is still offline. Finally, during a relatively brief downtime window, prepared data is copied from the source system and upgraded on the target system.The term in-place describes upgrades that take place on a single computer system. Upgrades between subreleases of AX 2012 use an in-place upgrade model.

2. Retail upgrade cases
Each of the following cases provides a simplified workflow of the phases that are involved in the upgrade of a Microsoft Dynamics AX Retail system. Only one of these cases will apply to your own upgrade.

Case 1: Upgrade AX 2009 for Retail (R2 Refresh) to AX 2012 Feature Pack
The AX 2012 source-to-target upgrade model defines the phases of a Retail module upgrade from AX 2009 for Retail (R2 Refresh).

Case 2: Upgrade AX 2009 for Retail (R2 Refresh) to AX 2012 R2 or AX 2012 R3
The Microsoft Dynamics AX 2012 source-to-target upgrade model defines the phases of a Retail module upgrade from Microsoft Dynamics AX 2009 for Retail (R2 Refresh).

AX 2012 R2 and AX 2012 R3 support up to two versions of POS software across multiple stores. Therefore, administrators have the flexibility to upgrade one store at a time instead of all stores at one time. For information about how to configure the Retail module for multiversion POS installations, see the appropriate section later in this topic, either “Deploy Retail POS for AX 2012 R2 or AX 2012 Feature Pack” or “Deploy Retail POS for AX 2012 R3.”

Case 3: Upgrade AX 2012 to AX 2012 Feature Pack
The upgrade installs a new model, OneFPK, onto the existing system to supply the framework and applications that support Retail functionality.

Case 4: Upgrade AX 2012 to AX 2012 R2 or AX 2012 R3
AX 2012 R2 and AX 2012 R3 support up to two versions of POS software across multiple stores. Therefore, administrators have the flexibility to upgrade one store at a time instead of all stores at one time.

Case 5: Upgrade AX 2012 Feature Pack to AX 2012 R2 or AX 2012 R3
AX 2012 R2 and AX 2012 R3 support up to two versions of POS software across multiple stores. Therefore, administrators have the flexibility to upgrade one store at a time instead of all stores at once.

Case 6: Upgrade AX 2012 R2 to AX 2012 R3
AX 2012 R3 supports up to two versions of POS software across multiple stores. Therefore, administrators have the flexibility to upgrade one store at a time instead of all stores at one time.

Deploy POS registers when upgrading to AX 2012 R3
Starting with AX 2012 Feature Pack, there is no longer an in-store upgrade process for Retail POS. Instead, you must uninstall the previous version, back up the Retail POS database, and then install AX 2012 R3 Retail POS and create a new database.

1. Configure AX 2012 R3 to support AX 2009 registers
AX 2012 R3 makes several changes to the configuration of data distribution to enable support for previous POS register versions.

2. Distribution location
In AX 2009 for Retail (R2 Refresh), the recommended configuration was to have one database for each register. This configuration is no longer supported, and instead one store database supports all registers in a store.

3. Scheduler jobs
All Retail installations of Microsoft Dynamics AX use scheduler jobs to define the data mapping between the headquarters Microsoft Dynamics AX database and Retail POS tables.

4. Configure AX 2012 R3 to support AX 2012 Feature Pack registers
After the headquarters system has been upgraded to AX 2012 R3, apply the following settings to support use of AX 2012 Feature Pack POS registers in some stores and AX 2012 R3 POS registers in others.

5. Configure AX 2012 R3 to support AX 2012 R2 registers
After the headquarters system has been upgraded to Microsoft Dynamics AX 2012 R3, apply the following settings to support use of Microsoft Dynamics AX 2012 R2 POS registers in some stores and Microsoft Dynamics AX 2012 R3 POS registers in others.

Deploy POS registers when upgrading to AX 2012 R2 or AX 2012 Feature Pack
Complete the Retail POS redeployment checklist

Skip to toolbar