Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0005215Openbravo ERP02. Master data managementpublic2008-09-23 18:122009-02-27 07:28
ReporterPavelPonomarev 
Assigned ToDowid 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS10OS VersionXP SP3
Product Versionpi 
Target VersionFixed in Versionpi 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0005215: Verify Bom button works incorrectly
DescriptionWhen a user creates a Product and adds products to its BOM, he can take that highlevel BOM and add it to itself. Then, the user clicks on the Verify BOM button, and the system does _not_ show an error that should signal of the BOM tree being incorrect.

Steps To Reproduce1. Navigate to Master Data Management || Product || Product
2. Search for a product with an existing BOM (ex. "foodkit" in trunk version)
3. Open found product
4. Master Data Management || Product || Product >> Bill of Materials
5. Create new BOM
6. Add multiple various products INCLUDING the current product (ex. "foodkit"). Save
7. Navigate to Master Data Management || Product || Product
8. Click "Verify BOM"

The system shows a success message, but the BOM tree is incorrect...
Proposed SolutionModify M_PRODUCT_BOM_CHECK function using the attached patch.
Additional Information
TagsNo tags attached.
Relationships
related to defect 0005229 closed Dowid Temporary tables T_Selection and T_Selection2 have been ported from v2.22 to 2.35 improperly 
depends on backport 0005216 closed Dowid Verify Bom button works incorrectly 
depends on backport 0005217 closed Dowid Verify Bom button works incorrectly 
related to defect 0004885 closed Dowid The BOM_PRICESTD, BOM_PRICELIMIT and BOM_PRICELIST function get an error 
Attached Filespatch VerifyBOM.patch (1,283) 2008-09-23 18:12
https://issues.openbravo.com/file_download.php?file_id=272&type=bug
Issue History
Date ModifiedUsernameFieldChange
2008-09-23 18:12PavelPonomarevNew Issue
2008-09-23 18:12PavelPonomarevAssigned To => cromero
2008-09-23 18:12PavelPonomarevsf_bug_id0 => 2124838
2008-09-23 18:12PavelPonomarevFile Added: VerifyBOM.patch
2008-09-23 18:12PavelPonomarevRegression testing => No
2008-09-23 18:17PavelPonomarevRelationship addedrelated to 0005017
2008-09-23 18:18PavelPonomarevRelationship addedrelated to 0005016
2008-09-23 18:41cromeroStatusnew => scheduled
2008-09-23 18:41cromerofix_in_branch => trunk
2008-09-23 18:41cromeroAssigned Tocromero => Dowid
2008-09-23 18:41cromerofix_in_branchtrunk =>
2008-09-24 12:58DowidRelationship addeddepends on 0005229
2008-10-24 12:09DowidRelationship deletedrelated to 0005016
2008-10-24 12:10DowidRelationship deletedrelated to 0005017
2008-10-24 12:12DowidRelationship addedblocks 0004885
2008-10-24 12:12DowidRelationship deletedblocks 0004885
2008-10-24 12:13DowidRelationship addedrelated to 0004885
2008-10-24 12:15DowidRelationship deleteddepends on 0005229
2008-10-24 12:16DowidRelationship addedrelated to 0005229
2008-11-11 13:56DowidNote Added: 0010168
2008-11-11 13:57DowidStatusscheduled => resolved
2008-11-11 13:57DowidResolutionopen => fixed
2008-11-11 13:57Dowidsvn_revision => 9767
2009-02-27 07:28sureshbabuStatusresolved => closed
2009-02-27 07:28sureshbabuNote Added: 0014123
2009-02-27 07:28sureshbabuFixed in Version => trunk

Notes
(0010168)
Dowid   
2008-11-11 13:56   
The solution is to replace string:

SELECT v_IsBOM INTO v_IsBOM FROM M_Product WHERE M_Product_ID=v_Record_ID;

to:

SELECT IsBOM INTO v_IsBOM FROM M_Product WHERE M_Product_ID=v_Record_ID;


This bug has been fixed with bug
0005229: Temporary tables T_Selection and T_Selection2 have been ported from v2.22 to 2.35 improperly
Revision: 9767
(0014123)
sureshbabu   
2009-02-27 07:28   
Retested in context 79.125.56.185/openbravotrunk