You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Divesh Dutta (Jira)" <ji...@apache.org> on 2026/05/22 15:23:00 UTC
[jira] [Commented] (OFBIZ-13422) Create Production Run Query Services
[ https://issues.apache.org/jira/browse/OFBIZ-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18082907#comment-18082907 ]
Divesh Dutta commented on OFBIZ-13422:
--------------------------------------
*Implementation Plan*
# *findProductionRuns*
*
** *Purpose:* Return a paged list of production run summaries for search and browsing.
** *High-level logic:*
*** Accept paging inputs and common filters such as workEffortId, productId, facilityId, statusId, workEffortName, and a broad text query.
*** Query production run rows from the production run view/entity.
*** Resolve display fields server-side for each row.
*** Return a compact summary object for each production run, along with paging metadata like total count and hasNext.
# *getProductionRunDetails*
*
** *Purpose:* Return a full production run detail payload for a single production run.
** *High-level logic:*
*** Accept productionRunId or workEffortId.
*** Load the production run header and related routing tasks using existing OFBiz domain helpers.
*** Batch-load related parties, fixed assets, notes, task components, and issued quantities.
*** Group related data in memory by task or work effort id.
*** Build a detail response with top-level parties, notes, tasks, and components, plus header fields such as product, facility, status, quantities, and timestamps.
> Create Production Run Query Services
> ------------------------------------
>
> Key: OFBIZ-13422
> URL: https://issues.apache.org/jira/browse/OFBIZ-13422
> Project: OFBiz
> Issue Type: New Feature
> Components: manufacturing
> Affects Versions: Upcoming Branch
> Reporter: Divesh Dutta
> Assignee: Divesh Dutta
> Priority: Major
> Fix For: Upcoming Branch
>
>
> Create read-side services for production run data so manufacturing consumers can retrieve production run summaries and production run detail in a consistent service contract.
> The work should provide two services:
> * findProductionRuns
> * getProductionRunDetails
> These services should return production run data with server-side resolution of display fields where practical, including product name, facility name, status description, and unit-of-measure description. The services should also support batched lookup of related data to avoid repeated entity queries.
> The resulting service layer should be suitable for reuse by future integration layers and client applications.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)