Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0008361Openbravo ERP05. Production managementpublic2009-02-18 17:482011-10-28 10:38
Reportereduardo_Argal 
Assigned Togorkaion 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionout of date 
PlatformOS20OS VersionUbuntu 8.04Hardy
Product Version2.35MP5 
Target VersionpiFixed in Version 
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
Summary0008361: Work effort: when generating standards, rejected quantity is not taken into account when updating stock.
DescriptionWork effort: when generating standards, rejected quantity is not taken into account when updating stock.
Steps To ReproduceCreate a process plan and work requirement.

Create a work effort.

In the Production Run tab select a phase of the created work requirement and fill the quantity and rejected quantity.

Run the create standards process. The quantities of the products haven't considered the rejected quantity and are based on the produced quantity.
Proposed SolutionModify the 'Create standard' process to consider the rejected quantity when the used product quantities are calculated.

Hide the 'Quantity rejected' field in the product tab for produced products.

Add a callout to increase/decrease the 'quantity' field when the 'quantity rejected' is modified for used products. In the product tab the 'quantity' field is the total quantity used in the production, including the rejected quantity.
Additional Information
TagsNo tags attached.
Relationships
blocks design defect 0007642pi scheduled gorkaion Work effort: when generating standards, rejected quantity is not taken into account when updating stock. 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-03-31 12:33psarobeTypedefect => backport
2009-03-31 12:33psarobefix_in_branch => 2.40
2011-10-28 10:38psarobeNote Added: 0042193
2011-10-28 10:38psarobeStatusscheduled => closed
2011-10-28 10:38psarobeResolutionopen => out of date

Notes
(0042193)
psarobe   
2011-10-28 10:38   
Openbravo provides community support only for the latest Openbravo version, which is Openbravo 3. This version has significantly improved financial flow, filtering, performance, etc and this issue is not present there. Upgrade path from Openbravo 2.50 to latest Openbravo version is available so we recommend to upgrade your instance to get this issue fixed.

Life cycle guarantee (backporting bug fixes to the previos to latest releases (Openbravo 2.40, 2.50)) is available for Professional Edition subscribers only. Please register your ticket through Openbravo Support Portal (http://support.openbravo.com/ [^]) if you have valid Professional subscription.

You can find more details about our Support policy in the following blog post
http://paolojuvara.blogspot.com/2009/12/maintenance-policy-for-openbravo-250.html [^]