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 you to insert data on Newly created store database by generating a script of cfgaddon Table from Enterprise database
Recommendations /Suggestion:
Suggested the customer to apply the latest patch available on portal. Asked him to after apply the patch on a test system and check functionality to prevent any issue on production.
Related Articles
Unable to Start iVend Add-on in SAP Business One
Environment: iVend Retail 6.6 7989 & SAP Business One 10.0 Problem statement: Unable to start iVend Add-on in SAP Business One Error:Access to the path 'C:\Program Files\SAP\SAP Business One\AddOns\CXS\CitiXsys iVend AddOn\CitiXsys Ivend AddOn.exe' ...
Newly configured store not seen in replication monitor
Product version: 6.5 Onward Problem Statement: Configured new store in iVend. Now this newly configured store is not seen in the replication monitor at Enterprise. Proposed Solution: In the store configuration, there is option ‘Is On Premise’, please ...
Replication stuck and Not Moving
Problem: Replication not moving from HO to Specific Store. Symptoms: Replication Log File Not generated and Event Viewer is showing "INVALID CLASS ERROR" What need to be Check : 1. Right Click on My PC 2. Click on Manage 3. Now Go to Services and ...
Newly created POS unable to login and showing error message 'Not a Valid License'
Environment : iVend Version 6.5 Update 4 With SAPB1 9.2 or Unplugged Problem Statement : Customer has informed that newly created POS unable to login and showing error message 'Not a Valid License. License has been tempered. Contact Vendor'. Symptoms ...
Replication not working
Environment: iVend 6.6 Problem Statement: Replication service not working due to controller application Error Screenshot: Solution: - This issue happened due to there’s an error showing from controller application when customer removed this ...