Through authorizations it is -theoretically- possible to restrict users to certain warehouses. However, with a large number of warehouses and users the drawback is: - lot of setup work - slow performance - not possible to grant a user - full access to warehouse A, - read access to warehouse B - no access to warehouse C. In my opinion it would be great to have a setup table "feasible warehouses per user". Preferably with authorization levels: full control, read, none. This should be respected at least in: - sales header - sales line - purchase header - purchase line - quotation header - quotation line - production order - production BOM - wave - load - shipment - work - on hand inventory - IC on hand inventory - transfer order header - warehouses - locations - inventory transactions Should be possible to setup from warehouse, and from user. Data area ID of the warehouse should also be part of the new table.
Comments
Inventory Transfer Order -
User can define "Vendor warehouse" simply by attaching Vendor to the warehouse. If this warehouse is used in "To" warehouse field in Inventory Transfer Order, that means that item is being sent to vendor location. System should allow user selecting vendor address and tax information for tax calculation purpose and also, there should also be a report filtering vendor warehouse shoing stock lying at vendor location, consumpton of the item, cost etc.
Category: Warehouse Management
Microsoft product team need to be really fast in action, in order to provide such useful features in time. Couple of ISVs and renouned developers do have design / code ready with them to review and incorporate in the product. Sometimes, its better to take a decision by focusing and considering the value of features, rather than going by the vote count.
Category: Warehouse Management
Continued Comment Part III.....
If user creates new delivery address in the PO (header), then system shows that address in the Organization >> Entity >> Address list which is not correct. Organization can request a vendor to deliver the item at specific location, say other vendor site, for outsourcing or project work etc. This type of transaction can also be covered if another type of warehouse (Outsourcing) is used in the delivery address.
Category: Warehouse Management
Continued Comment Part II.....
UI should have a capability of assigning a user, users or user group to one or multiple warehouses along with the below type of access rights-
a) No access - Warehouse won't be visible to the user anywhere in the transaction / inquire / report
b) Read only access - User will be able to use the warehouse to see the stock , inquiry, report or while transferring the item to "To" warehouse)
c) Full access - User will be able to use that warehouse in the transaction including "From" and "To" warehouse, can see all the transactions of that warehouse, inquiry and report.
I would suggest to provide list of menu items that user can use for the assigned warehouses. Existing security model is time consuming and complex. But this type of UI for user access can give a clear visibility stating which user will have access to which warehouse and related transactions/inquiry/report.
One more type of warehouse is needed as "Outsourcing". All the material sent out for any processing / repairs / replacement or service work (including office items like laptop etc.) should be routed through this type of warehouse, so that, a tracking can be done realizing which item is lying at which vendor, since how many days. If item is returned back then how much was paid for service charges or to repair the item. If item is changed after proess, then consumption of sent item and receipt of received item qty, cost etc should be tracked. A simple inward entry should be possible by taking the item as it is or by changing the item code or as a type service. If original form of the item is changed then consumption entry should be made and another item, if received, should be accepted in the store.
Currently, user need to define BOM mentioning vendor, service item or inventory item in it and then it can be used to send out for processing. Even if BOM related module is not implemented, this step is necessary.
Category: Warehouse Management
Comment Part I.........
An organization can have multiple operating offices / sites / warehouses. When a user at that specific address creates any PO or SO or any other record, system populates only one default warehouse or location that is setup in the system. In the system, we need to create multiple virtual warehouses against one real warehouse of the organization in real world (e.g.in transit warehouse, wip, main, quarantine, packing, vendor outsourcing etc). This becomes troublesome everywhere. User can select wrong warehouse or wrong office (in case of non-inventory transactions). Making correction is another task user need to perform. The expectation here is, if Microsoft provides a way to give office/warehouse/site specific user access and default value in it, then it would be of the great help to the user and organization.
A simple user interface having tree structure in it can be provided as under. Below is only the example to create a tree structure.
A) Office One-
a) Site - A
i) Warehouse - I (Raw Material / Main storage)
ii) Warehouse - II (Production Warehouse)
iii) Warehouse - III (In Transit Warehouse)
iv) Warehouse - IV (Quarantine Warehouse)
List of other warehouses created under Site - A
b) Site - B
i) Warehouse - V (Finished Goods Warehouse)
ii) Warehouse - VI (In Transit Warehouse)
B) Office Two -
a) Site - C
i) Warehouse - VII (Raw Material / Main storage)
ii) Warehouse - VIII (Production Warehouse)
iii) Warehouse - IX (In Transit Warehouse)
List of other warehouses created under Site - C
b) Site - D
i) Warehouse - IV
C) Office Three - No Site - No Warehouse
Category: Warehouse Management
Very important feature that is lacking.
Category: Warehouse Management
Hi
We have developed similar customization so if MCS wanted to review that Customization and incorporate then we are open to discuss this.
Regards
Uttam Bandivadekar
Category: Warehouse Management
Must have!
Category: Warehouse Management