Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0052517Retail ModulesWeb POSpublic2023-05-22 20:372023-05-24 08:13
Reporteraxelmercado 
Assigned Toranjith_qualiantech_com 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customerOBPS
Support ticket65049
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0052517: Problems when opening an order dated prior to the price list versions available
DescriptionWhen trying to open a POS ticket with a date prior to those available in the price list versions, the error shown in the attached image appears.
Steps To ReproduceIn livebuilds; https://livebuilds.openbravo.com/context/retail_mp_3.0RR23Q2. [^]

1-In backoffice, have a price list with valid date for example: 01-01-2023, you can modify the existing one.
2- In Web POS, try to open an old order.
3- Verify that the error is shown in the attached image.
Proposed SolutionFor older versions of livebuilds the error does not occur e.g.: https://livebuilds.openbravo.com/context/retail_mp_3.0RR22Q1.3 [^]
Additional Information
TagsNo tags attached.
Relationships
related to defect 0049603 closed radhakrishnan When pricelist version is empty, the paidreceipt has a null execption with no more info 
Attached Filespng pricelist version error.png (17,142) 2023-05-22 20:37
https://issues.openbravo.com/file_download.php?file_id=18554&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2023-05-22 20:37axelmercadoNew Issue
2023-05-22 20:37axelmercadoAssigned To => Retail
2023-05-22 20:37axelmercadoOBNetwork customer => OBPS
2023-05-22 20:37axelmercadoSupport ticket => 65049
2023-05-22 20:37axelmercadoTriggers an Emergency Pack => No
2023-05-22 20:37axelmercadoFile Added: pricelist version error.png
2023-05-22 20:40PracticsIssue Monitored: Practics
2023-05-23 07:15ranjith_qualiantech_comAssigned ToRetail => ranjith_qualiantech_com
2023-05-23 07:16ranjith_qualiantech_comStatusnew => scheduled
2023-05-23 08:38ranjith_qualiantech_comRelationship addedrelated to 0049603
2023-05-24 08:13marvintmReview Assigned To => marvintm
2023-05-24 08:13marvintmNote Added: 0150177
2023-05-24 08:13marvintmStatusscheduled => closed
2023-05-24 08:13marvintmResolutionopen => no change required
2023-05-24 08:14marvintmNote Edited: 0150177bug_revision_view_page.php?bugnote_id=0150177#r26121

Notes
(0150177)
marvintm   
2023-05-24 08:13   
(edited on: 2023-05-24 08:14)
The behavior of the application in this case is correct. In order for several flows in the POS to work, when an order is loaded, there must be a valid price list version for its pricelist, in the order date. Otherwise, some flows may fail.

So, it is not necessarily wrong to change the validity date of the price list version. However, if this is done, it is important to make sure that there is still a valid price list version for the dates in which orders were generated for this price list, otherwise it will not be possible to open them in the POS.

Anyway, even if it is possible, we recommend creating new price list versions that replace the old ones, instead of changing old ones.