[jira] [Closed] (OFBIZ-13460) Add durable MRP run history and provenance

["Divesh Dutta (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OFBIZ-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Divesh Dutta closed OFBIZ-13460.
--------------------------------
    Resolution: Fixed

> Add durable MRP run history and provenance
> ------------------------------------------
>
>                 Key: OFBIZ-13460
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13460
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: manufacturing
>    Affects Versions: Upcoming Branch
>            Reporter: Divesh Dutta
>            Assignee: Divesh Dutta
>            Priority: Trivial
>             Fix For: Upcoming Branch
>
>
> *Summary*
> Today, MRP execution details are not preserved in a durable way across runs. The current process reinitializes {{{}MrpEvent{}}}data at the start of a new run, so prior run context is lost. In addition, once related job/runtime records are cleared from {{{}JobSandbox{}}}, key audit details such as who triggered the run, when it ran, whether it completed successfully, and how long it took are no longer easily available.
> This improvement adds a lightweight, additive run-log model for MRP execution. The goal is to preserve durable run-level history and provenance without changing the existing {{MrpEvent}} reinitialization behavior.
> *Scope*
> This work introduces a new {{MrpRunLog}} entity and updates MRP execution so each run can persist:
>  * who triggered the run
>  * when it started and finished
>  * which facility or facility group it ran for
>  * the resulting {{mrpId}}
>  * run duration
>  * run status such as running, finished, or failed
>  * concise failure details
>  * a success summary including counts of created MRP events and proposed requirements
> *Acceptance Criteria*
>  * A durable {{MrpRunLog}} record should be created for each MRP run.
>  * MRP execution should update the run log as the run moves through running, finished, or failed states.
>  * The run log should store {{{}mrpId{}}}, timestamps, duration, and user/facility context when available.
>  * On failure, the run log should store a concise failure reason/message.
>  * On success, the run log should store a concise outcome summary and counts for created MRP events and proposed requirements.
>  * Existing OFBiz MRP screens should continue to work without regression.
>  



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