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

Swapnil Shah updated OFBIZ-7485:
--------------------------------
    Description: 
Here is the list of use cases that could be validated upon fixes made in 
OFBIZ-7173

# *CASE-01 -Production Run is created/confirmed but routing task is still not 
started*
## As soon as new Material is added via "Actual Material" screen for any task, 
the WorkEffortGoodStandard (WEGS) record should be created in WEGS_CREATED 
Status
## The above created WEGS should be reflected over "Production Run Declaration 
tab" under "Materials Required By The Running Task" section along with other 
material requirements created out of pre-defined BoM for to be produced item.

# *CASE-02-Routing task for any active Production Run is already started*
## As soon as new Material is added via "Actual Material" screen for any 
running routing task, the WorkEffortGoodStandard (WEGS) record should be 
created in WEGS_CREATED Status
## The above created WEGS should be reflected over "Production Run Declaration 
tab" under "Materials Required By The Running Task" section along with other 
material requirements created out of pre-defined BoM for to be produced item.
## Once user "Issue Component(ATP)" then available ATP against above newly 
created material requirement (WEGS) should get issued and new 
WorkEffortInventoryAssign (WEIA) should be created.
## The issued qty should also be reflected over "Production Run Declaration 
tab" under "Return Unused Materials To Warehouse" against respective task and 
be allowed to returned back to warehouse.

# *CASE-03-Production Run is not completed yet the Routing task get Completed*
##  As soon as new Material is added via "Actual Material" screen for any 
running routing task, the WorkEffortGoodStandard (WEGS) record should be 
created in WEGS_COMPLETED Status and subsequently the added material 
requirement should get issued and new WorkEffortInventoryAssign (WEIA) should 
be created in same transaction itself.
## The issued qty should also be reflected over "Production Run Declaration 
tab" under "Return Unused Materials To Warehouse" against respective task and 
be allowed to returned back to warehouse.

# *CASE-04-Routing task for any active Production Run is cancelled*
## New Material shouldn't be allowed to be added via Actual Material screen for 
any already cancelled task with proper error message

# *CASE-05-Production Run is already Completed (aka all Routing task are also 
completed/cancelled)*
## New Material shouldn't be allowed to be added via Actual Material screen for 
any already cancelled task with proper error message.


  was:
Here is the list of use cases that could be validated upon fixes made in 
OFBIZ-7173

* *Production Run is created/confirmed but routing task is still not started*
# As soon as new Material is added via "Actual Material" screen for any task, 
the WorkEffortGoodStandard (WEGS) record should be created in WEGS_CREATED 
Status
# The above created WEGS should be reflected over "Production Run Declaration 
tab" under "Materials Required By The Running Task" section along with other 
material requirements created out of pre-defined BoM for to be produced item.

* *Routing task for any active Production Run is already started*
# As soon as new Material is added via "Actual Material" screen for any running 
routing task, the WorkEffortGoodStandard (WEGS) record should be created in 
WEGS_CREATED Status
# The above created WEGS should be reflected over "Production Run Declaration 
tab" under "Materials Required By The Running Task" section along with other 
material requirements created out of pre-defined BoM for to be produced item.
# Once user "Issue Component(ATP)" then available ATP against above newly 
created material requirement (WEGS) should get issued and new 
WorkEffortInventoryAssign (WEIA) should be created.
## The issued qty should also be reflected over "Production Run Declaration 
tab" under "Return Unused Materials To Warehouse" against respective task and 
be allowed to returned back to warehouse.

* *Production Run is not completed yet the Routing task get Completed*
#  As soon as new Material is added via "Actual Material" screen for any 
running routing task, the WorkEffortGoodStandard (WEGS) record should be 
created in WEGS_COMPLETED Status and subsequently the added material 
requirement should get issued and new WorkEffortInventoryAssign (WEIA) should 
be created in same transaction itself.
## The issued qty should also be reflected over "Production Run Declaration 
tab" under "Return Unused Materials To Warehouse" against respective task and 
be allowed to returned back to warehouse.

* *Routing task for any active Production Run is cancelled*
# New Material shouldn't be allowed to be added via Actual Material screen for 
any already cancelled task with proper error message

* *Production Run is already Completed (aka all Routing task are also 
completed/cancelled)*
# New Material shouldn't be allowed to be added via Actual Material screen for 
any already cancelled task with proper error message.



> Documentation: Unit Test (Use)Cases for OFBIZ-7173
> --------------------------------------------------
>
>                 Key: OFBIZ-7485
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7485
>             Project: OFBiz
>          Issue Type: Task
>          Components: manufacturing
>    Affects Versions: Upcoming Branch
>            Reporter: Swapnil Shah
>            Assignee: Swapnil Shah
>
> Here is the list of use cases that could be validated upon fixes made in 
> OFBIZ-7173
> # *CASE-01 -Production Run is created/confirmed but routing task is still not 
> started*
> ## As soon as new Material is added via "Actual Material" screen for any 
> task, the WorkEffortGoodStandard (WEGS) record should be created in 
> WEGS_CREATED Status
> ## The above created WEGS should be reflected over "Production Run 
> Declaration tab" under "Materials Required By The Running Task" section along 
> with other material requirements created out of pre-defined BoM for to be 
> produced item.
> # *CASE-02-Routing task for any active Production Run is already started*
> ## As soon as new Material is added via "Actual Material" screen for any 
> running routing task, the WorkEffortGoodStandard (WEGS) record should be 
> created in WEGS_CREATED Status
> ## The above created WEGS should be reflected over "Production Run 
> Declaration tab" under "Materials Required By The Running Task" section along 
> with other material requirements created out of pre-defined BoM for to be 
> produced item.
> ## Once user "Issue Component(ATP)" then available ATP against above newly 
> created material requirement (WEGS) should get issued and new 
> WorkEffortInventoryAssign (WEIA) should be created.
> ## The issued qty should also be reflected over "Production Run Declaration 
> tab" under "Return Unused Materials To Warehouse" against respective task and 
> be allowed to returned back to warehouse.
> # *CASE-03-Production Run is not completed yet the Routing task get Completed*
> ##  As soon as new Material is added via "Actual Material" screen for any 
> running routing task, the WorkEffortGoodStandard (WEGS) record should be 
> created in WEGS_COMPLETED Status and subsequently the added material 
> requirement should get issued and new WorkEffortInventoryAssign (WEIA) should 
> be created in same transaction itself.
> ## The issued qty should also be reflected over "Production Run Declaration 
> tab" under "Return Unused Materials To Warehouse" against respective task and 
> be allowed to returned back to warehouse.
> # *CASE-04-Routing task for any active Production Run is cancelled*
> ## New Material shouldn't be allowed to be added via Actual Material screen 
> for any already cancelled task with proper error message
> # *CASE-05-Production Run is already Completed (aka all Routing task are also 
> completed/cancelled)*
> ## New Material shouldn't be allowed to be added via Actual Material screen 
> for any already cancelled task with proper error message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to