Skip to main content

​
What this page is for

This page shows every source Spherecast takes your data from: your ERP (Enterprise Resource Planning system - your company’s system of record) such as NetSuite, data warehouses such as Snowflake, files we pick up from an FTP server, and files your team uploads. For each source it shows what it delivers, when it runs, when data last arrived and whether it is healthy. Every plan you make rests on this data, so when something looks stale or wrong downstream, this is the first place to check.

​
Connected systems

The top of the page lists the systems your company is connected to, each as a card:
  • ERP - your system of record, such as NetSuite. It shows the Instance ID (your NetSuite account, which the icon opens), whether the connection is Active, and whether Write-back is enabled, that is whether Spherecast may send changes such as purchase orders back to it.
  • Data warehouse - such as Snowflake, Databricks or BigQuery, each with whether its connection is active.
  • Gmail - your own mailbox and the company mailbox, if you use the email automations, with their sync state and the actions to connect, sync or disconnect them. The icon on the company card explains who sees its emails.
Other connections, such as an FTP server, appear in a section of their own when you have one.

​
The Synchronizations table

Every source has one row, named by the data it delivers in the Data column. Inventory and Forecast come first. Transactions groups sales, purchase orders, transfer orders and work orders; Master data groups products, bills of materials, suppliers, supplier products and warehouses; Custom synchronizations lists the jobs that bring in other data or send data out. When several sources deliver the same data - for example inventory from NetSuite for some warehouses and from Snowflake for others - each has its own row, and the data is named on the first. On NetSuite, Products, Suppliers, Bills of materials, Purchase orders, Transfer orders and Work orders can be pulled on demand with the sync button at the end of their row. Upload rows link to the product settings page, where you upload a new inventory file.

​
Warehouses without an inventory source

The last inventory row, No source, counts the warehouses no source keeps the inventory of. Click it to list them:
  • Excluded from NetSuite inventory sync - NetSuite locations whose inventory deliberately comes from nowhere, such as mirror locations.
  • Not synced by any job - warehouses whose inventory was imported once rather than synchronized, each with when it last changed.

​
How it affects planning

Your forecasts, coverage signals and recommended orders are only as fresh as these sources. A Late or Failed source, or a warehouse your plan relies on that no job syncs, is your cue to investigate - or, on NetSuite, to pull fresh data with Sync.

​
Example

Before a planning session you see that the Snowflake 3PL inventory row is Failed; hovering shows the connection error, and its Covers list holds the ten 3PL warehouses it feeds, so you know their stock is from 15 hours ago. NetSuite inventory for your own warehouses arrived a minute ago, so you plan as usual for those and treat the 3PL stock with care until the next run at 10:00 AM succeeds.
Note: Once your data is confirmed flowing, see Writing to your ERP for sending plans back out, and Data alerts view for data problems the feeds surface.