The quick answer
Go to Transactions > Supply Planning > Refresh Planning Repository > Schedule and click New Planning Repository Refresh Schedule. Choose the Transfer Type and a Date Range that starts at the oldest open transaction, optionally pick the Supply Plan Definitions to launch afterward, then enter a Name, Next Date, Next Time, Recurrence Frequency and Repeat Every. Click Save. Nothing refreshes until the first run time.
The screenshots show sample data. Person and company names are fictional. Use your own dates, times and supply plan definitions when following the steps.
Before you start
In this example, a supply planner wants the planning repository refreshed every night at 3:00 am, so MRP and the Planning Workbench start each morning from a current snapshot. The account has two supply plan definitions, Main Plant MRP and Spare Parts MRP, and the oldest open transaction is dated 03/09/2026.
The repository is a snapshot of planning data as of its last refresh. It does not update continuously, so a repository that is a day old plans against yesterday's demand and supply. Refresh Planning Repository itself refreshes it once, on demand. The Schedule option repeats a refresh on a timetable. You need a role with access to supply planning, and menu labels can differ by release and role.
01. Open the Schedule list
Go to Transactions > Supply Planning > Refresh Planning Repository > Schedule. The Planning Repository Refresh Schedule list shows the saved schedules with the columns Id, Name, Recurrence Frequency, Repeat Every, Last Executed, Next Date and Internal ID. It is empty here. Click New Planning Repository Refresh Schedule.
02. Choose the transfer type and date range
Under Transfer Type, leave Complete Refresh selected. A complete refresh reloads all eligible item setup and transaction data, so nothing edited since the last refresh is missed. Net-Change Refresh loads only what changed since the last refresh, and it is the only choice that turns on Refresh Options, where you can limit it to Item Setup or include transactions as well. Which type suits a nightly schedule depends on how long a complete refresh takes in your account.
Set the Date Range. NetSuite warns that there are open transactions in past periods and shows the oldest transaction date, 03/09/2026. Enter Date From 03/09/2026 so no open transaction is left out, and Date to 12/31/2030. Days in the Past and Days in the Future show the range relative to today, 217 and 1,541. NetSuite uses the relative days for the later scheduled runs, so the range moves forward with the date. The range is not the planning horizon. Each supply plan definition sets how far forward it plans.
03. Choose the supply plan to launch
Leave Scope on Global Refresh, which refreshes all eligible planning items and locations. Scoped Refresh refreshes only what the selected supply plan definitions need. Under Supply Plan Definitions, select Main Plant MRP. This list is optional. Each definition you select launches after the refresh completes successfully, so the plan results are ready in the morning. Leave it empty to refresh the repository only.
04. Fill in the schedule
In the Schedule section, enter Name Nightly Planning Refresh, Next Date 10/13/2026 and Next Time 3:00 am. An overnight time lets the refresh finish outside working hours. Leave Recurrence Frequency on Daily and Repeat Every on 1, which repeats every day. Leave End Recurrence On empty so the schedule keeps running, and leave Inactive unchecked. Name, Next Date, Next Time, Recurrence Frequency and Repeat Every are required.
05. Save the schedule
Click Save. A Confirmation banner says the Planning Repository Refresh Schedule is successfully saved, and the schedule opens as a record with the values you entered. Last Executed is empty because nothing has run yet. Saving only stores the schedule. The first refresh starts at the Next Date and Next Time.
06. Check the list
Click Back to return to the Schedule list. The new schedule is there: recurrence DAILY, repeat every 1 and next date 10/13/2026 3:00 am, with an empty Last Executed column. Click Edit on the row to change the timetable, or check Inactive to pause the schedule without deleting it. After the first run, Last Executed shows when it ran, and you can check the refresh on the Planning Repository Event Log and the launched supply plan on the Supply Planning Event Log.
Common questions
What is the difference between Refresh Planning Repository and its Schedule?
Refresh Planning Repository refreshes the repository once, when you click Refresh data. A schedule saves the same kind of request and repeats it on a timetable, so nobody has to remember to run it.
Should I schedule a Complete Refresh or a Net-Change Refresh?
A Complete Refresh reloads all eligible item setup and transaction data. It is more thorough and usually slower. A Net-Change Refresh loads only what changed since the last refresh, and can be limited to Item Setup. Some teams schedule a Complete Refresh nightly when it fits the overnight window. Others schedule a Net-Change Refresh nightly and run a Complete Refresh periodically. Choose based on how long a complete refresh takes in your account.
What date range should I use?
Start Date From at or before the oldest open transaction date that the form shows, so no open transaction is left out, and end Date to well past the horizon your plans use. The range is not the planning horizon. Each supply plan definition sets how far forward it plans.
Can the refresh launch a supply plan afterward?
Yes. Select one or more Supply Plan Definitions on the schedule. Each launches after the refresh completes successfully. Leave the list empty to refresh the repository only.
Can I refresh twice a day?
A schedule is one recurrence, such as daily at one time. To refresh at a second time, create another schedule with a different Next Time. Avoid scheduling refreshes so close together that one is still running when the next starts.
Does saving the schedule refresh anything?
No. Saving only stores the schedule. The first refresh runs at the Next Date and Next Time.