Community mailing list archives
Re: Cancel done delivery orderby
Eficent Business and IT Consulting Services, S.L.
I totally agree Eva.
Proper ATP check is essential. If your customer wants the products for next christmas and you tell him "Oh, but at this moment there's not enough stock"..... Customer could say: "Hey buddy, are you listening to me? I said next christmas!".
Confirming an order that is not to be inmediately fulfilled may not necessarily need to create procurement orders, to allow the flexibility for users to be able to change the orders if the customers require so. The MRP should only recognize the need for procurement orders to be created, based on the date when the materials are really needed. For example, a PO would be raised in december 1st, if the customer delivery date is december 23rd.
Sales Orders entered with future delivery dates, that will not be inmediately fulfilled, would be incorporated to the sales forecasts, to be used by the company in order to properly plan for the future capacity.
In terms of the customer delivery order, I agree that creating upon demand, based on the due date for delivery is the way to go, because using this approach, users are free to amend the sales orders as needed.
But I would even state that the procurement order should be created upon confirmation, but this procurement order should not confirmed until the date when the deadline to initiate the procurement is met.
On Thu, Mar 19, 2015 at 12:48 PM, Eva Pinter <firstname.lastname@example.org> wrote:
HI Jordi,The problem we have to solve there is that the confirmation does creates immediately delivery order on confirmation. This is causing so much trouble because it then requires cancellation of delivery and order, in case the customer changes his mind.What we really need is a ATP system that helps decide what orders will be fulfilled. We need the MRP to run as soon as the order has been confirmed, so that we are clear in terms of procurement, but the delivery is to be created on request if I select all the sales orders I want to deliver during the next X days. This way, I have the freedom to change the sales order without caring about the delivery and from a business point of view, there should be a cancellation fee, as the business may have purchased something specifically for the customer and stay on these goods as the customer changed his mind.The MRP also needs to be enhanced. At the moment, the scheduler can only be run for the whole company or all companies in the system. It should be possible to run the scheduler for 1. One single company 2. only one product with or without BOM explosion.RegardsHi, following up on this topic, to me a key concept to understand here is the requested delivery date set by the customer. It is expected that if I place an order where I want something to be delivered to me next month, I should be able to change my mind up to x days before the order starts to be fulfulled. More precisely, I should be able to change my mind to the point where the requested delivery date will not be met if the order is not confirmed.Perhaps the key concept is that as a procedure, orders placed with the requirement to be delivered X days ahead, and that do not require to be inmediatelly fulfilled based on the lead times of the products, should remain in 'Draft' state until the deadline for successful order fulfillment is met. And then on that date at the latest the sales users need to confirm the order if they want the order to be successfully fullfilled as per the required delivery date indicated by the customer. Even Customer Service can place a call or email to the customer X days ahead of that date notifying that the order fulfuillment will commence shortly. If the user wants to introduce changes after the deadline, then that is not possible.Remember, the sales order does not manage a required delivery date at line item level, but overall for the whole sales order (called order date). I'd say if a new date is added 'Confirmation deadline' that is calculated based on the delivery lead times of the products contained in the sales order then sales users would have visibility on the confirmation schedule.Does this make sensne to you?On Thu, Mar 19, 2015 at 11:30 AM Nuria Arranz Velazquez <email@example.com> wrote:I shouldn't laugh but it is funny.<blockquote cite="mid:CAENzJ3FrZt3vX5LamEazH=JcPdX1F_UnMW2e9J2MAaTNXPUg8w@mail.gmail.com" type="cite">
Try cancelling the order and placing a new one instead of trying to reverse what's gone through the system already. That's how I'd do it so my inventory doesn't go bananas.
Besides, it makes sense that if the customer notifies you of a change of size 3 days after placing the order they need to be aware that there will be a delay in the delivery. It doesn't hurt to make them aware that the first order has to be cancelled and the goods return because they're out already. People tends to be understanding if you give them the chance and explain things nicely.
On 18/03/15 19:42, OpenERP Master wrote:
Here is a real world example. I talk to one client and I say exactly what you all have said. You cannot do this. See my message, this is real,
This is not the capability of the software. In all versions, once you confirm you are saying to the system “I confirm this information is right”. When you import orders from your storefront or create new purchase orders you can still edit them. Only after you confirm can you not make these changes. A suggestion would be to modify your business processes to ensure changes are made before you confirm the order.
I do not think you understand the functionality of our process, there are times this would need to be adjusted, for example: human error occurred or the customer made changes after the PO was confirmed. For example I had a customer call and change her size 3 days after the order was placed. I was able to make the adjustment with the vendor but could not edit or cancel and reset to draft to revise the PO. I still believe you should be able to set to draft of reverse a transaction…this is a normal function in any fulfillment system. Can we please re-evaluate this request
On Wed, Mar 18, 2015 at 2:31 PM, OpenERP Master <firstname.lastname@example.org> wrote:
Hello!I like the video clip. Thank you. That was entertaining.
I understand all points of view very clearly, however IMO sometimes I think that people can be stuck in their ways, both sides. You have many customers complain on one hand that the process you have available stinks. You argue for technical reasons it shouldn't be allowed (not you specifically).
I think there is always a separation between developer and business what works best. What I can tell you, is that the business process that is today sucks.
2015-03-18 12:37 GMT-06:00 OpenERP Master <email@example.com>:
My module will allow you to delete a delivery order by reversing all of its effect. You can then regenerate it from sale order. This condition is possible if there are no child dependencies, if there are or the accounting period is closed then you can't do this. This would be perfect in situations where delivery order is created but goods not yet sent to customer.In my opinion and the opinion of companies I have worked with canceling a document (delivery order) by creating a separate document to return goods or same principle for invoice is time consuming, can be confusing, and involves too many clicks. It is not at all a streamlined workflow.I already have such a module that does all of this but not going to release it for a couple more weeks because it isn't completely finished and its not high priority for the people that need it.
This post only brings me 1 answer after explain in several ways to somebody that do not want understand it is making a big big mistake one time customers calls you because accounting do not match with inventories and inventories do not match with historical moves and historical move do not match with several other process (claims, crm and so on), you will receive a call like the video bellow and you will answer only "Good Luck!" because you will not face their fix on data and you will need to do for free as a warranty of you consultancy (because you insist this is the way).
But even with the joke above, IMHO just for records qhen somebody in the future read this email is that this is an edicational process not a technical ones and follow your lead is a huge mistake.
Every document has its reverse process, then either you automate the reverse process 1 by one (as lionel explain) with all the process it involve also (Fiscal cancellation and so on) then you will face a re-training not/official of your customers (as eva said) to follow simply a "new" process which should be tha same than follow the original ones.
But I just added this "For the records" for future generations ;-)
-- N. Arranz-Velazquez OpusVL Odoo Specialist Team (OOST) OpusVL Drury House Drury Lane Rugby CV21 3DE T: 01788 298 450 W: www.opusvl.com