Make to order instructions

[mgerritt]

One of the toughest things we deal with in World in transmitting information throughout the order to cash process. A lot of what we do is effectively make to order. Standard information about product and customer requirements can be incorporated in print messages. But often there are requirements specific to an order. For those, customer service enters notes at both the header and line level of the sales order. That is fine for those who handle the ship advice/pick slip. But Manufacturing works from the WO, and would prefer that order specific info be on the WO. Remarks can be added to the WO, but as far as I can tell only from within the WO. I would like to have customer service enter these WO remarks (F5 Detail in the WO). The SO is generating MTO Work Orders, so there is a 'link' from the SO to the WO as soon as the SO is entered. But there does not seem to be a clean way to jump from the SO to the WO to enter the detail.

Has anyone come up with a clean, efficient, way to get order information onto the WO. It seems that being able to is a no brainer, in ISO 9001 terms this is 'contract review', and it is critical to a quality system.

 

[claitner]

You can print the Sales Order Text lines when you print the WO. See the processing options for WO Processing, R31410. Of course, you can better communicate typical or recurring customer requests via the Configurator. This has the added advantage in that it constrains the Order Entry personnel to enter orders that meet your engineering standards and production capabilities, provides a standard cost for the configuration and allows you to establish configuration pricing which can speed the quote process. If the need is to have an extreme variety of non standard customer requirements communicated to the order line, it is best to go through the design and approval process, create item numbers, enter the item numbers on the sales order line and manufacture these unique item(s) based on the unique parts lists, routings and related documentation.