Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. OFBIZ-7173

The Product Added from 'Actual Material' screen could be consumed for producing end product during routing task execution

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 16.11.01
    • Component/s: manufacturing
    • Labels:
      None
    • Sprint:
      Community Day 2 - 2016

      Description

      Currently any new product added against given routing task via Actual Material screen just reflects the inventory statistics it.

      We could try to add the feature of having the added products actually be added in conjunction with Actual projected Material requirement based on original BoM associated with the routing.

      1. This could be done by creating fresh WorkEffortGoodStandard (WEGS) with such added products against specified routing.
      2. 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
      3. Any completed taks should have WEGS created in COMPLETED status and WEIA created as well by issuing the added item's qty.
      4. Start showing such newly added material requirement in conjunction with original requirement (based on BoM) under all relevant sections over Production Declaration Screen

      Please refer to attached screenshot for reference

      1. AM.png
        101 kB
        Swapnil Shah
      2. OFBIZ-7173.patch
        3 kB
        Anuj Jain
      3. OFBIZ-7173.png
        126 kB
        Swapnil Shah

        Issue Links

          Activity

          Hide
          pfm.smits Pierre Smits added a comment -

          What do you mean with 'just reflects the inventory statistics it'?

          Show
          pfm.smits Pierre Smits added a comment - What do you mean with 'just reflects the inventory statistics it'?
          Hide
          swash78 Swapnil Shah added a comment -

          By Inventory stats we meant that the intent of Actual Material screen is limited to show the inventory item level details for product directly issue against any task.

          Possibly, we can try to make it work in sync with Production Declaration screen by giving newly added products the very same treatment as that of BoM component as specified in tix description

          Show
          swash78 Swapnil Shah added a comment - By Inventory stats we meant that the intent of Actual Material screen is limited to show the inventory item level details for product directly issue against any task. Possibly, we can try to make it work in sync with Production Declaration screen by giving newly added products the very same treatment as that of BoM component as specified in tix description
          Hide
          anuj.jain Anuj Jain added a comment -

          Thanks Swapnil for reporting this,

          For #1 and #4 I have provided a patch.
          Previously, when a new component product added to a task, only InventoryItemDetail is created for such product and no WEGS is created for this component product, that's why it is not getting reflected on Production Run Declaration screen. I have added a patch which will create a new record for WEGS if no existing record for WEGS for this component found.

          Show
          anuj.jain Anuj Jain added a comment - Thanks Swapnil for reporting this, For #1 and #4 I have provided a patch. Previously, when a new component product added to a task, only InventoryItemDetail is created for such product and no WEGS is created for this component product, that's why it is not getting reflected on Production Run Declaration screen. I have added a patch which will create a new record for WEGS if no existing record for WEGS for this component found.
          Hide
          diveshdut Divesh Dutta added a comment -

          Thanks Anuj Jain for your patch. I have committed slightly modified patch of yours in revision number 1749088 in trunk . When setting value of any field

          Instead of this:

           
           <set field="createWorkEffortGoodStdMap.workEffortGoodStdTypeId" default-value="PRUNT_PROD_NEEDED"/
          

          You should write this:

           <set field="createWorkEffortGoodStdMap.workEffortGoodStdTypeId" value="PRUNT_PROD_NEEDED"/
          

          As name suggests default-value is used when no other value is set for the field, in your case you can use value instead of default value.

          Thanks Swapnil Shah for suggesting this improvement. I am assigning this ticket to you for verification and closure.

          Show
          diveshdut Divesh Dutta added a comment - Thanks Anuj Jain for your patch. I have committed slightly modified patch of yours in revision number 1749088 in trunk . When setting value of any field Instead of this: <set field= "createWorkEffortGoodStdMap.workEffortGoodStdTypeId" default -value= "PRUNT_PROD_NEEDED" / You should write this: <set field= "createWorkEffortGoodStdMap.workEffortGoodStdTypeId" value= "PRUNT_PROD_NEEDED" / As name suggests default-value is used when no other value is set for the field, in your case you can use value instead of default value. Thanks Swapnil Shah for suggesting this improvement. I am assigning this ticket to you for verification and closure.
          Hide
          swash78 Swapnil Shah added a comment - - edited

          I have completed testing for it and found the following issues.

          1. Once we issue the component partially (i.e. by producing partial quantity while task is still running) then "Issue Component" is not honoring the already made issuance and hence issuing the whole required quantity once again. (please refer to attached screenshot)

          Anuj Jain Can you please post remaining use cases from OFBIZ-7485 that you are planning to address in OFBIZ-7468.

          Show
          swash78 Swapnil Shah added a comment - - edited I have completed testing for it and found the following issues. Once we issue the component partially (i.e. by producing partial quantity while task is still running) then "Issue Component" is not honoring the already made issuance and hence issuing the whole required quantity once again. (please refer to attached screenshot) Anuj Jain Can you please post remaining use cases from OFBIZ-7485 that you are planning to address in OFBIZ-7468 .
          Hide
          anuj.jain Anuj Jain added a comment -

          Hi,

          The isssues which should/will be covered in OFBIZ-7468

          #1 For newly added product in the task when task is in start/running status, The WEIA is created with WEGS for the item. The inventory should not be issue(WEIA) till the user issue any component manually from the production run screen.
          #2 When any product is added in the task when task in completed status, the WEIA and WEGS both is created at that time. and WEGS should be created WEGS_COMPLETED status.
          #3 User should not allow to add any component to a task when production run is in cancel status.

          Show
          anuj.jain Anuj Jain added a comment - Hi, The isssues which should/will be covered in OFBIZ-7468 #1 For newly added product in the task when task is in start/running status, The WEIA is created with WEGS for the item. The inventory should not be issue(WEIA) till the user issue any component manually from the production run screen. #2 When any product is added in the task when task in completed status, the WEIA and WEGS both is created at that time. and WEGS should be created WEGS_COMPLETED status. #3 User should not allow to add any component to a task when production run is in cancel status.
          Hide
          anuj.jain Anuj Jain added a comment -

          Hello Swapnil Shah,

          Thanks for reporting this,

          This issue is not due to the fix, This is existing issue and I would fix it under OFBIZ-7512.

          Show
          anuj.jain Anuj Jain added a comment - Hello Swapnil Shah , Thanks for reporting this, This issue is not due to the fix, This is existing issue and I would fix it under OFBIZ-7512 .
          Hide
          swash78 Swapnil Shah added a comment -

          Based on other reference tickets provided for reported suggestions, i think we are good to close this one.

          Show
          swash78 Swapnil Shah added a comment - Based on other reference tickets provided for reported suggestions, i think we are good to close this one.

            People

            • Assignee:
              swash78 Swapnil Shah
              Reporter:
              swash78 Swapnil Shah
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development

                  Agile