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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0055807
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Multi UPC/EAN for Productmajoralways2024-06-20 13:282024-06-25 18:48
ReportergorkaionView Statuspublic 
Assigned ToRajesh_18 
PriorityhighResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0055807: Duplicate UPC/EAN includes same product and deactivated records in the check

DescriptionWhen an update wants to remove a EAN code defined in the multiupc tab the proper way is to deactivate it so the incremental refreshes in the POS can remove it from the cache.

The handler checking for duplicated eans is not taking into account the deactivated multiupc eans. This is wrong since it avoids to assign the deactivated ean code to a different product.

The handler is not allowing duplicates in the same product. Hving the same EAN code in the Product header and in the mutiupc tab of the same product should be allowed.

Use case is: Product has code EAN13A in the product and EAN13B in the multiupc. Now it is required to switch them since the EAN13B has become the main one. This results in EAN13B in the header as a deactivated record in the multiupc and the EAN13A inserted in the multiupc tab. If this change is done using an integration process usually all the changes are flushed a single time causing the handler to fail as it is consindering the multiupc EAN13B still active.
Steps To Reproducetry to deactivate a multiupc ean and assign it to a different product or set it as the main ean of hte same product.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to design defect 0055838 scheduledRetail Openbravo ERP Inconsistent duplicate EAN validation 

-  Notes
(0166242)
hgbot (developer)
2024-06-24 10:25

Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.multiupc/-/merge_requests/8 [^]
(0166321)
hgbot (developer)
2024-06-25 18:48

Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.multiupc/-/merge_requests/8 [^]
(0166322)
hgbot (developer)
2024-06-25 18:48

Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.multiupc [^]
Changeset: 6aae2a648b8bb8308e0818caf400fa61183c5228
Author: Rajesh Senthilkumar <rajesh@qualiantech.com>
Date: 24-06-2024 11:24:31
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.multiupc/-/commit/6aae2a648b8bb8308e0818caf400fa61183c5228 [^]

Fixed ISSUE-55807: Refactored multiupc event handler to check duplicate of upc

---
M src-db/database/model/tables/OBMUPC_PROD_MULTIUPC.xml
M src/org/openbravo/multiupc/event/NoDuplicateUpcHandler.java
---

- Issue History
Date Modified Username Field Change
2024-06-20 13:28 gorkaion New Issue
2024-06-20 13:28 gorkaion Assigned To => Retail
2024-06-20 13:28 gorkaion Triggers an Emergency Pack => No
2024-06-20 13:29 marvintm Status new => acknowledged
2024-06-20 14:45 Rajesh_18 Assigned To Retail => Rajesh_18
2024-06-20 14:45 Rajesh_18 Status acknowledged => scheduled
2024-06-24 10:25 hgbot Note Added: 0166242
2024-06-25 14:39 gorkaion Relationship added related to 0055838
2024-06-25 18:48 hgbot Note Added: 0166321
2024-06-25 18:48 hgbot Resolution open => fixed
2024-06-25 18:48 hgbot Status scheduled => closed
2024-06-25 18:48 hgbot Note Added: 0166322


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker