SYSPRO Integration

SYSPRO's manufacturing focus

SYSPRO is unusual among mid-market ERPs in its concentrated manufacturing focus — the product is built primarily for discrete and process manufacturers, with deeper manufacturing-specific functionality than horizontal ERPs like Acumatica or NetSuite at similar price points. Customer concentrations include industrial machinery, electronics, food and beverage processing, and metal fabrication.

SYSPRO versions supported

• SYSPRO 8 — the current generation, with modernized web-based UI and improved API surface.
• SYSPRO Avanti — SYSPRO's web client framework, supporting the same underlying integration patterns.
• SYSPRO 7 — still deployed at many customers. Integration through e.net Solutions and database access.

Integration through e.net Solutions

SYSPRO's e.net Solutions framework is the primary integration mechanism — a comprehensive set of business object APIs covering most SYSPRO entities. For Horizon integration:

• Query business objects — for reading master data, inventory, transactions. COM-based with REST/SOAP wrappers in newer versions.
• Posting business objects — for writing back planned orders, parameter updates, forecasts.
• SYSPRO Workflow Services — for event-driven integration (notification of significant transactions).

SYSPRO-specific data objects Horizon reads

• Stock master (InvMaster) with planning attributes — ABC class, planning code, lead time, safety stock
• Stock warehouse records (InvWarehouse) for warehouse-specific overrides
• Inventory on-hand by warehouse, lot, and bin location
• Sales order history (SorDetail and related) with customer, branch, and shipment data
• Purchase orders (PorMaster and PorDetail) and receipts
• Bills of material (BomStructures, BomOperations) with phantom and reference designators
• Work centers (WipMasterFile) with capacity calendars
• Routing data (BomOperations) with operation sequences
• Supplier master (ApSupplier) with lead times and pricing

Direct database access as alternative path

For bulk historical data and analytics-style queries, SYSPRO's SQL Server database provides clean access through documented views. The Horizon implementation team typically uses a combination — e.net Solutions for transactional access, direct database views for bulk extraction of historical demand and inventory data.

SYSPRO's distinctive features

• Bill of Material with phantoms — SYSPRO's phantom handling is sophisticated, with multi-level explosion respecting phantom designations. The integration captures phantom logic for correct material requirements.
• Lot traceability — for food, pharma, and chemicals, SYSPRO's lot tracking flows through the integration so safety stock and replenishment respect lot expiry and traceability requirements.
• Forecast methods — SYSPRO's own forecast module has multiple statistical methods. Customers replacing SYSPRO's forecasting with Horizon's typically see accuracy improvements from per-SKU model selection and ML methods that SYSPRO doesn't natively provide.
• SYSPRO Espresso (mobile) — for customers using SYSPRO Espresso for shop floor and warehouse, Horizon's planning recommendations can flow into Espresso workflows.

Alternative integration path

SYSPRO environments without modern API exposure — common in older SYSPRO 7 deployments — can use scheduled SFTP delivery of CSV extracts produced by SYSPRO's report writer or custom SQL Server jobs.

Authentication and connection

• e.net Solutions: SYSPRO operator credentials with API access enabled. Network connectivity through the customer's SYSPRO web service host.
• Database access: Read-only SQL Server login with access to relevant views. Typical SQL Server authentication patterns.
• Cloud-deployed SYSPRO: Same patterns through cloud-hosted SYSPRO Application Server.

Write-back patterns

• Planned purchase orders through PorMasterUpdate or staging records
• Planned production jobs through WipMasterUpdate
• Stock master planning parameter updates (ABC code, safety stock, reorder level)
• Forecast records for SYSPRO's MRP consumption

Common SYSPRO-specific considerations

• Multi-company environments — SYSPRO's company structure (each company is a separate database) requires explicit handling. Horizon integration can pull from multiple SYSPRO companies into a unified planning view where the business model supports cross-company planning.
• Custom forms and customizations — Most SYSPRO customers have customizations through SYSPRO's customization framework. The integration captures customer-specific custom fields explicitly during configuration.
• Branch warehouse vs central warehouse models — Different SYSPRO deployments use different warehouse structures. Integration mapping happens during setup, not during runtime.
• Lot and serial tracking depth — Customers with deep traceability requirements have additional data flowing through inventory transactions. The integration captures lot-level data where customer's planning math requires it.