Project:
| View Revisions: Issue #43835 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0043835: Inventory Status support in OMS engine | ||
| Revision | 2020-04-28 14:22 by vmromanos | ||
| Description | The OMS considers as available stock the one with qty on hand - reserved qty > 0. This is a valid and simple to understand rule: "if something is not reserved, it's available for the OMS engine". However, there are scenarios where, for whatever reason, we might have exceptions to this rule, like for example when the stock is in the store window (valid stock but we don't want to issue) or when the stock is damaged. In these cases the OMS shouldn't take it into account. Inventory Status should have a new flag called "Available for OMS" to control the stock that is exposed for the OMS. By default in existing installations it will be set equal to the "Available" flag. With this new configuration, for example, the bin associated to the store window should have associated an inventory status with the "Available for OMS" flag set to false, so the OMS can automatically bypass it. The Stock By Warehouse window, which is the input stock for the OMS engine execution, should show a new column in grid view "Quantity Available for OMS", which will be the one taken into account by the OMS engine. Existing fields "Qty on Hand" and "Nettable Qty" will remain in form view but they will be hidden in grid view. This change represents a functional API change that should be properly communicated. |
||
| Revision | 2020-04-23 12:12 by vmromanos | ||
| Description | The OMS considers as available stock the one with qty on hand - reserved qty > 0. This is a valid and simple to understand rule: "if something is not reserved, it's available for the OMS engine". However, there are scenarios where, for whatever reason, we might have exceptions to this rule, like for example when the stock is in the store window (valid stock but we don't want to issue) or when the stock is damaged. In these cases the OMS shouldn't take it into account. A generic way to define this kind of exceptions is by using the inventory status' Netteable flag in the bin definition. See http://wiki.openbravo.com/wiki/Modules:Inventory_Status#Netteable [^] for more information. So, for example, the bin associated to the store window should have associated an inventory status with the Netteable flag set to false, so the OMS can automatically bypass it. The Stock By Warehouse window, which is the input stock for the OMS engine execution, already has registered the netteable qty, so it should be easy to adapt the engine to support it and the performance shouldn't be affected either. |
||
| Revision | 2020-04-23 11:57 by vmromanos | ||
| Description | The OMS considers as available stock the one with qty on hand - reserved qty > 0. This is a valid and simple to understand rule: "if something is not reserved, it's available for the OMS engine". However, there are scenarios where, for whatever reason, we might have exceptions to this rule, like for example when the stock in the store window (valid stock but we don't want to issue) or when the stock is damaged. In these cases the OMS shouldn't take it into account. A generic way to define this kind of exceptions is by using the inventory status' Netteable flag in the bin definition. See http://wiki.openbravo.com/wiki/Modules:Inventory_Status#Netteable [^] So, for example, the bin associated to the store window should have associated an inventory status with the Netteable flag set to false, so the OMS can automatically bypass it. The Stock By Warehouse window, which is the input stock for the OMS engine execution, already has registered the netteable qty, so it should be easy to adapt the engine to support it and the performance shouldn't be affected either. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |