API for integration

[dado-ca]

Greeting,

I see that the system has an implemented API, which is quite limited, at least judging by the documentation. Are you planning to expand the list of API endpoints? It would be desirable if data about orders, products, materials (raw materials), etc. could be pulled from the existing ERP via API, because this data certainly already lives in some other systems.

I see that it can be imported via CSV, files, but it would be good to automate these procedures via API.

Thanks

[jakub-przepiora]

Hi, and thanks for the thoughtful question - this is exactly the direction we're heading.

First, a quick clarification: the REST API is actually broader than the current documentation reflects (the docs are lagging behind the code). Under /api/v1/* there are already authenticated endpoints to read and write the core master data, not just import it via CSV:

• Products / product types - list, read, create, update, deactivate
• Materials (raw materials) - list, read, create, update, plus a bulk POST /materials/import
• Material lots - including forward/backward genealogy (traceability)
• Lines, workstations, process templates - full CRUD
• Work orders - read, accept/reject, plus scrap, anomalies and cost entries

So a fair amount of what you'd want to sync from an ERP can already be pushed in over the API today. We know the docs undersell this and are updating API_DOCUMENTATION.md to list the full surface.

On ERP integration specifically - yes, it's on the roadmap and actively being built. It's tracked in issue #21, with a work-in-progress PR (#204) adding a dedicated, ERP-agnostic layer under /api/v1/erp/*:

• POST /erp/work-orders/import - bulk import work orders using one canonical JSON contract. It reuses the same import/validation service as the CSV importer, so ERP sync and CSV share one create-and-validate path. This is exactly the "automate what we do by CSV today" case you described.
• Production and quality export endpoints - so your ERP can pull produced quantities, scrap, and quality results back out.
• Machine-to-machine auth via scoped API keys, so an integration only gets the permissions it needs.

A note on how the ERP side is delivered. The open, ERP-agnostic API layer above - the canonical contract, the generic import/export endpoints, the scoped keys - stays part of the open-source product and is free to build against. The actual connection to a specific ERP (SAP, Comarch, enova365, Microsoft Dynamics / Business Central, InsERT Subiekt, and so on) is, in most cases, delivered as a custom integration built per client e. Every ERP has its own fieldsemantics, master-data quirks and sync rules, so rather than shipping one-size-fits-nobody adapters, we map each customer's ERP to the cated engagement (with an upgrade-safeimplementation and, where wanted, an SLA). In short: the building blocks are open and self-serve; the tailored ERP connector and its ongoioffering.
You can see the currently available page: https://getopenmes.com/modules/.As a concrete example, there's alreaconnector offering bidirectional,real-time synchronization of orders,and warehouse documents - that's theshape a per-client ERP connector takes. The same page has the contact details if you'd like one built for your ERP.

To help us scope things: which ERP are you integrating, and which entities matter most first - work orders, products, or materials? Following issue #21 will keep you posted as the generic endpoints land, and if you'd like a tailored cuss a paid integration - your concrete field requirements would drive it directly.

If there's a feature or API endpoint you need that would also be useful for other users, let us know! We'd be happy to consider adding it to OpenMES. Thanks again for pushing on this - automated ERP sync is squarely in scope.

[dado-ca]

Thank you very much for the clarification, I'm glad to hear that the software is being developed in that direction.

As for the ERP we use, it is Datalab Pantheon ERP, popular in Eastern Europe. It works with MSSQL as a backend database, while API synchronization is achieved by installing the additional component PAWS or Pantheon WEB Light.

You can find more about Pantheon's PAW service on their user page https://shorturl.at/10mUa.

While part of the API documentation for the same is visible at https://paws.datalab.eu/index.html.

I am also sending you the full API documentation in JSON format for analysis if you have time to review it.

As for the data itself that it would be desirable to synchronize or pull from Pantheon to getOpenMES, these are Products, Product Components, Product LOTs and Component LOTs, Work Orders, Various Documents, Raw Material Receipt to the Warehouse and Release Documents from the Pantheon Warehouse. These are some things that would avoid manually retyping from Pantheon to OpenMes.

Thanks again, all the best.
Datalab-Pantheon-PAWS-API-Documentation.json

[JanKolo04]

@dado-ca hi, can you describe which parts of OpenMes you want to integrate with Datalab Pantheon ERP?

[dado-ca]

Of course, I will also try to explain Pantheon's logic related to production as best I can.

openMes and Pantheon integration - desirable:

Sync workorders from Pantheon. Workorders data are available throught dbo.vHF_WOExSetsItem view in Pantheon.

Manual import of products, from the tHE_SetItem table. But here it should be possible to import products from specific categories (called Classification in Pantheon, and identified by the acClassif column).

Materials, materials LOT-s and quantities, are also available in Pantheon.

However, it is specific in pantheon that the data about the final product and the data about the raw materials are kept in the same table, tHE_SetItem. The final product is actually the result of a combination of individual materials, which material and in what quantity ends up in one unit of the final product is defined in the so-called components (recipes), which are defined in Pantheon.

Perhaps I should have said that we are a company that produces bakery products. However, the same logic of production in Pantheon applies to other production companies.

Data on LOT numbers and available quantities can be extracted from vHE_SerialNoFree view.

Data of the component (recipe) of the final product is stored in the pantheon table tHF_SetPrst. The quantities of individual materials are expressed per piece of the final product. So that the total amount of material consumption is calculated as a multiple of the total number of pieces produced.

what I haven't seen in the software is warehouse management. Because, for example, when some material is used, in our case, it is withdrawn from the material warehouse in Pantheon, and when the work order is concluded, the warehouse of God's products is debited for the produced quantity. It would be good if the data on the available quantities were also visible to opnMES and, of course, synchronized.

In that case, documents for the release of materials from the raw materials warehouse, and documents for the receipt of finished products at certain warehouses, would have to be created.

[JanKolo04]

@dado-ca Hi, we finish'd up integration. You can check how it works.