Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0055838
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] 02. Master data managementmajoralways2024-06-25 14:372024-09-06 08:45
ReportergorkaionView Statuspublic 
Assigned ToRetail 
PriorityhighResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0055838: Inconsistent duplicate EAN validation

DescriptionWhen Multi UPC module is installed there is a validation that avoids having the same active ean code duplicated in the multi upc tab (obmupc_prod_multiupc). This validation is also considering ean code defined in the main product tab (m_product)

However there is no validation on the ean code defined in the Product table. So it is possible to have different products with the same EAN code. In case both products are loaded in a POS Terminal the barcode scan is unpreditable since the POS will add one of the products with no warning. While searching by the EAN code returns all the duplicated products.
Steps To ReproduceGo to Product window and assign the same EAN code to at least 2 products that are in the same store assortment.
Go to POS and scan the EAN code. Note that the POS adds one of the products to the ticket.
Go to Search view and search by the EAN code. Note that the POS shows all the products sharing the EAN code.
Proposed SolutionThe same no duplicated validation should be enforced in the Product EAN field and in the MultiUPC tab.

There should not be 2 different active products in the same organization tree sharing the same EAN code.

The validation should ignore deactivated products and deactivated multi upc records.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0055807 closedRajesh_18 Retail Modules Duplicate UPC/EAN includes same product and deactivated records in the check 

-  Notes
(0166310)
frank_gonzalez (developer)
2024-06-25 14:45

Jira: https://openbravo.atlassian.net/browse/RM-14960 [^]
(0166689)
hgbot (developer)
2024-07-04 15:18

Merge Request created: https://gitlab.com/openbravo/product/openbravo/-/merge_requests/1293 [^]
(0168849)
guillermogil (developer)
2024-09-06 08:44

No further action will be done at this stage. We've chenged older versions and behaviour is the same so it is not a regression.
As we have in the pipe the project that will change those validations it will be address there

- Issue History
Date Modified Username Field Change
2024-06-25 14:37 gorkaion New Issue
2024-06-25 14:37 gorkaion Assigned To => Triage Omni OMS
2024-06-25 14:37 gorkaion Modules => Core
2024-06-25 14:37 gorkaion Triggers an Emergency Pack => No
2024-06-25 14:39 gorkaion Relationship added related to 0055807
2024-06-25 14:45 frank_gonzalez Note Added: 0166310
2024-06-25 18:38 marvintm Assigned To Triage Omni OMS => Retail
2024-06-25 18:38 marvintm Status new => acknowledged
2024-06-25 18:52 Rajesh_18 Assigned To Retail => Rajesh_18
2024-06-25 18:52 Rajesh_18 Status acknowledged => scheduled
2024-07-04 15:18 hgbot Note Added: 0166689
2024-09-06 08:44 guillermogil Note Added: 0168849
2024-09-06 08:44 guillermogil Type defect => design defect
2024-09-06 08:45 guillermogil Assigned To Rajesh_18 => Retail
2024-09-06 08:45 guillermogil Status scheduled => acknowledged
2024-09-06 08:45 guillermogil Status acknowledged => scheduled


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker