|
Hi,
We have worked lately quite a lot on the warehouse management in an implementation for Internet company delivering processed and non-processed food with several delivery and preparation batch per day (To be noted that in 3 months operations, we already have 1 M stock moves which is currently becoming burdensome for many calculations/concurrent access - see below). Besides we have several implementation in industrial organization. Here after is a summary on user experiences and shortcomings using current OpenERP. I will not focus on what you plan to discussed in your (already said but true) excellent document. The direction taken would cover many of the current OpenERP shortcomings in warehouse management. Following functionalities are more usability issues that have been needed and implemented in all projects. We think these are important features to be included in the core. Processes - A stock move that is leaving is not a stock move that is arriving: there is a delay in transport and a stock move should have an intermediate state "on the way". Ideally a transport delay grid between location should be necessary. - QC location: to be bundled with QC ACL where a stock move can only be processed/validated by QC manager. - Quick internal move form: to be able to create a quick move (similar as SO/PO in editable tree sub form) - Wizard for batch process: confirm, cancel, check availability and force availability should be possible with a batch process wizard - Button in SP to deliver what is Available only. Physical inventory - Extremely slow with increasingly number of stock moves (all stock moves are accounted one by one...) - Cycle counting (setup in product or location) Barcoding support - Necessary for incoming shipments with lot management (nan-tic have done some great job) - Necessary for preparation after the wave is received (vocal preparation, scanning one by one products and system telling in which carton/hole to place the product) Double UoM - Auto MO for UoM conversion: currently one of the biggest difficulty: we sell packs of Apple that we need to convert from kilos. We have created the possibility to automatically produce MO (checking availability) for this case. Nevertheless, double UoM conversion should be available by default (UoS is not enough). Propagation - Possibility to propagate dates in SM. Eg a suppliers announces a delay in delivery and it impacts all the SCM. You want to be able to recalculate all chained moves. - 1 PO to supplier and the PO is split by the supplier => propagate the split along the supply chain (done in: http://v6apps.openerp.com/addon/7540) ACL: - Role per warehouse => stock for the given warehouse, ACL etc. - Misses the QC Manager role Reports on Stocks level and value: - We need to be able to easily access stock level at given time (currently report is far too slow). I have the feeling that stock.quant should solve the problem though - Cost as property may result as too slow and may generate concurrent access in batch processes when a procurement scheduler is running. What about a cost history table (with product_id, lot_id, company, price, date/time etc.). Every time a cost change, a new record is created: it allows a function to query anytime a cost for a company. - We need to be able to access the value of the stock at a given time for a company: cost history table should be able to solve this - today it is extremely difficult to have a synthetic view of the SCM in OpenERP. a simple report on all linked SM is necessary (with expected availability dates or Gantt view). Better if this is at MO/BoM level. - User must be able to easily know at which location/production lot is a product. Currently with high number of stock moves, stock report is useless. - In general, it is not normal that for any stock level, all SM have to be computed. Intermediate calculation should be stored. Expiry and PL - Expiry in production lot: sometimes it is a automatic calculation based on production date (in China, goods are labeled with production date, not expiry), sometimes on arrival date (Fruit and Vegetables) or manual input. Setup on the product or category - You cannot probably force production lot in the SM management but you can surely do it in the interface to avoid SM with no PL Procurement - At procurement level: add the possibility to modify the supply_method and supplier Return from customer/to supplier: - Default Return locations in warehouse: when returning from customer, it should be selected (Push Flows can be triggered) - could be in separate menus with a field to identify them (normal/return from customer/to supplier). - In the wizard to return, the default return location should be proposed. - a reason code is often necessary at that level. Delivery/wave process - Nothing mentioned in your document but you did mention waves. We have developed the wave function in our side and we had to create a Delivery Timeslot and Preparation Timeslot: - DTS: expected window (in date/time, not days) for delivery. Assigned at SO level (and PO for collected ones). Linked to the delivery module - PTS: expected window (in date/time, not days) for preparation (linked to DTS) - To create the waves we have rewritten the procurement scheduler taking into account the PTS (which is unit of measure smaller than the day) - all PTS/DTS are included in menus for search etc. Hope this help. We will publish during the summer a clean version of the modules developed so far in v7. Eric Caudal CEO -- Elico Corporation, Shanghai branch OpenERP Premium Certified Training Partner Cell: + 86 186 2136 1670 Office: + 86 21 6211 8017/27/37 Skype: elico.corp [email protected] http://www.elico-corp.com 
|
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
