[ 
https://issues.apache.org/jira/browse/OFBIZ-13246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985829#comment-17985829
 ] 

Yashwant Dhakad commented on OFBIZ-13246:
-----------------------------------------

Hi [~jacopoc], Thank you for the update. I agree that this issue cannot be 
reproduced in the current trunk version—once the internal requirement is 
approved, the system automatically generates the production run as expected.

Given that, I believe we can close this ticket. However, I would like to 
suggest a small enhancement: we could consider linking the internal requirement 
to the corresponding production run, and upon approval of the production run 
job, automatically update the requirement status to "Closed". This would help 
ensure that already-approved requirements are not picked up again in subsequent 
MRP runs, thereby avoiding redundant processing.

Please let me know your thoughts on this approach.

> Automate creation of production runs from approved internal requirements in 
> the Manufacturing module
> ----------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-13246
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13246
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: manufacturing
>    Affects Versions: Upcoming Branch
>            Reporter: Yashwant Dhakad
>            Priority: Trivial
>
> In the Manufacturing module, when an internal requirement is approved, the 
> system doesn’t automatically create the related production run. Instead, 
> users have to manually go back to the manufacturing screen and enter details 
> like the product ID, facility, and quantity again. This is because the 
> requirement approval screen neither shows the production run nor starts it.
> This creates a disconnect between two steps that are closely related: the 
> component that has been made internally and the finished product that needs 
> to be produced. This gap leads to delays, mistakes, and 
> inefficiencies—especially in high-volume operations. To fix this, the system 
> should:
>  * Automatically create a production run upon requirement approval, applying 
> the associated Bill of Materials (BOM) and routing.
>  * Link the production run to the requirement for traceability.
>  * Display a UI message or log to confirm creation.
> These changes will eliminate redundant steps, enhance traceability, and 
> streamline manufacturing operations.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to