How PlanetTogether APS connects to SAP Business One
Standard pre-built ERP integration
The vendor lists a standard integration for these SAP products. It imports orders, routings, resources and inventory and exports schedule results to the ERP. Business One on SQL Server or HANA is commonly on-prem, and PlanetTogether can be deployed on your servers or hosted, so confirm the topology you need.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Business One production orders and sales orders | PlanetTogether | Demand, quantities, due dates, status | Scheduled import or on demand |
| Business One BOMs, routings, work centers | PlanetTogether | Operations, run times, resources | Initial load and on change |
| Business One inventory and purchase orders | PlanetTogether | On-hand and expected supply | Each planning run |
| PlanetTogether | Business One | Rescheduled start dates and resources on production orders | Publish after schedule approval |
Setting it up
- 1Clean the master dataFix routings, BOMs, run rates and resource calendars first; APS exposes every error.
- 2Define resourcesModel work centers, shifts, setup and changeover rules in PlanetTogether.
- 3Configure the importMap ERP fields to PlanetTogether objects and select which order statuses are schedulable.
- 4Set scheduling rulesChoose priorities, optimisation rules, and which jobs are frozen.
- 5Run a shadow periodCompare APS schedules to what planners built in the same week without writing back.
- 6Enable write-backTurn on publishing of dates and resources with a restricted ERP user.
- 7Train plannersAgree who approves and publishes, and how often.
What usually breaks
- !Routings with unrealistic run times, giving schedules shop-floor staff ignore.
- !Orders released in the ERP between import and publish, creating conflicts.
- !Write-back overwriting dates a planner set manually in the ERP.
- !Material availability ignored because purchase order dates are stale.
- !Resource calendars not updated for holidays or maintenance.
- !Planning too frequently with no frozen horizon, so the floor sees constant changes.
A private AI layer across both systems
Late order explanations
A private assistant reads the schedule and ERP data and explains in plain language why an order is late, such as a constrained resource or missing material.
Master data quality scan
Find routings whose reported times deviate strongly from actuals and draft corrections for a planner to approve.
Schedule versus actual digest
Summarise yesterday's variance between planned and actual start and completion by work center.
Try it here, free
SAP Business One Production Order Checklist
A step-by-step checklist for creating, releasing, issuing to, receiving from and closing a production order in SAP Business One.
When something else fits better
- Business One's built-in MRP and a spreadsheet Gantt for small, simple shops.
- A visual scheduling add-on from the Business One partner ecosystem.
- Improving routings and dispatching discipline before buying APS.
Frequently asked questions
Does PlanetTogether write back to the ERP?
The vendor says it writes rescheduled production order start dates and resources back to the ERP. Confirm which fields and order statuses are updated in your version.
Can it run on-prem?
Business One is often on-prem. PlanetTogether offers its own deployment options, so ask the vendor which fit a restricted or air-gapped plant network.
What does an AI layer add to APS?
It explains and audits: why jobs are late, which data is wrong, how plan compares to actual. It should not publish schedules without planner approval.
Pairing documented at www.planettogether.com/aps/integrations/bydesign-integration . PlanetTogether APS is a product of PlanetTogether; Netray is independent and not affiliated with either vendor.