Upgrading a Retail system in MS Dynamics AX

This topic contains 2 replies, has 3 voices, and was last updated by  Locus IT 2 months, 3 weeks ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #20621

    Lee Min
    Participant

    I need to know the process for upgrading a Retail system in MS Dynamics AX. If anyone knows the process, please help me out. Anything would be appreciated. Thank you.

    #20636

    Anne Smith
    Participant

    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. Before administrators attempt an upgrade, they must be familiar with the Microsoft Dynamics AX 2012 Upgrade Guide and the regularly updated upgrade documentation on TechNet.

    Retail upgrade paths are a subset of general Microsoft Dynamics AX 2012 upgrade paths. Microsoft Dynamics AX supports several direct upgrade paths for Retail customers who want to upgrade to Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, or Microsoft Dynamics AX 2012 Feature Pack from previous versions.

    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.

    Upgrade-related deployment of POS registers differs in one respect from other deployments: You will probably want to set seed values for receipts at existing stores in order to maintain sequential receipt numbers. To do this, open the Retail POS redeployment form at Retail > Periodic > Retail POS redeployment and specify the appropriate seed values.

    To download all required data to an upgraded store, run a full data sync for the store’s channel database. Open the Channel database form at Retail > Setup > Retail scheduler > Channel integration > Channel database. On the Action Pane, click Full data sync and select distribution schedule 9999.

    Support for multiple versions of Retail POS
    A retail upgrade to AX 2012 Feature Pack required you to upgrade all of your POS register across all of your stores immediately after upgrading the Microsoft Dynamics AX headquarters system. Otherwise data connectivity with the registers would be lost when Microsoft Dynamics AX was stopped for upgrade, and any sales transactions processed after the start of the upgrade had to be manually imported for posting. AX 2012 R2 introduced new functionality that let a previous register version communicate with AX 2012 R2 after the upgrade. This functionality has been enhanced in AX 2012 R3 to support all of the earlier register versions:

    1. AX 2009 for Retail (R2 Refresh)

    2. AX 2012 Feature Pack

    3. AX 2012 R2

    Previous-version support depends on the following prerequisites:

    1. The Foundation upgrade model must be installed.

    2. The Keep update objects license configuration key for the appropriate version must be enabled.

    3. The Keep retail objects license configuration key must be enabled.

    4. The Retail Commerce Data Exchange backward compatibility license configuration key must be enabled.

    #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

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Skip to toolbar