Depending on how the order is created and how the flow is written, Demand planner can account for ‘planned’ orders within the flow. So while there’s not a future business linkage, you could play around with how the flows are written to see if that meets your requirements. you can choose planned_date, promised_Date, planned qty, etc.Test this and see if it does what you need it to do. Another possibility is to create imports around using the Events filed or something like that - it would adjust the forecast, it would be visible to the planner in the client as additional demand that isn’t necessarily part of a stat or adjusted forecast. Moreover, depending on how granular your flows are, the events would sum up to the combined flow for a given part rendering a top level view as well.
Hi Chanaka, Yeah, forecast weighting is something i’ve encountered with other programs (INFOR Products and others). Unless these collaborative forecasts are being tracked in some way though to see who’s the most accurate, it can just be busy work vs. something that actually reduces forecast error. Something to keep in mind. What one could do, depending on how the base flow is setup, is create a combined flow with base flows representing the split of each collaboration partner. This might be messy and depending on how the data is structured (e.g. all the demand history for the flow is coming from one customer, for example) it may not work. So for example - let’s say it’s a sales channel...or sales area, or something like that. Combined Flow: Sales channelDistribute adjustment to base flows > set split % based off of customer reqsKey Acct mgrs are forecasting via complete or collab forecasting at the base flow level and their split wraps up to the top and can be adjusted from the
There’s not a simple way to go from an aggregate forecast in a base flow to replicating that forecast in a newly created (and more granular) combined flow. What can be done, however, is running distribute adjustment to get the split percentages for items and running the aggregate forecast against those and then importing it via the FORECAST_DAY table. I ultimately started over from scratch, but I could see doing this if needed.
I’m back!In reading the road map, it also looks like the Demand Client is slated to be absorbed into IEE.Often when i’m working with a sales collaborator they want to work in dollars vs. units. We’ve input avg sales price (and will probably start using period price or flow price in the near future), but there’s not a good place that sums a given time horizon. There’s the sum forecast in the metrics window, but that’s over the entire time horizon and adjustments only show if:you’re working in adjusted forecast, not collaborative the aforementioned period horizon from the demand server vs a user-defined horizon there are no metrics detailing growth/decline vs a defined historical time period based on adj demand or actual demandThis may be too much, but pie in the sky having a slicer with period start and period end that would pull in the data from the existing table in the Demand Forecast screen (or where-ever it ends up) would be useful for getting collaborator input.
Yo Chanaka, I realize that this is thread necromancy, but it would be awesome to somehow synthesize syndicated POS data and demand/shipment data within the client. Customer schedules doesn’t exactly do this as it’s production focused vs. forecasting focused. I realize that this is a big request, but the client already does so much I figured it’d be here to ask for it.
I’m not sure I fully understand your issue - you’ve touched on multiple things, so take what follows with a grain of salt. In regards to starting and stopping the server, it may revert to whatever is currently written back in the FORECAST_DAY table as I understand values that are not written back are held in memory in the client itself. Personally, I’ve only had issues with Exported Forecasts differing from the client when there is a writeback error. If there is one, it will render on the IEE Demand Server dashboard. It’s also likely that there’s an error code somewhere.Regarding whether jobs will be run if they’re scheduled in the past when you start and stop the server, I’ve never tested that. That said, when I’ve encountered a writeback error, stopped the service (we’re running it as a service) and restarted it, the error cleared.I hope this helps - I realize i’m not fully answering your question, but hopefully i’ve given you enough to start chasing down where things are breaki
A solution for the board: At one point, create forecasts did indeed erase the collaborative forecast. However, that’s no longer the case. Collab forecasts stick around and have to be cleansed from the table manually. If you are seeking to cleanse it, contact IFS support or, at your own risk:“The field COLLABORATE_FORECAST must be altered to the wanted starting value. Equal to the adjusted forecast or to 0 for example, system forecast is not possible since the values are not in the database Deleting the contents will not work I believe.Looks like a data repair to find the collaborations and set them = 0 for example. Don’t delete the records in the table - simply update them.
Thanks y’all. The delta between Apps9 and Apps10 as it relates to S&OP is huge, Majose. Currently we’re using the demand client and i’m in the process of defining our product families in a more logical (or at least agreeable) state. In terms of a crawl/walk/run, I think that Apps9 will be sufficient for at least comparing sets for a gut check. Given that we implemented Apps9 a year ago, Apps10 will be a ways off i reckon. I appreciate everyone’s willingness to help!
Shawn - thanks for the thorough reply. I realize that my question was incredibly general and as you mention, only serves to create deeper questions versus illuminating answers. That said, I’m fully aware that IFS is only doing what we’ve instructed it to do - my concern is finding the “best right starting point” in terms of a starting point to addressing the Sisyphean task of baselining our supply chain processes. You’ve offered some great suggestions so I appreciate that. The unfortunate reality is that my predecessors had no idea what they were doing whereas I know only enough to be dangerous ;). We’re a make to stock company that deals in non-configured goods - so relatively simple in terms of supply chain & customer order complexity. Your general roadmap mirrors the one I had in my head, but with much better clarity and what we’re already doing. Sometimes it’s just helpful to be validated ;) Thank you, thank you, thank you.
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.
