iVend Store Upgrade Challenges
******Internal to CitiXsys*******Product Query:
A Customer running iVend 6.5 update 5 with 40 + Stores across the region and they are planning to upgrade to 6.6.
The Customer has come up with the below plan :
1. Upgrade iVend enterprise to 6.6 at Enterprise and monitor for 2 business days.
2. Upgrade 2 stores to 6.6 per day.
3. I will need around 20 days to complete all branches.
With this plan Customer has come up with the below queries:
1. With the above planning, Will the Enterprise server running at 6.6 will be able to communicate with stores running on 6.5 ?
2. If not how replication from stores to Enterprise will be managed( Sales, payments & stock adjustment,…)?
3. How replications of master data from Enterprise to stores will be managed during 20 days of the upgrade?
Solution:
First of all it is highly recommended to carry out the product upgrade in the Test environment and run all Business-critical UAT cases.Once it succeeds then only go for a production system upgrade.
And as best practices, it is recommended to carry out the upgrade at Enterprise and stores at one go ( if feasible). In case it is not feasible then individual stores can be upgraded later also at the next available slot, however replication between the stores and Enterprise will resume only once both are upgraded to the same version.
Q: With the above planning, Will the Enterprise server running at 6.6 will be able to communicate with stores running on 6.5 ?
Response: No.
Q: If not, then how replication from stores to Enterprise will be managed( Sales, payments & stock adjustment,…)?
Response: In that scenario, Customer can individually work on Store servers, which means they can perform the transactions even HQ and Store are not in the same version. However, there will be no Replication movement between HQ and Store until Both HQ and Stores are not in the same version of 6.6.
All the posted transactions on the store will be in the Replication queue and once the Store will be upgraded to the same 6.6, records will automatically be replicated which are in the queue. the Records in the queue.
Q: How replications of master data from Enterprise to stores will be managed during 20 days of the upgrade?
Response: No Replication will happen until both Enterprise and Store are in the same version.
Related Articles
Addon information was not updated for newly created store
Environment: iVend 6.6 integrated with SAPB1 Problem Statement: Addon information was not updated for newly created store Symptoms: Not Applicable Resolution/Work Around: Issue is already fixed in the latest iVend patch (8567). As a workaround we ...Require to make the inventory as Zero for particular store
Environment: iVend 6.6 with SAP B1 10 Problem statement: Require to make the inventory as Zero for particular store. Symptoms: products Inventory show in negative and some are in positive numbers. Resolution/Work Around: There is need to check if SAP ...Upgrade iVend version from 6.5 to 6.6
Environment: 6.5.X Statement : Is there any guide to show how to upgrade the iVend version from 6.5 to 6.6, step by step? Resolution: iVend 6.6 is a quantum jump with various new technologies such as Quartz, Signal R, GZip MS IIS, SQL Servers, etc. ...General Settings in SAP Business One
Introduction The iVend Add-on helps in setting up some configurations required for integrating iVend with SAP Business One. The following sections of this document capture the functionality of the new screens created and new fields added to the SAP ...iVend Upgrade - Best Practices Overview
Purpose The purpose of this article is to introduce the CitiXsys iVend Partner community to an overview of the recommended steps to be followed while upgrading the iVend Retail applications in accordance with best practices. Best Practices The ...