[
https://issues.apache.org/jira/browse/OFBIZ-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760507#comment-15760507 ]
Swapnil Shah commented on OFBIZ-7468:
-------------------------------------
I reckon systemically allowing inventory pegging to cancelled jobs makes more sense only when issued/related components are physically consumed during production processing in real time. But possibly there can be some better ways to just correct reporting in accounting books or backward cost adjustment.
In real time as well, if inbound material requirements are actually consumed at any stage of production processing then it must have been physically issued on shop floor first and system should be honoring this process. If its happening otherwise then it looks to be a case of business process re-engineering first before allowing system to honor such cases. We can definitely develop this feature as custom requirement but not sure if it can be considered as norm.
Current OFbiz behavior also doesn't support it as it works something like as follows:
1) Production run(tasks) can only be cancelled before it moves into 'Confirmed' status (i.e. none of the tasks has started yet). Thereafter its not possible to mark the production run as cancelled. Nor is it possible to issue the components for task before starting it, What it essentially means is that if production run is cancelled then none of the task could have been started and hence nothing was physically consumed. That's one of the reason in this task we tried to prevent component from being added to cancelled task.
2) Once production run comes into 'Running' state (i.e. task(s) have been started) then its not possible to Cancel the production run. What it means is that issuance must be made in order to complete the production run(tasks).System provides flexibility to add components to Completed task as they have been physically consumed before completion. And its still intact.
Also in none of the above cases system perform any backward cost transfer on production run upon any release/issuance or returns made after production run stands completed or cancelled. (We might need to define and finalize the generic workflow first before supporting this)
> Define constraints while adding new material to the task which is in completed/cancel status.
> ---------------------------------------------------------------------------------------------
>
> Key: OFBIZ-7468
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7468> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Trunk
> Reporter: Anuj Jain
> Assignee: Anuj Jain
> Attachments: OFBIZ-7468.patch, OFBIZ_7468_1.png, OFBIZ_7468_2.png, OFBIZ_7468_3.png
>
>
> Define actions on adding new material to the task which is in completed/cancel status.
> Actions suggested by Swapnil :-
> # We can begin with simple constraint of allowing new material against the only those routing task that has not cancelled yet within a production run
> # Any completed taks for uncomplete Production Run should have WEGS created in COMPLETED status and WEIA created as well by issuing the added item's qty.
> # If production is already completed (aka all its routing task also completed/cancelled) then don't allow new material to be added from Actual Material screen
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
