Hi @SandT, that has worked!Thank you for your help, have a good day :)Regards, William
Just on your second point @SandT, I am considering that.We will be using the access views for both the Purchase Order Line and the Supplier for Purchase Part data, so I thought having them connected with the single foreign key ID to join on would be handy, but ultimately it’s not a huge issue I suppose.
Hi @SandT,I tried this, but I’m getting an error:For context, I have the PURCHASE_ORDER_LINE_MVT data mart source enabled.
Correct, we don’t use handling units at all currently.We do in fact use the Start Picking process - for context, we’re also using Warehouse Tasks for customer order pick lists. That’s interesting though - I will suggest it to our consultant.Do you have any idea why the handling unit snapshot record wouldn’t get created for a pick list line? In most cases, it seems to exist
Hi @Kelum Pradeep Kumara I appreciate this is an old post, but we’re experiencing an issue where the “Aggregated” tab of customer order pick lists is sometimes empty. We don’t use handling units at all currently. I can’t see anything particularly out of the ordinary on the inventory part in stock records.When this issue occurs, we’re unable to pick the picklist on a WaDaCo device, but we can do it in IFS EE without any issue. (I presume this is because WaDaCo uses the view shown in the aggregated tab).Don’t suppose you have any idea what could be causing this to happen in the first place?
Hi, did you manage to resolve this?We’ve just had Update 17 deployed, and now have an issue with a custom menu and quick report using expandable parameters, which was previously working fine.
Nevermind - I found the Conditions option in the RMB Menu.
Hi, I’m using anmise’s solution here and it is working, but is there anyway of configuring this to allow multiple PO lines on one purchase order? Currently, a new PO will be created for each line in my CSV, even if the site and supplier align.Many thanks
This is solved now. For some reason, there were missing records in Warehouse Bays, Warehouse Rows, and Warehouse Tiers.
Hi @Kelum Pradeep Kumara I just tried, but still seeing the same error unfortunately.
Hi Bhagya,Thank you for the response. I had considered this, though the projected quantity for a given week takes the last weeks value into consideration, which complicates things a bit more. For example, a part might currently have an available quantity of 200. The next few weeks may look like this.Due Date Demand Supply Projected 11/10/21 100 0 100 18/10/21 50 25 75 25/10/21 100 0 -25 For the first week, the available quantity is used to calculate the projected value, which is workable. But for the following weeks, the projected quantity is calculated using the previous weeks value, which I can’t access due to it being null. Is a custom table perhaps the best way to go? Or do you think this logic can still be repeated in the data source?
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.
