Reference and administration

NetSuite Agriculture Configuration and Solution Scope

The Solution Console is the reference point for the rules behind the Agriculture screens. It brings together allocation settings, tolerances, spoilage ownership, prices and maintenance assumptions. Business owners should agree these values before an administrator changes them.

NetSuite Agriculture solution — Solution Console Health checks the consistency of the demonstration configuration — Solution Console Health checks the consistency of the demonstration configuration Demonstration data.

Before you begin

Identify the policy owner, approved value and effective period. Review the affected process before changing a setting; a change can alter downstream calculations immediately.

Navigation: Top-right screen dropdown → Solution Console.

Procedure

Start with Health and investigate failed checks.
Use Dimensions to check the presence and counts of source registers. Maintain the master data on its own records.
Open the relevant sidebar area: Allocation rules, Budget control, Spoilage policy, Pricing, Quality and lab, or Maintenance.
Compare the current value with the approved policy and identify the screens affected.
Have the authorised owner maintain the setting through the agreed change process, using the available Add, edit or Save control.
Recheck Health and the affected operational result after the change.

Responsibilities and follow-up

The business owner should be able to explain the rule, its effective period and its effect on the calculation. Configuration changes belong in the implementation’s change record, alongside the validation performed.

What Health checks

Check	Why it matters
Intermediate coverage	Every pool has an allocation rule
No circular path	Costs do not loop indefinitely
Rate totals	Percentage rules total 100%
Valid targets	Destination cost objects exist
Water drivers	Pivots have metered-water data
Master plans	Planted crops have a plan
Well licences	Recorded licence dates are current in the model
Close completeness	The computed close clears intermediate balances

Configuration areas

Area	What the business owner reviews	Dependent workspace
Dimensions	Farms, pivots, blocks, wells, crops, seasons and departments	All operational and cost screens
Allocation rules	Cycle, source, elements, basis, targets and effective dates	Allocation Engine and Cost Drill-Down
Budget control	Warning and Finance-routing thresholds by category	Budget Control Console
Spoilage policy	Production window and marketing share afterward	Packhouse and crop costs
Pricing	Board, budget, market and temporary approved price, approver and reason	Crop P&L
Quality and lab	Analysis master, panels and expected ranges	Roadmap laboratory workstream
Maintenance	Model groups, preventive triggers and spare-parts policy	Equipment and maintenance processes

NetSuite Agriculture solution — Allocation rule register exposes source, basis, targets and cycle sequence — Allocation rule register exposes source, basis, targets and cycle sequence Demonstration data.

NetSuite Agriculture solution — Budget tolerance settings identify the example warning and routing thresholds — Budget tolerance settings identify the example warning and routing thresholds Demonstration data.

NetSuite Agriculture solution — Spoilage policy contains the production window and marketing-share settings — Spoilage policy contains the production window and marketing-share settings Demonstration data.

NetSuite Agriculture solution — Pricing register retains the four price levels and temporary-price reason — Pricing register retains the four price levels and temporary-price reason Demonstration data.

NetSuite Agriculture solution — Maintenance settings describe model groups, preventive triggers and spare-parts policy — Maintenance settings describe model groups, preventive triggers and spare-parts policy Demonstration data.

Important notes

Health tests configuration consistency, not whether a policy is commercially appropriate. A deleted allocation rule can leave an uncovered pool even if the deletion saves. Quality and lab settings do not constitute a completed laboratory workflow; that workstream remains marked Roadmap.

Solution Scope and Implementation Roadmap

Solution Map separates the AgriOps workspaces from native NetSuite functions and the InoPeople workstream. Its state column identifies which areas can be opened in this demonstration and which remain on the roadmap.

NetSuite Agriculture solution — Solution Map identifies product ownership and availability by business area — Solution Map identifies product ownership and availability by business area Demonstration data.

Before you begin

Use the current Solution Map together with the agreed implementation scope. Confirm module availability and role access in the target account.

Navigation: Top-right screen dropdown → Solution Map.

Procedure

Identify the product layer: NetSuite, AgriOps or InoPeople.
Check the state: Open, Native NetSuite or Roadmap.
Open the available Agriculture workspace for the relevant process.
For native NetSuite functions, confirm the enabled module, account configuration and transaction procedure with the implementation team.
Treat roadmap areas as separate delivery items until the workflow has been implemented and accepted.

Responsibilities and follow-up

Training and operating procedures should follow the agreed delivered scope. A setting or a descriptive row on Solution Map is not a substitute for an accepted end-to-end process.

Areas explicitly marked Roadmap

Area	Scope indicated on the map
Laboratory and Quality	Analysis elements, sample panels and crop ranges
Dispatch and Logistics	Bill of lading, truck/gate movement and delivery variants
Van Sales and POS	Mobile selling and point-of-sale workstream
HR and Payroll / InoPeople	Separate HR product workstream on the same platform

Native ERP areas referenced

General ledger and close, accounts payable, receivables and collections, cash and bank, fixed assets, procurement, inventory and stores, sales and CRM, localisation/e-invoicing, and analytics are described on the map. This guide does not invent screen-by-screen instructions for those native areas because their transaction forms were not inspected. The agricultural handoffs to them are explained in the relevant chapters.

Important notes

The summary reports 15 working screens, while the navigation exposes 18 destinations including Solution Map and Solution Console. The guide covers those destinations. Native transaction forms and live external connectors were not tested; localisation, bank formats and integration behaviour require implementation confirmation.