[
https://issues.apache.org/jira/browse/OFBIZ-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226120#comment-14226120
]
Swapnil Shah commented on OFBIZ-5526:
-------------------------------------
[~ofbizzer] I understand that in order to have both of the above cases to be
working in real time,There seems to be few basic underlying assumptions as
follows:
# Produced part from predecessor task (that i would refer as intermediate
product) would be fed/used (as BoM component) for the immediate successor task.
# There is no existing WIP or ATP available in the facility apart from what is
produced/rejected through the given production run.
Moreover, as of now In the currently implemented workflow, i don't think there
is support for multi-step routing (where something produced from on routing
task is used to be fed into subsequent task within same production run and what
is produced from one task constraints or act as bottleneck for the production
from subsequent tasks).
Currently only check that prevent user from completing any given routing task
is through the issuance of pre-defined bill of material. And based on that it
seems both of the above data points are not pre-set in the system in order to
derive the desired behavior using existing flow. Can you please try to attempt
following and let us know how it behaves:
# Create just one step routing and associate the multiple tasks in its own
separate routing.
# Associate the intermediate product (produced from each task) to the concerned
routing set in step#1
# Set up the Intermediate product (produced from any given routing) as BoM
component for the subsequent routing/task as deliverable product
# Make sure that there is no existing WIP/ATP in the facility and whatever is
produced from one given production run would create the ATP for produced
product.
# Set up/create different production run based on above set up for each
product(intermediate product) that is supposed to be produced from each routing.
In this manner unless and until the production for intermediate products is not
complete from concerned production runs, the ATP for intermediate product won't
come into existence and hence subsequent production runs won't be allowed to be
completed because you won't be able to issue the required BoM component qty in
order to get its task completed.
Please let us know either way and let us know exact requirements so that we can
take it up as needed enhancement on top of existing workflow.
> registering defective products on task doesn't show in Production Run Header
> and completed tasks
> ------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-5526
> URL: https://issues.apache.org/jira/browse/OFBIZ-5526
> Project: OFBiz
> Issue Type: Bug
> Components: manufacturing
> Affects Versions: Release Branch 11.04, Release Branch 12.04, Release
> Branch 13.07, Trunk
> Reporter: Pierre Smits
>
> When registering rejected products on a task in a production run in
> execution, the (total of) rejected products are not shown on the Production
> Run Header, are not shown on the task completed. This subsequently leads to
> uncompleted production runs as the corrected output cannot be registered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
