Integrations / ERP / Acumatica Cloud ERP
Acumatica Integration Guide for Production Scheduling with SkyPlanner APS
This Acumatica integration guide shows partners and IT teams how to connect Acumatica Cloud ERP (Manufacturing Edition) to SkyPlanner APS. SkyPlanner integrates with Acumatica in both directions:
- Production orders with their operations, work centers, machines, tools, shifts, stock items and purchase orders flow in.
- Planned start and end dates are written to the production order operations, and the order is firmed.
- Operator timelogs go back as labor and move entries.
- SkyPlanner webhooks push schedule changes as they happen.
The SkyPlanner team configures the integration to your Acumatica 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.
Acumatica’s integration interfaces
The integration runs on interfaces Acumatica already ships. Nothing is installed in the instance.
- Contract-based REST API. Endpoints are versioned and follow the release. The Manufacturing endpoint (for example 26.200.001 for 2026 R2) exposes
ProductionOrder,OrderOperationDetail,BillOfMaterial,WorkCenter,Machine,Tool,Shift,WorkCenterCrewSchedule,LaborEntry,MoveEntryandMaterialEntry. The Default endpoint coversStockItem,PurchaseOrderandSalesOrder. URLs follow{instance}/entity/{Endpoint}/{version}/{Entity}. - Actions on the same endpoint.
FirmProductionOrder,UndoFirmProductionOrder,ReleaseLaborEntry,ReleaseMoveEntryandReleaseMaterialEntryrun the same logic as the buttons on the screens. - OData. Any Generic Inquiry (SM208000) can be exposed over OData. A Generic Inquiry of open production operations with dates is the fastest bulk read.
- Push notifications (SM302000). Built on a Generic Inquiry or a built-in query, they post inserted and deleted rows to a URL you configure.
- Import and export scenarios with CSV and Excel providers for bulk loads.
Entities and actions are listed on Web Service Endpoints (SM207000) and in Acumatica’s REST client repository.
Authentication and limits
Acumatica uses OAuth 2.0 and OpenID Connect through client applications registered on Connected Applications (SM303010). The documented flows are Authorization Code, Implicit, Resource Owner Password Credentials and Hybrid. For a server integration, register a dedicated integration user with least-privilege roles and use Authorization Code with a refresh token, or Resource Owner Password Credentials.
Your license sets the ceiling: the License Monitoring Console (SM604000) shows the allowed API requests per minute and API users.
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.
Data mapping
| Acumatica object (endpoint / form) | SkyPlanner object | Direction | Frequency |
|---|---|---|---|
StockItem (Default; Stock Items IN202500) | Products and materials | Acumatica → SkyPlanner | Initial load, then delta |
BillOfMaterial (AM208000): materials, operations | Product structure, subproducts, materials per product | Acumatica → SkyPlanner | Initial load, then on change |
| BOM operations: Setup, Run, Machine, Queue, Finish, Move Time | Process steps with durations, setup and teardown times | Acumatica → SkyPlanner | Initial load, then on change |
WorkCenter (AM207000), Machine (AM204500), WorkCenterSubstitute | Workstations, workstation groups, efficiencies, alternative workstations | Acumatica → SkyPlanner | Initial load, rarely after |
Shift, Work Calendar (CS209000), WorkCenterCrewSchedule | Shifts and personnel capacity | Acumatica → SkyPlanner | Daily, or shifts kept in SkyPlanner |
Tool (AM205500) | Tools as finite resources | Acumatica → SkyPlanner | Initial load |
ProductionOrder with OrderOperationDetail (Planned, Released, In Process) | Orders and jobs with due dates, dispatch priority, material needs | Acumatica → SkyPlanner | Push notification or polling every few minutes |
PurchaseOrder lines (Default) | Purchase orders with expected delivery date | Acumatica → SkyPlanner | Polling, hourly or on schedule run |
| Item warehouse quantities | Stock balances | Acumatica → SkyPlanner | Polling, hourly or on schedule run |
OrderOperationDetail: StartDate, EndDate, WorkCenter | Planned start, end and workstation per operation | SkyPlanner → Acumatica | On schedule change, via SkyPlanner webhook |
FirmProductionOrder action | Locks the written dates against Acumatica APS | SkyPlanner → Acumatica | After each write-back |
LaborEntry, MoveEntry with release actions | Timelogs, completed quantities, operator confirmations | SkyPlanner → Acumatica | Per confirmation or per shift |
| Not in Acumatica | Setting time matrix, named operators, multi-operator jobs | Maintained in SkyPlanner | Set up during onboarding |
Integration patterns
1. Initial master data load. Read work centers, machines, tools, shifts and calendars first. Then read stock items and bills of material. Decide how a work center with several machines maps: one workstation group with machines as workstations, or one workstation. Acumatica’s Basis for Capacity tells you which way the plant thinks.
2. Order sync. Read production orders with their operations from the order, not from the BOM. Operations are copied to the order and planners change them there. Subscribe a push notification to a Generic Inquiry of open orders and operations, or poll it. Read open purchase order lines too. SkyPlanner treats ordered material as available on the PO delivery date and updates stock when the PO is marked Delivered.
3. Schedule write-back. For every operation the engine placed or moved, SkyPlanner writes StartDate and EndDate to the OrderOperationDetail, and the work center when work moved to an alternative. Then it calls FirmProductionOrder. Acumatica: “When you run finite scheduling of production orders, the system does not reschedule the firmed production orders.” (source)
4. Shop-floor confirmations. Operators log work with SkyPlanner Mobile Confirmations or the Production Timer. Timelogs become LaborEntry documents (time and completed quantity per operation) or MoveEntry documents (quantity only), released with the matching action. If your floor already reports in Acumatica, through Labor (AM301000) or the Shop Floor Kiosk, progress flows the other way. Pick one channel, never both.
5. Ownership and conflict rules. Write them down before go-live:
| Data | Owner |
|---|---|
| Stock items, BOMs, quantities, order status, costing | Acumatica |
| Operation sequence, start and end times, workstation assignment | SkyPlanner |
| Setting time matrix, tools, operator requirements, alternatives | SkyPlanner |
| Shifts and absences | One system, chosen in scoping |
| Labor and move transactions | Acumatica, posted from SkyPlanner timelogs or entered on the floor |
The main conflict source is Acumatica’s own APS. Rough Cut Planning or the APS Maintenance Process can recalculate dates on orders SkyPlanner scheduled. Firming each written order closes that door. Exclude scheduled orders from APS runs as well.
Typical project steps
Implementation is normally completed within weeks after onboarding starts. Before that, the 30-day free trial runs on your own data. Export work centers and open production orders with their operations from a Generic Inquiry to Excel, import them and validate the schedule.
- Mapping. Fix the mapping table, ownership rules, sync frequencies and the labor posting channel.
- Access. Register the connected application, create the integration user and roles, and confirm the endpoint version on Web Service Endpoints. Sandbox first.
- Initial load. Work centers, machines, tools, shifts, stock items and BOMs.
- Order sync. Production orders, operations and purchase orders by push notification or polling.
- Constraint setup in SkyPlanner. Setting time matrix, named operators, multi-operator jobs and alternatives.
- Write-back. Operation dates, firming and labor or move entries.
- Parallel run. Compare SkyPlanner’s dates with the current plan and fix master data.
- Go-live. Switch on write-back once the data matches.
What to plan for in an Acumatica integration
- Know which APS engine is on. Classic and Optimized store settings separately, and only one can be enabled. Check Enable/Disable Features (CS100000) before the first write-back.
- Pin the endpoint version. The version is part of the URL. A release upgrade adds a new version, so retest on each upgrade.
- Updating operations. Some operation fields are read-only over REST, and the order status matters. Test the write-back sequence for Released and In Process orders in a sandbox.
- Units and time fields. Run time is per Run Units, machine time per Machine Units. Queue and move time “affect the calculated schedule but do not occupy work center capacity.” Convert carefully on import.
- Material answers. Classic APS requires all material available in full. SkyPlanner plans against stock and incoming purchase orders by date. Agree which answer planners follow.
- API limits. Requests per minute are licensed. Use delta reads and push notifications, not full reloads.
Who configures and supports the Acumatica integration
- The SkyPlanner team configures it during onboarding and supports it after go-live. Every plant runs Acumatica differently, and this is where that know-how goes.
- Your Acumatica partner can take part. The partner knows your customizations, Generic Inquiries and roles. SkyPlanner provides the REST API, Swagger/OpenAPI documentation and webhooks.
- Your own developers can build on it against the same REST API with an API token. An API token is enough to start, and the SkyPlanner team assists when needed. Laboratory & Allied took this route on SAP Business One: its in-house IT team built the integration largely on its own, with SkyPlanner’s help.
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, so you see the full cost before you start. See how Acumatica’s own APS compares in Acumatica finite capacity scheduling, the overview on the Acumatica page, and other systems in 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.
1,000swork orders scheduled automatically
“Production is under control in a different way, and our understanding of capacity is on a completely different level.”
Hannu Ryynänen, CEO
Mamec · Industrial mixers, pumps and high-tech contract manufacturing
Thousands of work orders are scheduled automatically, with a real-time view of production for the whole organization.
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 the Acumatica API include production orders?
Yes. The contract-based REST API’s Manufacturing endpoint exposes ProductionOrder, OrderOperationDetail, BillOfMaterial, WorkCenter, Machine, Tool and labor and move entries, plus actions such as FirmProductionOrder.
Who builds the Acumatica integration?
The SkyPlanner team configures the two-way integration to your Acumatica setup during onboarding and supports it after go-live. Your Acumatica partner or your own developers can also build on SkyPlanner’s documented REST API, and an API token is enough to start.
Do we need Acumatica APS for this integration?
No. Acumatica’s own finite run is the Rough Cut Planning form, and Classic APS plans orders ending beyond 120 days at infinite capacity (source); SkyPlanner builds the fine-grained finite schedule itself from production orders, operations, work centers, machines and tools, so the integration works whether or not APS, which Acumatica says “is subject to licensing”, is enabled. Autopilot keeps the schedule current, and operators log work with Mobile Confirmations.
How do we stop Acumatica APS from overwriting SkyPlanner’s dates?
SkyPlanner firms each production order after writing its operation dates. Acumatica’s finite scheduling does not reschedule firmed orders.
Can Acumatica push changes in real time?
Yes. Push notifications (SM302000) on a Generic Inquiry post changed rows to a URL as they happen. SkyPlanner’s own webhooks push schedule changes the other way.
Which authentication should the integration use?
OAuth 2.0 through a client registered on Connected Applications (SM303010), with a dedicated integration user and least-privilege roles. The flow is confirmed for your instance during scoping.
Can we test SkyPlanner before building the integration?
Yes. The 30-day free trial supports up to 20 workstations with Excel or CSV imports from an Acumatica Generic Inquiry, no credit card needed. Start the trial, or talk to sales to scope the integration.
