Hi all, While developing a PWA app for the MRP planning on top of Apache OFBiz, I found a gap regarding MRP run history and provenance.
Today, MrpEvent stores the planning event ledger, but run-level context is not stored durably. Some details can be reconstructed from JobSandbox and serialized RuntimeData, such as who ran MRP, the facility, run name, start/finish time, and duration. However, JobSandbox is scheduler working data and can be purged based on service engine configuration. This means MrpEvent rows may still exist, but the context explaining which run produced them can be lost. I would like to propose adding a small durable MRP run history entity, for example MrpRunLog, to store one header row per MRP execution. Possible fields: mrpId, jobId, mrpName, facilityId, facilityGroupId, runByUserLoginId, statusId, startedAt, finishedAt, durationMillis This would help with: - Showing which MRP run produced the current event plan. - Showing who ran it, when, for which facility/warehouse, and its duration. - Avoiding fragile API logic that deserializes RuntimeData to reconstruct business context. - Preserving MRP run provenance even after JobSandbox cleanup. MrpEvent would remain the detailed event ledger. The new entity would only store run-level metadata/provenance. Does this direction sound reasonable? If there is agreement, I can create a Jira ticket with the proposed entity and service changes. Thanks -- Divesh Dutta www.hotwaxystems.com
