Openbravo Issue Tracking System - Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0040941ModulesAdvanced Warehouse Operationspublic2019-05-23 13:422019-05-30 17:14
Reporterfrancisco 
Assigned ToTriage Omni WMS 
PriorityhighSeverityminorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Support ticket
OBNetwork customer
Regression introduced in release
Summary0040941: [AWO] The routing assignment is not working when a Product Category Tree is set
DescriptionThe routing assignment is not working when a Product Category Tree is set. If the routing assignment is configured with a child product category the routing assignment is observed, but if you configure the routing assignment using a parent product category (one to several levels), the routing assignment does not work.

This situation forces to have one Routing assignment for every child product category. We expect to have only to configure one routing assignment for every family of product/business partner category.
Steps To ReproduceGo to Product Category
Crate a father category with two son:
Frozen:
    Fish
    Meat
Go to Product
Create Tuna product with Fish as Product Category
Put Pallet as Alternate UOM
Go to warehouse definition
Create a Routing Assignment:
    Inventory Transaction type: Put-Away StorageDetaill
    Routing : STGn to SHP, ManConf - STGN - Storage - Non Public - US West Coast - SHP - Shipping - US West Coast
    Product category: Frozen
Go to Goods receipt to create stock of Tuna
Go to warehouse definition and Put-Away the Tuna
The bin that suggest is a storage bin and not the shipping
I the rest of the put-Away are non Active, but only the one which configure the product category "Frozen" it will say there is no route for that product
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2019-05-23 13:42franciscoNew Issue
2019-05-23 13:42franciscoAssigned To => Triage Finance
2019-05-23 13:42franciscoResolution time => 1560376800
2019-05-23 15:17SandrahuguetAssigned ToTriage Finance => nonofrancisco
2019-05-27 22:55nonofranciscoStatusnew => scheduled
2019-05-27 22:55nonofranciscoNote Added: 0112189
2019-05-30 16:31SandrahuguetResolution time1560376800 =>
2019-05-30 16:31SandrahuguetTypedefect => feature request
2019-05-30 16:37SandrahuguetNote Added: 0112277
2019-05-30 17:05vmromanosSeveritymajor => minor
2019-05-30 17:13vmromanosNote Added: 0112278
2019-05-30 17:14vmromanosAssigned Tononofrancisco => Triage Finance
2019-05-30 17:14vmromanosStatusscheduled => acknowledged
2022-09-06 17:18caristuCategoryAdvance Warehouse Operations => Advanced Warehouse Operations

Notes
(0112189)
nonofrancisco   
2019-05-27 22:55   
Test Plan

Go to Product Category
Crate a father category with two son:
Frozen:
    Fish
    Meat
Go to Product
Create Tuna product with Fish as Product Category
Put Pallet as Alternate UOM
Go to warehouse definition
Select US West Coast warehouse
Create a Routing Assignment:
    Inventory Transaction type: Put-Away StorageDetaill
    Routing : STGn to SHP, ManConf - STGN - Storage - Non Public - US West Coast - SHP - Shipping - US West Coast
    Product category: Frozen
Go to Goods receipt to create stock for Tuna in Food001 Storage Bin
Go to warehouse definition and Put-Away the Tuna
Verify the task was created successfully having Food001 as Expected Bin From and SHP301 as Expected Bin To
(0112277)
Sandrahuguet   
2019-05-30 16:37   
Moved to FR, the system works as expected.
The routing assignment not support trees in product category
(0112278)
vmromanos   
2019-05-30 17:13   
Please note that this change would also create a functional API change that might heavily change the existing users' flows.

Also note that implementing this feature would add several drawbacks:
* Performance penalty
* Complexity in the way to calculate the IRAssignment, and therefore in the way to explain to the user what really happened.
* Full redefinition of the rules for finding the best IRAssignment (what happens if there is a match with a father? or a grandfather? What is the score in those cases? How this score affects other filters (like Product, BP, etc.)?
* Not only IRAssignment would be affected, but Warehouse Algorithms too in the same sense.