Integrations / ERP / SYSPRO
SYSPRO Integration Guide for Production Scheduling with SkyPlanner APS
This SYSPRO integration guide shows partners and IT teams how to connect SYSPRO 8 to SkyPlanner APS. SkyPlanner integrates with SYSPRO in both directions, using SYSPRO’s own interfaces:
- Jobs, job operations, Structures and Routings, work centers, machines, Stock Codes, stock and purchase orders flow in.
- Planned start and finish dates go back to the jobs.
- Operator timelogs can post back as labor, if you choose.
- SkyPlanner webhooks push schedule changes as they happen.
The SkyPlanner team configures the integration to your SYSPRO setup during onboarding and supports it after go-live. This guide is for partners and developers who want to take part, or to build on SkyPlanner’s documented REST API (API reference) themselves.
SYSPRO’s integration interfaces
SYSPRO gives an external scheduler two data routes:
- e.net Solutions Business Objects. SYSPRO business logic called from outside, XML in and XML out. There are three families: Query (for example WIPQBL, WIP Balance Query), Transaction or Post (for example WIPTJB, WIP Job Creation and Maintenance) and Setup for master data. Business objects apply the same validation as the SYSPRO screens and stay compatible across releases. SYSPRO’s best-practice guide is direct: “SYSPRO’s Business Objects are used to query and post data to SYSPRO.”
- SYSPRO OData Service (OData v4). RESTful, read-only access to the company and system databases and to Business Activity Queries, which are SQL views defined in SYSPRO. It is available from SYSPRO 8 2021 R2. In SYSPRO Cloud ERP, “Syspro OData is the only mechanism available when applications need access to SYSPRO data.”
Business objects are called through the e.net Communications service, using the SYSPRO WCF Service or SYSPRO Web Service.
Master Data Take On (IMPIMP) imports spreadsheets through Setup business objects, useful for a one-off master data load. SYSPRO Harmony reaches end of life on 31 December 2026, so build nothing new on it.
Authentication and licensing
- e.net logon. The integration logs on as a SYSPRO Operator with a company and receives a session GUID for later calls.
- Licensing. The operator needs the business object functional areas it calls in your SYSPRO license.
- OData. Access runs through operators configured for OData, over HTTPS.
On the SkyPlanner side, the REST API authenticates with an API token (SkyPlanner Settings > API) and is documented in Swagger/OpenAPI. The integration tutorial walks through the first calls.
Events and polling
SYSPRO sends no outbound webhooks. Electronic Signature Transaction Setup can fire triggers such as email or a VBScript when a transaction succeeds. But SYSPRO states: “It is not intended that triggers from e.net Business Objects fire VBScript triggers.”
So the SYSPRO side is polled. Business object queries or OData requests filtered to open jobs and recent changes pick up new work. The frequency is set per plant, from every few minutes for jobs to hourly for stock.
SkyPlanner sends webhooks when state or the schedule changes, so the write-back side is event-driven.
Data mapping
| SYSPRO object (interface) | SkyPlanner object | Direction | Frequency |
|---|---|---|---|
| Stock Codes, units of measure (OData or Query business objects) | Products and materials | SYSPRO → SkyPlanner | Initial load, then polling |
| Structures (components, notional parts, co-products) | Product structure, subproducts, materials per product | SYSPRO → SkyPlanner | Initial load, then on change |
| Routings: work center, setup, run, queue and move time, Maximum units | Process steps with durations, setup and teardown times | SYSPRO → SkyPlanner | Initial load, then on change |
| Work Centers (productive units, capacity) and Machines | Workstations, workstation groups, efficiencies | SYSPRO → SkyPlanner | Initial load, rarely after |
| Capacity Calendar, Shift Patterns | Shifts and non-working days | SYSPRO → SkyPlanner | Daily, or own shifts in SkyPlanner |
| Jobs and sub jobs (WipMaster), job operations, job material | Orders and jobs with due dates and material needs | SYSPRO → SkyPlanner | Polling every few minutes |
| Warehouse stock on hand per Stock Code | Stock balances | SYSPRO → SkyPlanner | Polling, hourly or on schedule run |
| Purchase orders with due dates | Purchase orders, incoming material by delivery date | SYSPRO → SkyPlanner | Polling, hourly or on schedule run |
| Job planned start and finish dates (WIPTJB, WIP Job Creation and Maintenance) | Planned start and end per job | SkyPlanner → SYSPRO | On schedule change, via SkyPlanner webhook |
| Labor Posting: setup and run time per job operation, machine, employee | Timelogs and operator confirmations | SkyPlanner → SYSPRO | Per confirmation or per shift, if chosen |
| Job Receipts (WIP Job Receipts business object) | Completed quantities | SkyPlanner → SYSPRO | Per confirmation, if chosen |
| Not in SYSPRO | Setting time matrix, tools as finite resources, alternative machines and personnel | Maintained in SkyPlanner | Set up during onboarding |
Integration patterns
1. Initial master data load. Read Stock Codes, Structures and Routings, work centers, machines and calendars through OData or Query business objects. Map work centers to SkyPlanner deliberately: a work center with four machines becomes one workstation group or four workstations.
2. Job sync. Read live jobs with their operations and material, plus open purchase orders. SkyPlanner treats ordered material as available on the PO delivery date and updates stock when the PO is marked Delivered.
Schedule live jobs only. Suggested jobs live in the MRP snapshot until MRP Job Review turns them into jobs.
3. Schedule write-back. When the engine places or moves a job, a SkyPlanner webhook triggers a post to the WIP Job Creation and Maintenance business object (WIPTJB). It sets the job’s planned start and finish dates. The business object validates the change exactly as Job Entry would.
4. Shop-floor confirmations. Operators log work with SkyPlanner Mobile Confirmations or the Production Timer, and the timelogs keep the schedule current. You choose whether actual times post back to SYSPRO. If yes, setup and run time go to Labor Posting per job operation, and completed quantities to Job Receipts. If no, labor is entered in SYSPRO as before.
5. Ownership and conflict rules. Write them down before go-live:
| Data | Owner |
|---|---|
| Stock Codes, Structures and Routings, quantities, job status | SYSPRO |
| Operation sequence, start and finish times, machine assignment | SkyPlanner |
| Setting time matrix, tool and operator requirements, alternative resources | SkyPlanner |
| Shifts and non-working days | One system, chosen in scoping |
| Labor, material issues and receipts | SYSPRO, entered there or posted from SkyPlanner timelogs |
Pick one writer of job dates. SkyPlanner needs no SYSPRO scheduling module, so it replaces Factory Scheduling, Visual APS or APS (Nexsys) as the writer of planned dates. If one of them still updates planned dates, switch that off for jobs SkyPlanner schedules. In Factory Scheduling the Job Entry option is “Update planned dates to scheduled dates.”
Typical project steps
Implementation is normally completed within weeks after onboarding starts. Before that, validate the schedule in the 30-day free trial with work centers, routings and open jobs exported from SYSPRO as CSV or Excel.
- Mapping. Fix the mapping table, ownership rules, sync frequencies and whether labor posts back.
- SYSPRO access. Create the integration operator, confirm business object licensing and enable OData where used. Test in a copy company first.
- Initial load. Stock Codes, Structures and Routings, work centers, machines, calendars.
- Job and purchase order sync. Polling with filters, paging and retries.
- Constraint setup in SkyPlanner. Setting time matrix, tools, operator counts per job and alternative machines or personnel.
- Schedule write-back. WIPTJB posts from SkyPlanner webhooks, plus labor posting if chosen.
- Parallel testing. Run SkyPlanner beside the current plan, compare dates, fix master data.
- Go-live. Switch on write-back once the data matches.
What to plan for in a SYSPRO integration
- _TMP jobs. Finite trial loads in Job Entry can create _TMP jobs in WipMaster. Filter them out on every read.
- Started operations. Forward Finite Scheduling errors on started operations that do not fit. Read operation progress into SkyPlanner before each run, so the schedule starts from work already done. Running Time Lock then freezes the next hours of work.
- Routing time units. Setup, run, queue and move time each need the right unit and basis. Queue and move time are waiting, not machine time. Convert on import or every duration is wrong.
- Subcontract operations. Offsite Days and Dock to Stock Days are elapsed time, not your capacity. Model them as time-only steps.
Who configures and supports the SYSPRO integration
- The SkyPlanner team configures it during onboarding and supports it after go-live, across the agreed business objects and OData queries. Every plant runs SYSPRO differently, and this is where that know-how goes.
- Your SYSPRO partner can take part. The partner knows your setup, custom forms and licensing, and can set up the operator and OData access alongside the SkyPlanner team.
- Your own developers can build on it against SkyPlanner’s REST API with an API token. An API token is enough to start, and the SkyPlanner team assists when needed. Integration documentation is at SkyPlanner integration docs.
SkyPlanner starts from 199 € per month with 5 workstations included, billed monthly. The integration is quoted up front for your process and needs, together with your plan. See pricing, SYSPRO finite capacity scheduling, the SYSPRO page and the ERP integrations hub.
SkyPlanner reviews from manufacturers
2 hsaved every week
“SkyPlanner has taken our production planning from Excel spreadsheets to real-time production optimization.”
Kalle Kalliomäki, Supply Chain Specialist
UTU · Electrical switchboards and switchgear
Production planning saves 2 hours of working time every week, and a new work queue reaches the line in seconds.
+90%production efficiency
“Efficiency has gone up 90% in production.”
Abdul Rucyinga, Head of IT
Laboratory & Allied · Pharmaceutical manufacturing
Production efficiency is up 90%, and a three-month optimized plan across all workstations takes under 30 minutes.
98%delivery reliability, up from about 50%
“SkyPlanner plays a decisive role in maintaining our delivery reliability.”
Hannu Lahtinen, Managing Director
KJH-Comp · Sheet-metal mechanics and contract manufacturing
Delivery reliability rose from around 50% to as high as 98%, and scheduling now needs one supervisor instead of two.
99.2%delivery reliability
“SkyPlanner has brought visibility to identifying bottlenecks and clarified production management.”
Toni Tuori, Production Manager
Piristeel · Roof safety and rainwater systems
Delivery reliability reached 99.2% this year, and scheduling saves up to four hours of working time per day.
FAQ
Does SYSPRO have an API for jobs?
Yes. e.net Solutions Business Objects query and post SYSPRO data, including WIPTJB for job creation and maintenance. The SYSPRO OData service adds RESTful read-only access to tables and Business Activity Queries.
Does SYSPRO support webhooks?
No outbound webhooks. Triggers in Electronic Signature Transaction Setup are not meant to fire from business object calls, so the integration polls SYSPRO on a schedule set per plant. SkyPlanner’s own webhooks push schedule changes as they happen.
How are planned dates written back to SYSPRO?
Through the WIP Job Creation and Maintenance business object (WIPTJB), which sets the job’s planned start and finish dates. SYSPRO validates the post with the same rules as Job Entry.
Does the integration work with SYSPRO Cloud ERP?
Yes. SkyPlanner reads Cloud ERP data through the SYSPRO OData service, which SYSPRO names the only data access route there. The SkyPlanner team sets up the write-back route with you and your SYSPRO partner during scoping.
Should a SYSPRO partner propose SYSPRO MOM Visual APS or SkyPlanner?
SkyPlanner, when the customer wants a working finite schedule in weeks. Visual APS comes with the SYSPRO MOM suite, with its own license, installed against the SYSPRO SQL Server, and MOM Workbench users need seat licenses (SYSPRO help). SkyPlanner connects through e.net Business Objects and OData, replans automatically, plans changeovers, tools, crews and material, and has unlimited users, from 199 € per month.
Can we test SkyPlanner before building the integration?
Yes. The 30-day free trial supports up to 20 workstations with CSV or Excel imports from SYSPRO, no credit card needed. Start the trial, or talk to sales to scope the integration.
