Skip to content
onagero

Analyzing abas ERP: tools for what the standard does not show

abas is common in one-off and variant manufacturing. Many companies have built lists and analyses around the ERP that are maintained by hand. Onagero replaces exactly these lists with tools that update themselves.

  • Read only
  • No change to your ERP
  • Connection included in the pilot
  • GDPR ready

In short

Onagero reads abas data through a route your IT releases, such as an existing interface or a scheduled export, and builds internal tools on your server from it. It writes nothing into the ERP and does not replace any screen. We set up the connection with your IT during the getting-started phase.

Possible ways to the data

Which one fits for you we clarify with your IT before the contract.

Existing interface

If your abas already delivers data to other systems, Onagero can use the same route read-only.

Scheduled export

A regular export of the required data into a file or database.

Data store

Where abas data already flows into a data warehouse, Onagero reads from there.

What your IT provides

  • a read-only route to the data the workflow needs
  • a short alignment with your abas contact
  • a server or virtual machine in your network

Good to know

Which route is possible with your abas version and your operating model, we clarify with your IT before the contract. We do not promise anything we have not seen there.

Turning abas ERP data into a foundation to build on

What stays with you, what Onagero makes of it, and what the language model gets to see.

Onagero creates an analysis copy of the needed data on your server and describes it in the data map: the meaning of each column, relationships, origin and review status. Your people build on that.

In development, the copy holds no personal data. Released applications read from a live view only what their roles allow.

The data path at Onagero Your systems feed, over a read only connection, into a masked analysis copy on your server. Your people build internal tools from it with Onagero. Only the released, masked parts of a request go to the model provider. Your server, your network ERP BDE and MES Excel, files Analysis copyNames masked OnageroYour people build Internal toolwith roles per person Live view, only what thetool may read Model provider, external What goes out is only what a request needs: released and masked. The databasestays in your building. The data path at Onagero, top to bottom Your server, your network ERP BDE, MES Excel Analysis copyNames masked OnageroYour people build Live view, released Internal toolwith roles per person Model provider, external Only what a request needs, released and masked. The database never leaves your building.
The path of your data: platform, analysis copy and tools on your server; only masked parts of single requests go to the language model. Data security in detail

Questions about connecting to abas ERP

Does this work with abas in the cloud?

If there is a read-only route to the data, such as an interface or an export, yes. We check that before the contract.

Can info systems be replaced?

Onagero does not replace abas screens. It makes sense for analyses that are produced by hand outside the ERP today.

Does Onagero write into abas?

No. Tools read.

What does the connection cost?

Connecting the sources for your first problem is part of the getting-started phase and is stated in the quote.

Which problem would
your team solve first?

Show us a real process. We will show you how it could look with Onagero.

Book a demo →

Check first whether a pilot fits: fit check in 2 minutes →