How to Export from SYSPRO to Excel
how to export from syspro to excel
Also searched as
- syspro export to excel
- syspro browse export excel
- syspro report to excel
- syspro office integration excel
Short answer
The fastest way to export from SYSPRO to Excel is the export option on any browse window, which copies the rows you see to a spreadsheet. For formatted output send a report to a file or Excel from the print options, for live refreshable data use SYSPRO Office Integration, and for large or repeatable pulls query the database over SQL or ODBC.
Applies to: SYSPRO 7 and SYSPRO 8; Office Integration requires the licensed add-in; menu labels vary by version
Four ways to export SYSPRO data to Excel
- 1Browse export: open any browse window (stock codes, customers, sales orders), apply the filters and sort, then use the export or copy option on the browse toolbar to send the visible rows to Excel.
- 2Report to Excel: run the report, and in the output options choose a file or Excel format instead of printer or screen. Where the report runs through SRS, the export formats are offered in the preview.
- 3Office Integration: if licensed, use the SYSPRO add-in inside Excel to pull data with a query that refreshes on demand and respects your SYSPRO operator permissions.
- 4SQL or ODBC: create a read-only SQL login, then in Excel use Data > Get Data > From Database > From SQL Server and point it at the company database for repeatable pulls.
- 5Check that the first load matches SYSPRO by comparing a row count and a total against the on-screen figure.
- 6Format code columns such as stock code and customer as text before saving so leading zeros survive.
Which method to choose
Browse export is a one-off snapshot and is the right answer for most users who need a list this afternoon. It is limited to the columns the browse shows, so a missing column means changing the browse layout or choosing another method.
A report exported to Excel keeps the report's logic and totals, which makes it suitable for month-end packs. Because reports are built for printing, expect merged cells or headings you will want to clean up before using the data in pivots.
Office Integration and SQL are the right choice when the same extract is needed every week. They give you a refreshable connection instead of a copy that goes stale.
Pulling data with SQL into Excel
Each SYSPRO company has its own SQL Server database, with tables prefixed by module, such as InvMaster for stock, ArCustomer for customers and SorMaster for sales order headers. Use a read-only login that your DBA creates, never the application login.
In Excel choose Data > Get Data > From SQL Server Database, enter the server and database, and paste a SELECT statement under the advanced options. Keep the statement narrow so Excel is not loading millions of rows.
SELECT StockCode, Description, StockUom, ProductClass FROM InvMaster WHERE StockOnHold <> 'Y';
Data quality and security
An export leaves SYSPRO's security model behind. Once in Excel, anyone with the file can see the prices, costs and customer details in it, so apply the same controls as for the source data. For supplier and customer extracts, consider whether the file belongs on a shared drive.
Large exports can also lock browse windows or slow the server in business hours, so schedule heavy SQL pulls out of hours.
Try it here, free
SYSPRO SQL Query Generator
Generate read-only SQL Server queries against common SYSPRO tables. Fill in database and filters, then copy the code.
Common pitfalls
- !Exporting a filtered browse and forgetting the filter, then reporting a partial list as the full list.
- !Losing leading zeros or turning long codes into scientific notation in Excel. Import code columns as text.
- !Using the application SQL login in Excel. Use a dedicated read-only login.
- !Emailing exports containing cost and customer data without access controls.
- !Treating a pasted export as live data. Refresh or re-export before reporting.
How an ERP-grounded AI assistant handles this
Instead of exporting to Excel to answer each ad hoc question, ERPray lets a user ask in plain language, shows the SQL it generated against the SYSPRO database and returns the table, which can then be downloaded. It can run on-prem with a local model, so the data does not leave the network. Excel remains the right tool for pivots, modelling and sharing with people who do not use SYSPRO.
Frequently asked questions
How do I export a SYSPRO browse window to Excel?
Open the browse, apply your filters, then use the export or copy to Excel option from the browse toolbar or right-click menu. The export contains only the columns and rows the browse shows, so adjust the browse layout first if you need more columns.
Can SYSPRO data refresh automatically in Excel?
Yes, with SYSPRO Office Integration or an Excel connection to the SQL Server database. Plain exports are static snapshots. Refreshable connections need credentials and permissions set up by your administrator.
Why does Excel change my SYSPRO stock codes?
Excel guesses data types, so codes made of digits lose leading zeros and long numbers become scientific notation. Set those columns to Text before pasting, or import with the text type selected in Power Query.
Is it safe to connect Excel straight to the SYSPRO database?
It is safe only with a dedicated read-only login, limited to the tables needed, and ideally off business hours for large pulls. Never use the application login, and never write to SYSPRO tables, because that bypasses business logic and validation.
Related
SYSPRO SQL Query for Inventory On Hand by Warehouse
SYSPRO runs on SQL Server with one database per company, typically named like SysproCompanyA, and inventory is split between InvMaster for part-level data and InvWarehouse for quantities per warehouse. Join them on StockCode, filter, and read the quantity columns. Use a read-only login, never write to SYSPRO tables directly, and prefer e.net business objects for any change.
How-toSYSPRO tables list: core database tables by module and safe queries
SYSPRO stores data in SQL Server with one admin database (SysproAdmin) and one database per company (for example SysproCompanyA). Table names are module prefixed and Pascal case, such as InvMaster, SorMaster and WipMaster. Query them read-only and write only through business objects.
AdvancedSYSPRO API integration: e.net business objects, REST, EDI and Office
SYSPRO integrates mainly through e.net Solutions, a set of business objects that take and return XML, exposed through COM, .NET and web service interfaces including a REST style service in recent SYSPRO 8 releases. EDI and Office integration cover document exchange and spreadsheet work. Pick the route by direction, volume and who owns the code.
How-toSYSPRO Analytical Reports and PO Reporting
SYSPRO gives you four reporting routes for purchase orders: the standard PO reports in the Purchase Orders module, SYSPRO Reporting Services (SRS) for formatted output, SYSPRO Analytics for dashboards and trend analysis, and direct SQL against the PorMasterHdr and PorMasterDetail tables. Use standard reports for routine status, Analytics for management views, and SQL for open commitments or receipt gaps the standard reports do not show.
How-toSYSPRO reporting API: e.net, SRS server-side reporting, Crystal Reports and SRS preview problems
SYSPRO gives you three reporting routes: the e.net Solutions business object API (XML in, XML out) for programmatic data, SYSPRO Reporting Services (SRS) for designed reports run on the server, and Crystal-based or SQL-based custom reports. If the SRS preview does not work, check the services, the runtime and bitness, the SQL permissions and the client and server versions in that order.
Error fixError validating SYSPRO online profile: what it means and how to fix it
A profile validation error means the SYSPRO client or service could not confirm the operator, company, licence or database connection it was handed at logon. Check the service and licence first, then the operator and company, then the database and disk, in that order. Storage errors are usually full disks, a locked SQL file or a tempdb problem rather than a SYSPRO bug.
AI for ERPAI for SYSPRO, Grounded in Your Own Manufacturing Data
Add AI to SYSPRO without moving your manufacturing data to a public model. On-premise and private-cloud LLMs for SYSPRO in Australia, NA, and beyond.
AI for ERPNatural Language Query for ERP Data: Ask SAP, Infor, or Oracle a Question in Plain English
See how natural language query over SAP, Infor, Oracle, and NetSuite data works: grounded text-to-SQL, role-based permissions, and a visible audit trail.
AI for ERPA Private LLM Grounded on Your ERP Data
How a private LLM answers questions on your ERP data: RAG plus text-to-SQL, role-based permissions inherited from the ERP, and where each fits.
Stuck on SYSPRO?
Talk to engineers who work inside SYSPRO every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SYSPRO SQL Query GeneratorGenerate read-only SQL Server queries against common SYSPRO tables. Fill in database and filters, then copy the code.
- SYSPRO Job Costing WorksheetEnter estimated and actual material and labour for each WIP job and see cost variance per job and in total. Exports to Excel.
- SYSPRO MRP ChecklistA checklist of the master data, parameters and review steps that decide whether SYSPRO MRP output can be trusted.
ERP fixes and how-tos
- SYSPRO API integration: e.net business objects, REST, EDI and OfficeHow to integrate with SYSPRO 8: e.net business objects, web service and REST options, EDI and Office integration, with a table of which route fits which job.
- SYSPRO SQL Query for Inventory On Hand by WarehouseHow to query SYSPRO inventory on hand by warehouse in SQL Server: company database names, InvMaster and InvWarehouse joins, read-only safety and pitfalls.
- How to Add AI to SYSPRO On-Prem Without Moving Your DataReference architecture for adding a private AI assistant to on-prem SYSPRO: SQL Server read replica, e.net business objects, retrieval, local GPU and audit.
AI on your ERP
- AI for SYSPRO production and job costingHow AI reads SYSPRO WIP jobs, labor and material postings to explain job cost variances and late work orders, with read-only access and on-prem hosting.
- AI for SYSPRO, Grounded in Your Own Manufacturing DataAdd AI to SYSPRO without moving your manufacturing data to a public model. On-premise and private-cloud LLMs for SYSPRO in Australia, NA, and beyond.
Integrations
- How to use ChatGPT with SYSPROHow to use ChatGPT with SYSPRO: exporting data vs live access, custom GPT actions over a SYSPRO API, enterprise data controls, and when a private model is better.
- How to connect Power BI to SYSPROConnect Power BI to SYSPRO: SQL Server direct vs data warehouse, on-prem data gateway, manufacturing dashboards, refresh strategy and natural-language Q&A.