 |
|
Topic: Paste a column of quantities into "New Purchase Order" and "New RFQ"?
|
| By: Ken at DTS | Posted on: Jan 27 2022 at 02:49:13 PM | Hello,
Our new project RFQ/Purchasing workflow includes 1) generate a Consolidated PickList, 2) sort it by Supplier, 3) enter the "New RFQ" or "New Purchase Order" for a Supplier as appropriate, 4) manually click on each p/n in "Select items to add" as given in the Consolidated PickList, 5) manually enter in each item's quantity as given in the Consolidated PickList.
At minimum, it would simplify Step 5 if the "New RFQ" and "New Purchase Order" DataGrids would permit a multi-row paste. This would permit all of the quantities manually copied from the Consolidated PickList to be transferred in one step into a RFQ or PO. This might be easy to implement because after Step 4 all of the "Quantity" cells exist and are waiting for input.
A more complicated solution would simplify Steps 4 and 5 somehow. | |
| By: Jason | Posted on: Jan 28 2022 at 05:17:06 AM | When you're looking at a Work Order BOM you see a burger (3 lines) menu button at the top of the BOM. Click that and select the option to "Show Shortages".
This shows what you need to buy. There's an "Order Y/N" checbox column. Place a checkmark into each item you want to buy (shortages are highlighted in red).
Now when you open a PO for any vendor these items will be pre-populated into the PO.
FEATURE REQUEST.
The above works well but it would be better if there was a way to go to the Purchasing Menu area and see a list of Vendors who have items waiting to be ordered. | |
| By: Ken at DTS | Posted on: Jan 28 2022 at 02:26:23 PM | Thanks, Jason. I started experimenting with Customer Orders and Work Orders... which is how MiniMRP is designed to be used, after all.
We presently don't use MiniMRP to track inventory or create Work Orders. This is because we only buy materials against each project. When materials are received, they are placed alongside all of the other materials for that project. At the end of the project, all parts ordered for that project are sent to the customer. At present, we have one MiniMRP "location/site", each issued PO adds to an item's "on hand qty", and (because we don't issue Work Orders) "on hand qty" is continually increasing and is ignored.
The problem with the above is that if I want to use a Work Order to create shortages in order to give one the opportunity to automatically populate a vendor PO, the quantities take into account our incorrect "on hand qty". There is no way to override the quantity on the "Show Shortages" screen.
I just noticed that MiniMRP supports an infinite number of "locations/sites". (I had thought incorrectly that it only permitted 6 "locations/sites".) I considered making a separate "location/site" for each project. Question: Does each new "location/site" use what appears to be a separate master list of components and assemblies? I seem to recall this behavior when first evaluating MiniMRP years ago. | |
| By: Jason | Posted on: Jan 29 2022 at 06:26:26 AM | Hi Ken. So you're just using it as an inventory database. Not using the Works Orders, Bills of Materials? Or are you creating Assemblies/BOMs but just not Work Ordering them.
One idea for you might be to create multiple separate folders. There's another topic on the forum where somebody asked about that. here's the answer that was given
Assuming you are a single user (ie not a network of users sharing the same database)
Navigate to c:program files(x86) See the minimrp folder and click it with the RIGHT mouse button and select "Copy"
Now go to your desktop and click with the RIGHT mouse button into an empty area of the desktop and select "Paste"
You now have a copy of the program folder on your desktop.
Open the folder you've just copied and you'll see the minimrp program. If you start minimrp via that you'll be using the database in that folder.
You can make as many copies as you wish.
The 'Pro' version is easier in that there's a button within the program allowing you to navigate to and select a data file.
The only downside of the above methods is that there's not really any way for you to see which database you're in so it requires a bit of disciplin on your part to make sure you're actually in the database you want to be.
With multiple folders you could have one for every customer or for every project.
I don't think using the multiple locations is right for what you want to do. I think the Multiple folder idea might be better. Or if you have the Pro version you could have multiple data files with different names and just point minimrp at whatever data file you want to work with.
I'm sure if you email support they'll be happy to send you a blank data file so you can set up a few project folders
| |
| By: Ken at DTS | Posted on: Jan 29 2022 at 08:49:13 AM | Hi, Jason,
We are using the Pro version. We are creating Components/Assemblies/BOMs but just not Work Ordering them. Still use MiniMRP to generate and track Supplier Purchase Orders.
We are familiar with the "separate program folders for separate Access databases" model. I took advantage of it during the initial roll-out of MiniMRP for "off-line" experimentation and "isolated" training of new users. We've since switched to MS SQL Server to enjoy the speed improvements.
| |
| By: Guest | Posted on: Jan 31 2022 at 05:57:15 AM | In that case you could create multiple databases in your SQL Server.
In MiniMRP, in the database setup window, just select a different database to switch from one to the other.
That wouldn't be as snappy as switching folders but probably still better than trying to fiddle with the Multiple Locations in one database. | |
| By: Ken at DTS | Posted on: Jan 31 2022 at 08:05:09 AM | Separate databases would mean different lists of Components and Assemblies, but most of our Components and Assemblies are common across all of our projects.
| |
| By: Guest | Posted on: Feb 1 2022 at 09:09:49 AM | In that case, Ken, I guess the only option would be to use the Locations thing. Locations can be added for each new project but can only be removed under certain circumstances such as zero stock, zero orders etc. There's no magic button to flush/empty a location and delete it once your project is complete so it'l likely that your list of locations would just get bigger.
Do you really keep totally separate inventories for different projects? Physically separate as in different rooms, shelves etc. | |
| By: Ken at DTS | Posted on: Feb 1 2022 at 09:48:09 AM | > Do you really keep totally separate inventories for different projects?
Basically, yes. We do have "bin items", of course, for bulk items such as fasteners, wire and sheet metal that aren't purchased against a particular project. Otherwise, when a part is received from a supplier, we mark its PO as "received" then physically place it directly into the project's assembly area; it does not pass though a traditional stockroom.
MiniMRP is a terrific tool whose existing workflow certainly fits into every other company I have worked at. I am all for keeping the "mini" in MiniMRP. That's why only I suggested only opening up the existing quantity cells in the "New RFQ" and "New Purchase Order" DataGrids for multi-row pastes. | |
Reply - add a comment to this topic.
You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.
|
|
|
