Integrations / ERP / Divalto infinity
Divalto Integration Guide for Production Scheduling with SkyPlanner APS
This Divalto integration guide shows partners and IT teams how to connect Divalto infinity to SkyPlanner APS. SkyPlanner integrates with Divalto in both directions, using Divalto’s own REST services:
- OF and séquences OF, gammes, nomenclatures, articles, centres de charge, postes de travail, ressources, opérateurs, outillages, stock and supplier orders flow in.
- Planned start and end dates go back to every OF and séquence, with a new centre or poste when work moves to an alternative.
- Operator time and completed cycles can post back too, if you choose.
Divalto’s integration interfaces
Divalto infinity gives an external scheduler three building blocks on its API platform:
- RecordSql (native REST). Reads Divalto tables through declared query files (DHOQ). This is the read route for OF, séquences, gammes, articles, postes and stock. A new query declaration can take up to ten minutes to take effect (Divalto RecordSql settings).
- WEBSERVICE_INFINITY (REST). Divalto business web services. Each call is a JSON body with the action WEB_SERVICE_INFINITY, the access token and a parameter string naming the business action, the dossier and the data (call format). Production actions include create_dataxml (file drop for the production scrutateur), integration_dt (create technical data: components, séquences, ressources, outillages), stock queries and article creation (production actions).
- The production scrutateur. A file watcher in Divalto production that imports XML files. create_dataxml delivers a base64 file to it. Import types include GG_DATES_ORDO for planned dates, GG_TEMPS_IMPORT for time, GG_FIN_DE_CYCLE for completed cycles, CO_MES_IMPORT for MES data and GG_COMPOSANT_OM for component consumption (create_dataxml).
Divalto’s SOAP service is no longer supported on the platform, so build on REST only.
Authentication
- Divalto side. The integration posts a user and password to the Authent/Auth endpoint of the Divalto API gateway, with an account created in DLMT. It receives an access token that Divalto states is valid for forty-five minutes, so the connector renews it on a timer. The token travels in the JSON body of each business call, not in an HTTP header (Divalto auth).
- SkyPlanner side. The REST API authenticates with an API token in the Authorization-Token header (SkyPlanner Settings > API) and is documented in Swagger/OpenAPI. The integration tutorial walks through the first calls.
Events and polling
Divalto’s webhooks are inbound: an external system calls a Divalto webhook to start a process, and Divalto states that a webhook is not meant to return data (Divalto WebHooks). Divalto sends no outbound events.
So the Divalto side is polled. RecordSql queries filtered to open OF and recent changes pick up new work. The frequency is set per plant, from every few minutes for OF to hourly for stock.
SkyPlanner sends webhooks when state or the schedule changes, so the write-back side is event-driven.
Data mapping
| Divalto object (interface) | SkyPlanner object | Direction | Frequency |
|---|---|---|---|
| Articles, article characteristics (RecordSql) | Products and materials, product properties | Divalto → SkyPlanner | Initial load, then polling |
| Nomenclatures (components) | Product structure, subproducts, materials per product | Divalto → SkyPlanner | Initial load, then on change |
| Gammes: séquences, opérations standard, times, ressources, outillages | Process steps with durations, setup and teardown times, tools | Divalto → SkyPlanner | Initial load, then on change |
| Ateliers, centres de charge, postes de travail | Workstations, workstation groups, efficiencies | Divalto → SkyPlanner | Initial load, rarely after |
| Opérateurs and habilitations | Personnel and allowed workstations | Divalto → SkyPlanner | Initial load, then on change |
| Poste calendars | Shifts and non-working days | Divalto → SkyPlanner | Daily, or own shifts in SkyPlanner |
| OF (BF) and séquences OF (BH) with due dates and components | Orders and jobs with due dates and material needs | Divalto → SkyPlanner | Polling every few minutes |
| Stock per article and depot | Stock balances | Divalto → SkyPlanner | Polling, hourly or on schedule run |
| Supplier orders with delivery dates | Purchase orders, incoming material by delivery date | Divalto → SkyPlanner | Polling, hourly or on schedule run |
| GG_DATES_ORDO: OF start and end (BF.PLANDEBDH, BF.PLANFINDH), séquence start and end (BH.PLANDEBDH, BH.PLANFINDH), CENTRE and POSTE | Planned start and end per job and step, assigned workstation | SkyPlanner → Divalto | On schedule change, via SkyPlanner webhook |
| GG_TEMPS_IMPORT: time per séquence | Timelogs and operator confirmations | SkyPlanner → Divalto | Per confirmation or per shift, if chosen |
| GG_FIN_DE_CYCLE: completed cycles | Completed quantities | SkyPlanner → Divalto | Per confirmation, if chosen |
| Not in Divalto | 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. Declare the RecordSql queries and read articles, nomenclatures, gammes, centres de charge, postes, opérateurs, outillages and calendars. Map centres to SkyPlanner deliberately: a centre de charge with four postes becomes one workstation group with four workstations.
2. OF sync. Read open OF with their séquences and components, plus open supplier orders. SkyPlanner treats ordered material as available on the PO delivery date and updates stock when the PO is marked Delivered. Read the principal OF and its sub-OF together, since Divalto rejalonne only the principal OF.
3. Schedule write-back. When the engine places or moves a job, a SkyPlanner webhook triggers a create_dataxml call. The file is a GG_DATES_ORDO document with, per OF, the dossier, establishment and OF number, the planned start and end date, and per séquence its number, planned start and end, and the centre and poste if work moved to an alternative (GG_DATES_ORDO format). Divalto’s scrutateur imports it into the OF header and séquence lines.
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 time posts back to Divalto. If yes, time goes as GG_TEMPS_IMPORT files and completed cycles as GG_FIN_DE_CYCLE files. If no, time is entered in Divalto’s MES as before.
5. Ownership and conflict rules. Write them down before go-live:
| Data | Owner |
|---|---|
| Articles, nomenclatures, gammes, OF quantities and status | Divalto |
| Séquence order, start and end times, poste assignment | SkyPlanner |
| Setting time matrix, tool and operator requirements, alternative resources | SkyPlanner |
| Shifts and non-working days | One system, chosen in scoping |
| Time, consumption and completions | Divalto, entered there or posted from SkyPlanner timelogs |
Pick one writer of OF dates. SkyPlanner replaces Opcenter APS and manual rejalonnement as the writer of planned dates. If Opcenter APS is in use, switch its import off for OF that SkyPlanner schedules, since both use GG_DATES_ORDO.
Typical project steps
Implementation is normally completed within weeks after onboarding starts. Before that, validate the schedule in the 30-day free trial with postes, gammes and open OF exported from Divalto as CSV or Excel.
- Mapping. Fix the mapping table, ownership rules, sync frequencies and whether time posts back.
- Divalto access. Create the integration account in DLMT, declare the RecordSql queries and activate the production scrutateur. Test on a test environment first.
- Initial load. Articles, nomenclatures, gammes, centres, postes, opérateurs, outillages, calendars.
- OF and supplier order sync. Polling with filters, paging and retries.
- Constraint setup in SkyPlanner. Setting time matrix, tools, operator counts per job and alternative postes or personnel.
- Schedule write-back. GG_DATES_ORDO through create_dataxml from SkyPlanner webhooks, plus time 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 Divalto integration
- Scrutateur settings. create_dataxml files land only when the production scrutateur is active, with the MES box and an “Interfaces” path set in the Production dossier.
- Token renewal. The Divalto access token expires after a short time (see Authentication). Renew it before each batch of calls.
- Query declarations. New or changed RecordSql queries take a few minutes to activate. Declare them before the initial load.
- Principal and sub-OF. Divalto rejalonne only the principal OF. Schedule sub-OF as subproducts, so the parent waits for its components.
- Article characteristics. Divalto keeps scheduling properties of an article in ten characteristic fields. They map well to SkyPlanner product properties for the setting time matrix and “Allow similarity”.
Who configures and supports the Divalto integration
- The SkyPlanner team configures it during onboarding and supports it after go-live, across the agreed RecordSql queries and web service actions. Every plant runs Divalto differently, and this is where that know-how goes.
- Your Divalto partner can take part. The partner knows your dossier, surcharges and settings, and can set up the DLMT account, the queries and the scrutateur 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, Divalto finite capacity scheduling, the Divalto 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.
100%delivery reliability since 2021
“SkyPlanner gives us visibility into capacity and makes planning predictable.”
Dan Berglund, COO/CFO
Opes Corporation · Chemical and food manufacturing
Delivery reliability has been 100% for the entire time SkyPlanner has been in use, since 2021.
Fewerstoppages from material shortages
“The value SkyPlanner brings us is that it is a tool that works in daily use, especially for setting delivery dates.”
Tommi Männistö, Production Planning Manager
Eskomatic · Contract machining
Automatic load scheduling gives more accurate delivery dates, and production stoppages caused by material shortages have fallen sharply.
FAQ
Does Divalto have an API for manufacturing orders?
Yes. RecordSql reads OF, séquences and other tables over REST, and the WEBSERVICE_INFINITY service runs business actions such as create_dataxml and integration_dt for production.
Does Divalto support webhooks?
Divalto webhooks are inbound only and do not return data. The integration polls Divalto through RecordSql on a schedule set per plant, and SkyPlanner’s own webhooks push schedule changes as they happen.
How are planned dates written back to Divalto?
Through a GG_DATES_ORDO XML file sent with the create_dataxml action. It carries planned start and end dates for each OF and each séquence, and a replacement centre or poste when work moves. Divalto’s production scrutateur imports it.
Does the integration need Opcenter APS?
No. SkyPlanner does the finite scheduling and writes the planned dates itself. If Opcenter APS is in use today, SkyPlanner takes over as the single writer of OF dates.
Should a Divalto partner propose Opcenter APS or SkyPlanner?
SkyPlanner, when the customer wants a finite schedule running in weeks that keeps itself current. Opcenter APS in Divalto runs when the planner starts it and exchanges files through a Windows folder (Divalto docs). SkyPlanner connects over Divalto’s REST services, 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 Divalto, no credit card needed. Start the trial, or talk to sales to scope the integration.
