Community mailing list archives
Re: Purchase Requisition Processby
On 12 May 2015, at 14:27, Pedro Manuel Baeza Romero <firstname.lastname@example.org> wrote:Hi, Eva, they are in spanish across multiple issues:Regards.
https://github.com/odoomrp/odoomrp-wip/issues/8052015-05-12 15:04 GMT+02:00 Jordi Ballester Alomar <email@example.com>:I agree with Eva that most of the time users do not have any idea about what product do they want. They just place their need and Purchasing gives proper shape to their request.I will put together the ideas discussed into a working Google Docs.Thanks for your feedback!!!Regards,Jordi.On Tue, May 12, 2015 at 2:49 PM, Eva Pinter <firstname.lastname@example.org> wrote:
Hi Eric,Yes, it’s a standard process to have to purchase something that does not exist in the system as a product and this could be a reason for not using the procurement as the basis for this specification.To ask user to use a “blanket product” is not an idea I would support. As it is possible to purchase without product code, why should the PR be with a product code?The standard process is:Request from the userApproval (many steps possible), based not only on the price, but also on other criteriaCreation of the Requests for quotationReception of the multiple requests for quotationIf the product does not yet exist, creation of the productCreation of the PO.Approval of the POConfirmationGoods receipt / Service receiptRegardsOn 12 May 2015, at 13:23, Caudal Eric <email@example.com> wrote:I concur. We have developed the function for one of our clients and bids are definitively not the solution.Bids are not even workable for what they should be designed for (but that is another debate...).Purchase requisition could be an object just before procurement with a workflow for approval (usually by the head of department of the user and depending on some criteria such as type of product or total amount).The tricky part I have found is that the end user usually doesnot/cannot know about the product he needs/wants so you need some kind of blanket product (parent of all possible options) that will be switch to the final product (after bid or after decision from purchaser). It is not exactly a template product either.So workflow is probably something like:1. user select a blanket product that he needs (eg: screen 17")2. approval from department3. purchaser gathers all blanket product, (might have a bid process) and create 1 or several procurements (depending on stock, prices etc.) for Screen DOLL 17" and screen SONGSONG 17"4. procurement generate PO/MO/IM etc....I can help on this topic during the Experience days.2015-05-12 19:48 GMT+08:00 Joël Grand-Guillaume <firstname.lastname@example.org>:JoëlRegards,It clearly correspond to the procurement object in Odoo. I think we should start thinking with that in mind IMO. Would we start a draft google docs for this ? May be we can also talk about that during the OCA code sprint in June ?Thanks for sharing !In my understanding, the PR in SAP is kind of "Need record", a date when it's needed and where. That is the procurement in Odo. The type of PR is in fact the route and the procurement rule linked to it. As they define it :
You use this component if you wish to give notification of requirements of materials and/or external services and keep track of such requirements.
Requisitions can be created either directly or indirectly.
“Directly” means that someone from the requesting department enters a purchase requisition manually. The person creating the requisition determines what and how much to order, and the delivery date.
“Indirectly” means that the purchase requisition is initiated via another SAP component."At least this is how SAP handles the Purchase Requisition process. And makes sense to me:http://help.sap.com/saphelp_erp60_sp/helpdata/en/5e/7eb65334e6b54ce10000000a174cb4/content.htm?frameset=/en/52/7eb65334e6b54ce10000000a174cb4/frameset.htm¤t_toc=/en/32/81b65334e6b54ce10000000a174cb4/plain.htm&node_id=41&show_children=falseRegards,Jordi._______________________________________________Hi Joël,But IMHO a Call for Bids is a purely purchasing function that responds to a strategic decision made by the purchasing department to group a certain number of requests for material and/or services, in a package that they send out to suppliers requesting for a quote. This package or Bid is result of a decision made by the Purchasing user.IMHO the process of Call for Bids is being used incorrectly in Odoo. Think of the way the MRP now creates Calls for Bids from Procurement Orders. 1 Call for Bid for each Procurement Order. If you have 10 manufacturing orders, it creates 10 Bids for the exact same product. Nonsense, because the purchasing department may want to group these 10 requests for the product into a single Bid that they send out.Now, perhaps the correct thing to do would be to use your logistic requisition, that can be initiated by an individual, or by the MRP scheduler, if the product has an attribute "Create Logistic Requisition" = True (same as with the currently used in Call for Bids, but this time is correctly used).Then using your Logistic Requisition, Purchasing department can group lines of Logistic Requisitions into a Call for Bids, a Purchase Order or even Stock Transfers. So it is the function of Purchasing to determine how to fulfill each individual item requested in a Logistic Requisition.I can see that the requirement that you now have for 1 Logistic Requisition : 1 Call for Bids is just a specific scenario for a particular business case, for example, in NGO's.What do you think? Perhaps starting with isolating the Logistic Requisition into its minimal expression (minimum dependencies) could start to define a very strong process, that can later be used in different business contexts.Regards,Jordi.JoëlRegards,That would be a first stone.That way, using this route will automatically grouped PR that make sense together. We can put some hooks in the proper place so everyone will be free to define their own business rules to know how to grouped and so on. This first module will provide a new procurement rules and method to add needs in an existing PR ar create one.2) If no PR exists, create one1) Look if an existing PR exists for the given WH, if yes, it'll add the quantity there (the same than your module you backported in v7)This new route will :What about the person wanting to make a PR create in fact a procurement in Odoo for the concerned warehouse, and put new create Route "Grouped PR" (like I suggested to do for this module : https://github.com/OCA/stock-logistics-warehouse/pull/47).Hi jordi,Just an idea, but may be interesting:
The modules that Joël is working on would capture a material request by an employee, irrespective of how will it be fulfuilled afterwards. The solution looks to me more oriented towards the sale, organizing the procurement flow before the sale one is triggered.
What I was looking for was to extend Purchase Requisitions to manage internal purchase request made by various people within the company, which is a more simple scenario.
My use cases are:
- Direct procurement: project managers that need material to complete their project. This material has not been explicitly identified in any sales order.
- Indirect procurement: employees asking for office supplies.
Would you be you are interested to fulfill this same requirement?
Looking at the community threads, I can see that internal stock requests can also be fulfilled with this module:
I have not evaulated stock_indent yet.
This feature is something I am seeking as well. I am willing to contribute funding to help the development.
I was thinking on using the stock management module to request the move and based on availability a draft would be generated.JoëlRegards,Looking forward to hear from you !In any case, your approach sounds goods because then it is generic enough to be used also with the logistic_requisition module.Any idea how to handle that ? Did you already think about it ?Hi Jordi,I'll need this feature too, that's why I'm seeing how we can work together here. Currently, the blocking point I'm facing is that a PO can only have one delivery address and may be your PR A and PR B have different !Thanks Joël for the feedback. But I have the feeling that "logistic_requisition" is prepared to fulfill a much more complex scenario. But I'm looking more closely at it now.In my scenario the basic assumption is that users raise requisitions, and a centralized purchasing department can then decide to raise a PO to fulfill multiple requisitions. I am looking at your project, and it looks like a call for bids cannot be linked to likes of different logistics requisitions. This, in my opinion, would break my essential requirement.My proposal would be as follows. In my opinion is simple, and would not break anything that exists now. (Note: instead of "Call for Bid" i will refer to a Purchase Requisition or "PR")Basic workflow:1. - User "1" creates a PR "A" and confirms it,2. - User "2" creates a PR "B" and confirms it.3. - Purchasing department reviews the requisitions and decides to create a new PR "C", and import the lines from PR's "A" and "B". Then confirms the PR.* From PR "A" and "B" you can see, for each line, that is going to be sourced by "C".* PR "A" and "B" change to state "Waiting for another Requisition". Nothing can be done in this state in "A" or "B".4a. - If PR "C" is cancelled, PR "A" and "B" change to the previous state "Confirmed".4b. - When PR "C" changes to status "PO created", the related PR's also change to "PO created".In order to handle more complex scenarios where some of the lines could not be procured, a status of the purchase requisition line would be needed, so that the requisitioner can get to know for which lines was the PO created.This would allow, for example, that the purchasing department can create Bids that group individual requirements created by users or the MRP scheduler.Look, for instance, at the MRP process creating automatically 50 bids for the same product, out of 50 different manufacturing orders. But the purchasing department just wants to issue 1 PO to the supplier!!Regards,Jordi._______________________________________________JoëlBest regards,Let me know, but I think I may have to show you those modules to have a better explanation. I don't know if they can fit your needs, but I have the feeling that it may work perfectly. If not, I'm really interested in developing a module compatible with "purchase_requisition_bid_selection" in any case, so I can even imagine contributing financially in order to achieve that. Please let me know.It's a very short summary of what we've done (as it's a huge project), but I think it really cover the use case you described.* If accepted, the sourcing done above will be trigged and the required document will be generated (PO based on FA, PO based on Framework agreement, Warehouse dispatch,..)* Once source, you create a draft SO (cost estimate) to submit to the requester for approval* Source them with various way : On Stock, On framework agreement, On Tender* Record request from requester called "Logistic Requisition" (for need of services, product or whatever).In the vertical NGO addons, you'll need to install the logistic_requisition and his dependencies. It's a set of module where you can:Also another interesting module is for better CBA process (which I'm not sure it is what oyu want, but still interesting) : https://github.com/OCA/purchase-workflow/tree/8.0/purchase_requisition_bid_selectionYou can find them here : https://github.com/OCA/vertical-ngoDear Jodri,There is I think something that may interest you, but that's a whole lot of module made for NGO's (the big project I'm working on for 2 years now).Hello Community,I'm in need of Purchase Requisition process as Wikipedia defines it (http://en.wikipedia.org/wiki/Purchase_requisition).What I'm finding is that the current "purchase_requisition" module is more oriented towards organizing a bid for a predefined set of products. 1 Bid translate to 1:N PO's.But what I'm looking for is a model where users can request the procurement of materials or services to the purchasing department, and this department can then decide to group various Requisitions to initiate a single purchase (or even a bid that would complete a number of user requisitions).That is, a model where N Purchase Requisitions can translate to 1:M Purchase Orders.Before we start the work to develop the modules to fulfill this need, I'd like to double check with others to see if there's consensus about the Purchase Requsition process.Regards,Jordi.--
Post to: mailto:email@example.com
Post to: mailto:firstname.lastname@example.org
----Eric CAUDAL+86 186 21 36 16 70--