This will be somewhat scatter brained because I’m unsure where to start. We’re using Apps9. Currently, our system is driving purchasing and shop order reqs with start dates in the past. this makes sense to me if we’re trying to meet a certain date for production due to sales orders etc based on the (poor) information we’re feeding the system, but obviously I cannot or produce order something to arrive in March if it’s already April. Moreover, it doesn’t appear that MRP or Master Scheduling is cleaning up these back dated reqs. Clearly step one is fix the bad data, but which besides lead times? I know I need to clean this information up, but it’s unclear where - these reqs are sitting in either a proposalcreated or planned status. Any guidance on how to eat this elephant would be appreciated - it seems wholesale deleting them is an option, but given the amount of clean up utilities and other functions within IFS, that seems in-congruent with the way the rest of the system works.
Is it possible to freeze a given forecast within a specific window out of the box while allowing a horizon in the future adjust whenever ‘create forecast’ is run? Does the lead time factor into this within the client or is it just another data point? I’m aware that i could go item by item, toggle the padlock and then move forecasts per period one by one, but it’d be great if they could be locked and the standard ctrl, shift, drag functionality would work. I’d like to use the metrics within IFS so i can compare a lag-1 or a lag-3 forecast’s accuracy/bias/adjustment factor/etc.
I’ve a very simple base flow that is also our master flow which contains our current forecast. I want to take the SKU-level forecasts from the base flow and transfer it to a combined flow that consists of customers demand history effectively allowing forecasting by customer. I’m using Apps9 and DP Client 4.0.2.22. Using distribute adjustment on a top level does not carry over the seasonal models per product and it doesn’t seem to bring over the sku-level forecast either. The parameters i’m using are: target: forecast (in the new combined flow) distribution: based on forecast distribute by: part # distribute from: current base flow What am I missing? Is there a way to pull over the aggregate forecast with out doing it per sku? I realize that the granular customer level forecast may render odd but I’m less concerned with that to begin with so long as the aggregate per SKU rolls up to the currently existing forecast.
Hey folks, I’ve a combined flow consisting of a bunch of subflows organized by customer. When I attempt to use the distribute adjustment functionality in the client, it doesn’t pull in all the flows, even if there is forecast or issue history for the flow it’s not bringing in. The parameters i’m using for testing are: based on forecastdistribute by flowdistribute by periodsource product family xxxxAs an aside, we’re using Apps 9 - distribute forecast seems buggy in general in that sometimes it fails in even calculating a distribution.Is there something with my parameters that would prevent it from blowing out to all flows where a forecast or history exists? The reason this is an issue is that one of the customers it’s missing is over 20% of our overall business!
We’re currently using IFS Apps 9 and using the demand planning client. I’ve built flows per our largest customer but i’m running into a situation where i’d like to import the customer’s submitted forecast within DP while also maintaining a separate adjusted forecast (so that we can measure accuracy, etc.) I see that customer scheduling is an option for master scheduling, but I can’t seem to find a way to manage a separate adjusted forecast other than manually doing it with scenarios. Another option I’ve thought of is using collaborative forecasting and having the customer’s forecast input as a collaborative forecast. Am I missing something simple here? Do my solutions make sense?
Hi folks, I’m running into a weird situation where old collaborative forecasts from the Demand Client can’t be deleted. I’ve tried to delete trolleys, unpublish to specifics folks in IEE, nothing seems to work. Moreover, I can’t seem to find documentation on how it’s supposed to work - for whatever reason, I recall that running “create forecasts” on the Demand Server should cleanse old collaborative forecasts….but that doesn’t seem to be what’s happening. Am I off base in my memory? Is there a way to force a refresh/deletion of collaborative forecasts?
Hi folks, I’ve found .ppts for Apps10 S&OP (which has a ton of features I covet, but we’re not in a place right now to upgrade), but I’ve not found any eLearning for the screen in Apps9. I can obviously read the help screens, but they’re failry bare bones. What am I missing? I’m missing the step-by-step data reqs for S&OP as they pertain to IFS. I realize we need the demand plan (we use demand forecaster client) but I’m unclear of all the screens of necessary data to use the inborn dashboard.
Is it possible to create recipes in Engineering parts? Our business uses a mixture of both - raw materials going into recipes (stuff) and the stuff going into discrete packages for sale (things). It would be helpful to have a ‘sandbox’ to work on recipes prior to their transfer over to inventory parts and structures. I can’t seem to find any documentation on this so apologies if i’m missing something simple. We’re using apps 9.
Hi folks, I was hoping to get some suggestions on how to model a lead time appropriately: we buy items that are often harvested once or twice a year in a given period so they obviously don’t always fall within a standard # of days lead time - it’s dynamic depending on where you are within the year. I was thinking of using the unlimited supply date to model this better within our system but am I missing something? Any suggestions would be appreciated!
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.
