Different iVend business date and system date

Different iVend business date and system date

Environment:

iVend 6.6 and 6.5 Update 6 with SAPB1

Problem Statement :

iVend MC screen displays the different business date and system date.


Symptoms:

Product Query

Resolution/Work Around:

The First date displays the business date and last date displays the system date. Once EOD done, business date will be changed while system date always remain the same as current date.




Recommendations /Suggestions :

Not Applicable

    • Related Articles

    • 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 ...

    • The Business Date is different than the System Date

      ******* Internal to CitiXsys ******* Environment: iVend 6.6 Problem Statement: Getting an error message "the Business Date is 02\15\2021 is different than the System Date 02\14\2021" when trying to login the POS before 11:00 am. However, the business ...

    • SAP Business One - iVend Retail Integration Points

      Introduction SAP Business One software is created specifically for small and midsized businesses. It is a powerful application and iVend Retail seamlessly integrates with it to help retailers better manage every aspect of their daily retail ...

    • Business date is different from System date.User not allowed to login, please contact manager

      Version: Not version-specific Issue: Not able to login to Point of Sale (POS), getting an error message "Business date is different from System date. User not allowed to login, please contact manager", below the screenshot of the error: Solution: ...

    • Business Date Different From System Date

      Article - Template Environment: iVend 6.5.6 Problem Statement: When tried to login in, the POS application was showing the below message. Symptoms: N/A Resolution/Work Around: Make sure the DB name should be corrected in the Connection Manager at ...