Hi Carsten, Thanks for your feedback.
However, this is much like the handling of sales orders on products. When registering an order the inventory of the product is not adjusted, but only the AtP of the good. Likewise, the confirmation of a production run does not trigger the inventory mutation. That only happens when goods are released to the production run (action 'Issue Components'). But it should adjust the AtP. So that Requirements (for PO) and/or PO can be created earlier than when QoH reaches 0. Because in current situation both AtP and QoH are adjusted at the same moment (when components are issued and production output is declared). But also, when the AtP of the end product (the good to be produced)is adjusted at the moment of confirmation of the production run, no unwanted (incorrect) production runs will be generated due to MRP processes. I also want to remind you that currently running production runs can not be terminated with the 'Cancel'-action. Regards, Pierre Smits On Tue, Aug 20, 2013 at 2:20 PM, <[email protected]> wrote: > See my previous comments on the mailing list. I disagre with this > behaviour. > > The current behaviour reflects reality much better (I do not say this is > ideal). Taking raw materials out and putting inexistent stock in at the > confirmation of a production will result in incorrect accounts for both, > raws and end products, > > If we touch this, I suggest we check out inventory when work actually > begins (this is NOT when the prodrun is confirmed, but rather when the > first actual routing task is started) and allow to return a fraction of > checked out inventory when a prod run is cancelled. > The end product should only be added to stock/inventory when the prod run > is confirmed (allowing for example a QA function to confirm the Prod run > and add only the fraction of end products that have passed QA. > > Both, the check out of raw as well as the confirmation of end products > work in OFBiz as described above. Thus this JIra record should focus at the > inventory behaviour when production runs are cancelled. > > Regards > > > Carsten > > > ------Original Message------ > From: Pierre Smits (JIRA) > To: [email protected] > ReplyTo: [email protected] > Subject: [jira] [Created] (OFBIZ-5296) AtP of products should be adjusted > when production run is confirmed > Sent: Aug 20, 2013 14:09 > > Pierre Smits created OFBIZ-5296: > ----------------------------------- > > Summary: AtP of products should be adjusted when production > run is confirmed > Key: OFBIZ-5296 > URL: https://issues.apache.org/jira/browse/OFBIZ-5296 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing, product > Affects Versions: SVN trunk > Reporter: Pierre Smits > > > When a production run is confirmed we know what is intended to go in the > production run (the components or ingredients aka the raw materials) and > what is intended to go out (the finished product). > > Unlike with an order, the AtP (Availability to Promise) of the goods > involved does not get adjusted. > The result is that requirements for PO or even the PO itself get generated > to late (at the moment when QoH reaches minimum stock in stead of when AtP > reaches minimum stock). > > Following scenarios need to be resolved: > 1. On confirmation of the production run (action = Confirm), the AtP of > the product to be produced must increase and the AtP of materials needed > must decrease. > > 2. When production is running and materials have been released to the > production run, it is possible to return materials back to inventory. When > doing so, the AtP of the materials must be adjusted accordingly with the > same date-time and quantity as the returned materials. > > 3. When a production run has rejected end products the AtP of the end > product must be adjusted with the same date-time and quantity as the > declaration of the rejected product. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira > > Gesendet mit BlackBerry® Webmail von Telekom Deutschland
