Supply Chain Planning Engine Workbook Setup Checklist

Supply Chain Planning Engine Workbook setup requires four separate checks: enabled features, the intended user's role permissions, sharing, and generated supply planning output. Start with Material Requirements Planning, verify both required permissions, and run supply planning before opening the workbook.

The important distinction is between account readiness and user readiness. Reviewing features does not confirm a planner's permissions, and checking permissions does not confirm that planning output has been generated. Use the checklist below to record each result separately.

Key takeaways

Feature prerequisite: Enable Material Requirements Planning and review the broader supply planning settings at Setup > Company > Enable Features.
Role permissions: The intended user's role needs SuiteAnalytics Workbook — Edit and Material Requirements Planning — View or higher.
Access: Enabled features and sharing matter alongside permissions.
Output and opening: Run supply planning, then go to Analytics > Workbooks and open Supply Chain Planning Engine Workbook.

1. Check the workbook's feature prerequisite

For administrators, the first check is whether Material Requirements Planning is enabled. It is the explicit workbook feature prerequisite. The broader supply planning settings in the next section provide setup context; they should not be confused with an unconditional list of workbook-specific requirements.

Open Setup > Company > Enable Features.
Review Material Requirements Planning under Items & Inventory.
Enable it if needed, and click Save after making changes.
Record the feature result separately from the role-access and planning-output checks.

A useful handoff entry is specific: “Material Requirements Planning enabled; feature review complete.” Avoid the broader statement “workbook ready” at this stage, because permissions, sharing, and output still need their own checks.

Likewise, finding the Material Requirements Planning permission on a user's role is not confirmation that the feature is enabled. Feature enablement and role permission are distinct readiness items, even though they share a name.

These setup requirements do not establish that the prerequisites were introduced or changed in a particular release. Treat this as a readiness checklist, not as a list of newly introduced requirements.

2. Review the broader supply planning feature settings

An account that already uses supply planning may have some settings enabled. Review the existing configuration before deciding which changes are needed. The supply planning feature-enablement path is Setup > Company > Enable Features.

Subtab or condition	Features to enable
Company	Locations
Items & Inventory	Multi-Location Inventory; Advanced Inventory Management; Material Requirements Planning
If using NetSuite Manufacturing	Assembly Items; Advanced Bills of Materials; Work Orders

Click Save after making changes.

Read the table in two parts. Material Requirements Planning is the explicit workbook prerequisite. The remaining entries supply the broader supply planning setup context, with the manufacturing selections applying if you use NetSuite Manufacturing.

For a practical review, distinguish settings that were already enabled from settings changed during preparation. That record helps the administrator explain what was checked without implying that a feature change also generated planning results.

Manufacturing teams should include the conditional manufacturing selections in their review. Teams not using NetSuite Manufacturing should not turn that conditional row into an unconditional workbook requirement.

3. Verify both permissions on the intended user's role

Review the role the intended user will actually use to open the workbook. Successful access under an administrator's role does not confirm readiness under another role.

Permission	Required level
SuiteAnalytics Workbook	Edit
Material Requirements Planning	View or higher

Both permissions are required. A generic approval such as “analytics access checked” is less useful than recording each permission and its required level.

For example, suppose an administrator can open the workbook but a planner asks whether their own access is ready. The next useful check is the planner's intended role: does it have SuiteAnalytics Workbook at Edit, and does it have Material Requirements Planning at View or higher? Repeating the administrator's opening test does not answer those questions.

A suggested permission-review record is:

Intended user and role identified.
SuiteAnalytics Workbook checked at Edit.
Material Requirements Planning checked at View or higher.
Any unresolved permission question assigned for administrator review.

This is a handoff aid, not an additional NetSuite prerequisite. Its purpose is to make the access review specific enough that another person can understand what was actually verified.

4. Review sharing and access to needed data

Permissions are not the only access consideration. Enabled features and sharing also matter. If a user cannot access needed data, ask an administrator to review the intended user's role permissions and sharing settings.

Keep this review tied to a concrete question: what data does the user need to access? That is more actionable than an undifferentiated request to “fix access.”

Use these review prompts:

Are you reviewing the intended user's role rather than a different test role?
Are both required permissions present at the specified levels?
Have sharing settings been reviewed for the access the user needs?
Has feature enablement been checked separately?

Consider a user whose role has both required permissions but who still cannot access needed data. The permission check is useful evidence, but it is not enough to declare the setup complete. The administrator should continue the permissions and sharing review rather than treating those two permission entries as a complete access diagnosis.

These are review prompts, not a click-by-click sharing configuration procedure. Keep the sign-off centered on whether the intended user's access has been checked.

For related reading outside this checklist, see the Planning Engine Messages Dataset readiness checklist. Keep its review separate from this workbook's readiness decision.

5. Run supply planning to generate output

Run supply planning to generate planning output. Feature enablement and permission checks do not replace this step.

This is the clearest place to separate access preparation from output preparation. An administrator may finish reviewing features, permissions, and sharing while the planning-output task remains outstanding. Record that distinction rather than marking the whole workbook ready prematurely.

For example, consider this handoff:

Material Requirements Planning is enabled. The intended role has both required permissions. Sharing has been reviewed. Supply planning has not yet been run to generate output.

The remaining action is explicit: run supply planning. Another permissions review would not replace that action.

As a coordination aid, identify who will own the output-generation task and record when it has been completed. This avoids a handoff in which each person assumes someone else has run planning. It does not add a new workbook requirement; it makes the existing requirement visible.

Keep adjacent reading separate from the readiness steps:

Neither reference replaces the instruction to run supply planning and generate the output required here.

6. Open the workbook and complete the handoff

After the feature, permission, sharing, and output reviews, go to Analytics > Workbooks and open Supply Chain Planning Engine Workbook.

Use the following as a final sign-off record rather than another round of configuration instructions:

Readiness area	What to confirm
Features	Material Requirements Planning is enabled; applicable supply planning settings have been reviewed.
Intended role	SuiteAnalytics Workbook is at Edit; Material Requirements Planning is at View or higher.
Sharing and access	Sharing and access to needed data have been reviewed for the intended user.
Planning output	Supply planning has been run to generate output.
Workbook opening	Supply Chain Planning Engine Workbook has been opened from Analytics > Workbooks.

Only mark a row complete when that check has actually been performed. If something remains outstanding, name the unresolved item instead of using a blanket “ready” status.

Administrators should focus on feature enablement, permissions, and sharing. Supply planners and workbook users should confirm the required permissions and that supply planning has been run. Manufacturing teams should contribute the manufacturing-specific feature review where applicable.

The resulting handoff should answer two different questions: has the environment been prepared, and has the intended user's readiness been checked? Keeping those questions separate makes the checklist more useful than confirmation that someone, under some role, could open the workbook.

FAQ

What permission levels does the workbook require?

The intended user's role needs SuiteAnalytics Workbook at Edit and Material Requirements Planning at View or higher. Both are required; neither replaces the feature, sharing, or output checks.

Why might access remain unresolved after both permissions are checked?

Access also depends on enabled features and sharing. When needed data is inaccessible, ask an administrator to review the user's role permissions and sharing settings.

Must supply planning run before opening the workbook?

Yes. Run supply planning to generate planning output, then open Supply Chain Planning Engine Workbook from Analytics > Workbooks.