After you undo the delivery, you can go back to the actual shipment screen and change to preliminary.
Regarding your second paragraph - having a warehouse worker / worker group set up as BDR in your environment will not affect the way transport tasks are consolidated. That only directly effects the creation of warehouse tasks. etc. Back to your first paragraph - your site setting is exactly how mine is set up regarding the consolidation of the transport tasks. You are consolidating based on multiple parts that meet the criteria of pulling from the same warehouse and going to the same bay WITH a common denominator of single ref 1 ( Shop order number, customer order number, etc.). Location Group, unfortunately, will always separate the transport tasks if they are different.
The purpose of a location group is to group several locations with the same location type. Therefore, you can specify one location type for each location group. This means that you will probably need one group for arrival, one for inspection, one for picking, etc. This provides for quicker handling of your inventory parts. In other words - if you have two different location groups with the same location type -IFS assumes this is two separate groups of workers doing that task.
Hi, For any purchase related parameters (min order size, std lot size, lead time, etc.) you would want to set that on the supplier for purchase part. MRP will consider those parameters. For a purchased raw part, the inventory part planning data page - safety stock is the one field that MRP should consider. The similar fields you see on the inventory part planning data page (min order size, max order size. std lot size) is related to a manufactured part type.
My organization had this similar issue, and there really is no easy way around it. We would run a script to find all the parts that need to be lot tracked that are currently on hand and that are not reserved. After that, we would count all of those parts out, turn on lot batch tracking on the master part, and then count them back in. For the parts that are reserved, it was a part by part basis.
Thanks for the response. The issue I still have is creating a count report that includes parts that are lot batch tracked. Do you know if IFS allows you to create count reports with inventory parts that have data in their lot batch field?
Sorry - I am a bit confused on the backend of that statement. If the finished goods items are in a floor stock location not in a shop order handling unit - you will have to use the Report Picking of Part Shop Order Pick List configuration since the good is not in a shop order handling unit. I hopefully can help more if you can describe the situation a little bit more. Thanks!
I do not believe it is required, but it is possible yes.
Yes there is. The inventory part default locations page will allow you to default locations for when you are doing register arrival through the desktop or when there is not a default location set in wadaco. In wadaco, if you set your default location to XXX - it will populate that when you are registering arrival regardless of what is set as the inventory parts
Yes, you can. The data collection process is REPORT_PICK_HU_SO_PICK_LIST. If the finished good is packed into a handling unit (not shipment handling unit) - you should be able to report the picking of a handling unit on a shop order pick list. You could make this a subsequent process to a warehouse task if your organization is utilizing those as well.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
