New SuiteAnalytics Workbook Template for Supply Chain Planning Engine (MRP/MPS)

A new out-of-the-box SuiteAnalytics workbook, Supply Chain Planning Engine Workbook, is now available under Analytics > Workbooks. It gives MRP/MPS users a queryable, tabular view of planning engine output without requiring custom saved searches or manual dataset construction.

What changed

The workbook ships with two pre-configured table views, each backed by its own dataset:

1. Planned Order Analysis

• Root record type: Planning Engine Pegging — this is the dataset's starting record, meaning all source-field paths originate from pegging rows that link a supply line to a pegged demand line.
• Key fields exposed: Supply Plan Definition, Supply Planning Run Id, Item, Location, Supply Source, Supply Start Date, Supply Date, Supply Quantity, Demand Source, Demand Date, Demand Quantity, Pegged Quantity, plus order-sizing parameters (Minimum Order Quantity, Lot Sizing Method, Fixed Lot Size, Fixed Lot Multiple) and demand/forecast settings (High Impact Late Demand Threshold, Backward/Forward Consumption Days, Past Due Forecast Days).
• Formula fields: Days Late (computed lateness) and Is Latest Supply Planning Run (boolean identifying the most recent run per plan definition).
• Default filter: Is Latest Supply Planning Run = True and Replenishment Method IN (MRP, MPS) on the Planning Repository Item Location Properties join.

2. Planning Messages

• Surfaces message type, action type, planning order type, quantity, source/target dates, and related-record links (Planned Order, Transaction, Transaction Line, Supply Change Order, Inbound Shipment).
• Includes a View Workbench column — clicking View Results opens the Planning Workbench filtered to that message's context.
• Formula field: Is Latest Supply Planning Run (same boolean filter, defaulted to true).

Multiple Units of Measure note: When the feature is enabled, all quantities in both views display in base units. There is no column toggle for alternate UOMs within the workbook itself.

Permissions required

• SuiteAnalytics Workbook — Edit level (not View; Edit is needed to open workbook templates).
• Material Requirements Planning — View level or higher.

Access to specific data rows is further governed by role-based record access and workbook sharing settings.

What to do

1. Verify the MRP feature is enabled. Navigate to Setup > Company > Enable Features > Items & Inventory (or the equivalent supply planning setup path) and confirm Material Requirements Planning is active. The workbook will not appear without it.
2. Run supply planning first. The workbook reads planning engine output tables. If no supply planning run has been executed, the views will be empty.
3. Check role permissions. Any role that needs access requires both SuiteAnalytics Workbook (Edit) and Material Requirements Planning (View+). Add these via Setup > Users/Roles > Manage Roles.
4. Review existing custom workbooks. If your team already built custom datasets against planning engine records, compare them with the shipped template. The out-of-the-box datasets may cover your requirements and are likely to be maintained across upgrades, reducing custom-object maintenance.
5. Extend with caution. You can duplicate the workbook to add columns or pivot tables, but edits to the original template may be overwritten by future releases. Clone it first.
6. UOM handling: If you rely on alternate units of measure in planning reports, be aware that this workbook shows base units only. You may need a formula field or a companion dataset to convert.

Gaps in the source

The Oracle documentation does not specify which NetSuite release introduced this workbook, nor does it state whether it is automatically provisioned or requires manual installation from the workbook template gallery. The source also does not clarify whether the Planning Engine Pegging record type is available via N/query or SuiteQL outside the workbook context — verify by running SELECT * FROM PlanningEnginePegging (or the actual table name) in the SuiteQL query tool if you plan to build integrations against this data.