Define Scheduling
Explanation
Use this activity to define the execution schedule for the different jobs the server can automatically perform.
The jobs from which you can select are:
- Qualify: Fills the forecast part register with parts that qualify as forecast parts, and deletes forecast
parts that no longer qualify as parts. (Forecast parts are parts that are going to have forecasts generated for
them.)
- Uses extra parameters define from the button Change Schedule Settings
- Number of Qualification Periods how many forecast periods from the latest and back
in time should make up the qualifying range.
- Minimum Number of Transactions within Range to Qualify Parts the minimum number of
transactions in the qualifying range on a part to created as an inventory part.
- Minimum Number of Transactions within Range to Disqualify Parts the minimum number
of transactions in the qualifying range on a existing forecast part to avoid being deleted as a forecast
part.
- Aggregate daily: This job also aggregates the present period so you can see how much demand is used up to the
current day and it aggregates planned future customer demand and sales quotations planned in the forecast range.
- Uses extra parameters define from the button Change Schedule Settings
- Look for sold out days when active the aggregate daily job will compute sold out
days, quantity lost and service rates.
- Create Forecast: Aggregates demand by period through the end of the previous period, and then creates a
forecast starting with the present period. Should be scheduled to run once in the beginning of each forecast
period.
- Uses extra parameters define from the button Change Schedule Settings
- Refresh Data when active the Create Forecast job includes a complete DP Data
Refresh, this will make the job having a longer running time.
- Create in Release the forecast parts will be in status released after the Create
Forecast job is completed so users with non full access parts published will have access to the forecast
parts directly after the Create Forecast Job. e.g No Full Access user needs to manually change the parts
status for them to access the forecast parts.
- Refresh DP Data: Syncs the Demand Plan Server with the database, parts that have been deleted will get
removed and parts that have been added newly will get added to Demand Plan Server.
- Writeback DP data to file : Writes back the server forecast to the hard drive.
- Lock Write back: Locks the forecast server to prevent updates. The server is unlocked after the next forecast
run. The server also can be unlocked from the server menu.
- Refresh IPR Data: Reads all changes done in the IPR planning hierarchy, will also fetch new inventory parts
that have planning method B, and remove the ones that have got another planning method set.
- Uses extra parameters define from the button Change Schedule Settings
- Generate Delivery Schedule when activated the Refresh IPR Data job will generate a
delivery schedule according to the order and delivery days in the Delivery Route connected to the
part(s)
- Forward the maximum number of days forward to generate delivery schedules.
- Records per Part how many order cycles to generate for each part, 2 is minimum to
get the Dynamic Coverage model to work correctly.
- Minimum number of Delivery Schedule Days this is the minimum number of days to
generate delivery schedule records for.
- Example if Records per Part is set to 10 and Minimum number of Delivery Schedule Days is set to 90,
then the system will generate an accurate Delivery Schedule Days for 90 days is these 90 days does not
contain at least 10 order cycles the system will continue until 10 order cycles is reached if 10 order
cycles is not archived within Forward number of days it stops.
- Send Auto Trolleys: Send out a Trolley for all trolleys that are defined as automatic.
- Complete DP Data Refresh: Empties the entire DP Server and loads all the data from scratch. (will take much
longer time than the Refresh DP Data job)
- External Export: Performs the external export command defined in the Only External Import / Export
field.
- External Import: Imports records put in FORECAST_DAY_IMPORT view. See Import.
The different time intervals between job executions are:
- Disabled (the job will not run).
- Minute.
- Daily.
- Weekly.
- Fortnight (the job is executed once every two weeks).
- Monthly.
- Quarterly.
- Half-year.
Prerequisites
This activity requires that the Demand Planning Server General parameters be defined.
System Effects
There are no system effects until the forecast server is started.