Evert Bos Technical Fellow

1.The "backflush BOM materials at start": parameter = yes and I am using advanced warehousing. I am also having multiple picking rounds for one prod order because not all materials are always there at the start. I want to pick and then backflush what I have and pick and backflush the rest later. 2. This scenario is not supported in current system. I release my prod order with not all materials available yet.. No problem there. Warehouse work only generated for what I have . I complete whs work 3. Now the operator wants to start operation 10. We have backflushing at start. This is a process operation so it has a quantity. The system wants to auto flush but the picklist is created for all items in the prod bom, including the ones we don't have yet. 4.The auto backflush at start fails, the operator can't start the job 5.We need the proposal parameter that is avl when I manually create picklists. It would be set to 'picked' in our case. then we have no problem. Just like with sales order "shipping what you picked" we could at prod order do a partial backflush for what we have picked. The remainder we do another day. 6. The mfg execution prod order defaults needs a parameter "proposal" for the picklist which would solve our problem. I see this as a fundamental feature to make advanced warehousing work with production order execution functionality. But even without execution we would have the problem. If I just "Start" the prod order and want to auto flush at start. there is no way to tell the system that I want only the 'picked' items.

A production order has to be started in order to post any journals. But when I have parameters for auto post Picklist and auto post Route card after receiving a subcontract PO, there is no warning. The PO is received but no postings for the prod order of any kind are possible. we need a warning up front. The system should make it impossible to receive that PO or have a warning like this ;"Prod order not started, cannot create Journals" or something.

When working with production orders and advanced warehousing, one creates warehouse work when one releases the production order. But in case of shortage , no materials are available at all, no work is created at all. But the wave is. If I solve my shortage and want to release again, I get an error that there is already a wave for my prod order. I have to delete this prod wave first before proceeding. SUGGESTION: if the release to warehousing does not result in any work, do not create that prod wave either. Seems to have no sense to create this wave and then let it sit in status 'created". I can not pick up this old wave for my next release .Roll back the entire process, in other words.

When you are in project WBS, and you put in a requested role, you can open the resource field go to the calendar and book a project resource. This is a convenient way of staffing a project, we thought. But in the background, the system adds this reservation to the default role, showing in the fast tab project team and scheduling. This could be "team member" . I expected to see the role of the chosen resource to show there. That is the role for which I had booked the person. The default role also shows up behind the persons name if you open the resource field in the WBS task. This functionality makes no sense to me. It came back as 'designed' but I consider it a bug. Please vote for this functionality to be changed as ap. the customer is completely confused by this .

This workspace has all prod jobs lined up in the middle. It is however bad news to find out that none of these jobs show any dates. One has to personalize but that is not enough. the production order delivery date is an absolute must in this screen. Without that the user has no idea what the date is to aim for. An urgent request to add to this grid: - delivery date of the prod order - scheduled start and scheduled finish date of the operation that the job represents.

This is a rather serious flaw that needs to be addressed. We know that you can create and process a production order all the way without having a BOM. So you can make something out of nothing. Not sure whether I would allow that if it were my ERP system but we have accepted that for years. Now we have a new situation with the handheld app for advanced warehousing. the issue is the RAF transaction. The following scenario is possible. My flushing principle is "available on location" (the only sensible choice when you use advanced warehousing. It makes sure you only flush what you have picked. "start" or "finish" do not care about what you have picked) 1.After creating picking work for the prod order, for some reason forget to complete it. 2. Start the prod order. do your labor etc. 3.Do an RAF transaction on the handheld . The handheld RAF is different logic then the other ship RAF, which you will soon find out. It is hard coded to "finish" flushing. I don't have any finish flushing . But the mothership RAF would warn me that I "have not released all materials". The handheld does not. It lets me quietly RAF and even END my prod order. Result: I have created something out of nothing but now with a Prod BOM in place. Accounting is not happy. This loophole should be closed. We need the same check on "any remaining quantity in the prod bom "? as we have in the mothership RAF. That can't be hard. Right now this is a big risk.

When I release a prod order to warehouse and I don't have all the materials I get an error that mentions the LOT ID of the item that is short. With a little effort it should be possible to have this error message talk part numbers , with description, so the user knows exactly which items are short , so he can take action. The Lot - ID is an obscure field that no functional user would have to deal with.

The on hand screen should show the Unit of Measure. One should not have to look up the unit in the inventory tab of the item. IT should display clearly . The ON hand screen that shows inventory in horizontal rows, per site/ warehouse and location.