Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0055838Openbravo ERP02. Master data managementpublic2024-06-25 14:372024-09-06 08:45
gorkaion 
Retail 
highmajoralways
scheduledopen 
5
 
 
Core
No
0055838: Inconsistent duplicate EAN validation
When 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.
Go 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.
The 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.
No tags attached.
related to defect 0055807 closed Rajesh_18 Retail Modules Duplicate UPC/EAN includes same product and deactivated records in the check 
Issue History
2024-06-25 14:37gorkaionNew Issue
2024-06-25 14:37gorkaionAssigned To => Triage Omni OMS
2024-06-25 14:37gorkaionModules => Core
2024-06-25 14:37gorkaionTriggers an Emergency Pack => No
2024-06-25 14:39gorkaionRelationship addedrelated to 0055807
2024-06-25 14:45frank_gonzalezNote Added: 0166310
2024-06-25 18:38marvintmAssigned ToTriage Omni OMS => Retail
2024-06-25 18:38marvintmStatusnew => acknowledged
2024-06-25 18:52Rajesh_18Assigned ToRetail => Rajesh_18
2024-06-25 18:52Rajesh_18Statusacknowledged => scheduled
2024-07-04 15:18hgbotNote Added: 0166689
2024-09-06 08:44guillermogilNote Added: 0168849
2024-09-06 08:44guillermogilTypedefect => design defect
2024-09-06 08:45guillermogilAssigned ToRajesh_18 => Retail
2024-09-06 08:45guillermogilStatusscheduled => acknowledged
2024-09-06 08:45guillermogilStatusacknowledged => scheduled

Notes
(0166310)
frank_gonzalez   
2024-06-25 14:45   
Jira: https://openbravo.atlassian.net/browse/RM-14960 [^]
(0166689)
hgbot   
2024-07-04 15:18   
Merge Request created: https://gitlab.com/openbravo/product/openbravo/-/merge_requests/1293 [^]
(0168849)
guillermogil   
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