Skip to main content
Setting up the ERP integration involves two people: a tenant admin who works in the Omnilinker web app, and an IT person who installs the ERP Sync agent in your network. This page lists what each of them needs.

Computer for the agent

Install the agent on a Windows computer that stays switched on and can reach your ERP database server. The agent only works while this computer runs, so a server is a better choice than a desktop that is shut down at night.

Network

The agent needs no inbound connection, and it opens no network port on its computer: it opens every connection itself. The tray app talks to the service on the same computer through Windows, not over the network.

Disk space

The agent keeps a small local database, a cached copy of its configuration and its log files on the agent computer. Log files roll over daily and the last 30 are kept.

SQL Server login

The agent connects to the ERP database with a login you choose: SQL Server authentication, or Windows authentication. With Windows authentication the service connects as the account it runs under, Local System. On SQL Server that account appears as:
  • the agent computer’s domain account, <DOMAIN>\<COMPUTER>$, when SQL Server runs on another computer. Both computers must be in the same domain, or in trusting domains.
  • NT AUTHORITY\SYSTEM, when SQL Server runs on the agent computer itself.
Give that login the rights below. If you cannot, use SQL Server authentication. For Wapro, the login needs:
  • read access to four tables: ARTYKUL, MAGAZYN, CENA and CENA_ARTYKULU. Membership of the db_datareader role gives it;
  • EXECUTE on Wapro’s own procedure dbo.Api_ProductPriceModify, which a current Wapro Mag installs. The agent’s connection test checks it (Wapro price procedure installed) and does not pass without it. SQL Server hides a procedure from a login that may not execute it, so a missing right and a missing procedure look the same;
  • optionally, read access to two more tables, JEDNOSTKA (a product’s unit) and KOD_KRESKOWY (its extra barcodes). Without them products still arrive, but without a unit and without extra barcodes, and the agent logs a warning;
  • optionally, read access to three more tables, ARTYKUL_CENA_IE, POZYCJAKONFIG and INTERFIRMAPOZYCJA. They only let the agent check whether Wapro keeps prices equal across the company’s warehouses (the check Same prices in every warehouse, see Wapro). Without them prices are read and sent as usual, and the check shows its hint;
  • optionally, read access to WFM_INT_SYSTEM. It only lets the agent warn about an old change-tracking registration (see Wapro); without it that warning is skipped;
  • optionally, read access to ARTYKUL_BLOB, Wapro’s product images, and to WAPROERP_KONFIGURACJA. They are needed only to read product images; without ARTYKUL_BLOB only reading images goes off, and everything else carries on.
dbo.Api_ProductPriceModify is the procedure the agent calls to write a price you send from Omnilinker. It runs as the connection’s ERP user for writes, who also needs Wapro’s ArtykCenSprz right; see Sending prices to Wapro. Reading prices needs only the read access above.

Rights for orders and customers

To send orders and create customers (see Orders to your ERP), the same login also needs the rights below. They are not needed to read, or to send prices. Without them the connector’s check fails at Order and customer procedures present, and orders and customers stop while everything else keeps working. The check names what is missing.
  • EXECUTE on Wapro’s own procedures that place, accept and cancel orders and create customers: dbo.Api_OrderDocumentHeaderAdd, dbo.Api_OrderDocumentPositionAdd, dbo.Api_OrderDocumentAccept, dbo.Api_CustomerAddOrModify, dbo.Api_DocumentDeliveryAddressessAddOrUpdate, dbo.RM_ZatwierdzStatusZamowienia and dbo.RM_DodajZestawNaZam_Server (adds a set line to an order). The last one is required even if you sell no sets: without it the check fails and all orders and customers stop. If the login was set up before 2026-10-20, add this grant;
  • EXECUTE on three functions those procedures use: dbo.AP_Func_PobierzParamKonf, dbo.RM_Func_PodajTypZamowienia and dbo.WAPROERP_Func_DateTimeToClarionDate;
  • INSERT on MIEJSCE_DOSTAWY, to add an order’s own delivery place (the customer’s default place is never changed);
  • UPDATE on the column ZAMOWIENIE_INTERNETOWE_ID of ZAMOWIENIE, where Omnilinker records its reference for the order;
  • UPDATE on the free-field columns POLE1 to POLE10 of KONTRAHENT, ZAMOWIENIE and POZYCJA_ZAMOWIENIA. Wapro’s procedures save these fields with dynamic SQL, which runs with the rights of whoever calls it, so the login needs them even though Omnilinker uses at most one of the fields;
  • SELECT on ZAMOWIENIE, POZYCJA_ZAMOWIENIA, KONTRAHENT, MIEJSCE_DOSTAWY, DOSTAWA, KRAJE, ARTYKUL, MAGAZYN, JEDNOSTKA, STAWKA_VAT, STAWKA_VAT_UE, FIRMA_VAT_UE, WALUTY, FORMA_PLATNOSCI and the view Api_V_CurrencyRates. db_datareader covers all of them;
  • optionally, EXECUTE on dbo.Api_CurrencyImport, so the agent can ask Wapro to download NBP exchange rates before a foreign-currency order. The download also needs the SQL Server to allow CLR and to reach the NBP site over HTTPS; without any of it the order is still sent, with a warning. Skip the grant if you leave Download NBP exchange rates off.
Orders are written in the name of an ERP user, which an administrator sets on the connection (ERP user for writes); see Monitoring. SQL Server hides an object from a login that may not use it, so a missing right and a missing object look the same: if the check fails and the right is granted, update Wapro. Have the company number (ID_FIRMY, usually 1) ready: the agent’s connection form asks for it. See Wapro.

Rights for reading orders back

To show the status, invoices and KSeF numbers of the orders Omnilinker sent (see Invoices), the login also needs SELECT on the tables below. db_datareader covers all of them; grant them one by one only if you do not use it. ZAMOWIENIE and POZYCJA_ZAMOWIENIA are already among the rights for sending orders, and without them orders stop too (see above). The other four tables are not needed to send orders: without one of them, only the read-back goes off: the PC and connector tab shows Read orders sent from Omnilinker marked switched off, the agent’s log names what is missing, and no check fails.
  • ZAMOWIENIE and POZYCJA_ZAMOWIENIA: the orders and their lines;
  • POZYCJA_DOKUMENTU_MAGAZYNOWEGO and DOKUMENT_MAGAZYNOWY: the warehouse documents that realise an order;
  • DOKUMENT_HANDLOWY, including its column KSEF_ID: the invoices and their KSeF numbers;
  • TYP_DOKUMENTU_HANDLOWEGO: the types of those documents, which tell a sale invoice from other documents;
  • optionally, MAG_SLOWNIK_STATUSOW_DOKUMENTOW: Wapro’s names for order statuses. Without it the read-back works, but the card cannot show Wapro’s own name for a status.

Rights for changing orders

To change the products of an order that is already in Wapro (see Change an order that is in the ERP), the login also needs the rights below, on top of those for orders and customers. Without them only the change is switched off: the PC and connector tab shows Change orders marked switched off, no check fails, and placing, cancelling and reading orders carry on. A change you make to an order that is in Wapro is then refused as “ERP connection not ready”.
  • EXECUTE on Wapro’s own procedures that prepare an order for change and change or remove a line: dbo.Api_OrderDocumentPrepareForModify, dbo.Api_OrderDocumentPositionModify and dbo.Api_OrderDocumentPositionDelete. Adding a line and accepting the order use procedures you granted for sending orders;
  • SELECT on POZYCJA_ZAMOWIENIA_SPRZEDAZ_TRANSGRANICZNA (the cross-border rows of a line), and on the four tables of reading orders back (POZYCJA_DOKUMENTU_MAGAZYNOWEGO, DOKUMENT_MAGAZYNOWY, DOKUMENT_HANDLOWY and TYP_DOKUMENTU_HANDLOWEGO), because Omnilinker checks whether Wapro has fulfilled or invoiced the order before it changes anything. db_datareader covers all of them.

Omnilinker access

ERP integration feature

The ERP integration is off by default. Omnilinker enables it for your organization on request. Until it is enabled, the ERP Integration menu does not appear. See Modules and feature availability.

Permissions for the tenant admin

The person who sets up the connection needs these permissions from the ERP Integration group:

The agent’s own access

You do not create a user or assign permissions for the agent. When the agent is connected with a connection code, Omnilinker creates a dedicated service account for the connection and gives its key only what the agent needs. See Create a connection.

Checklist

  • Omnilinker has enabled the ERP integration for your organization.
  • The tenant admin has the permissions listed above.
  • A 64-bit Windows computer that stays on and can reach the ERP database server.
  • A local administrator account on that computer for the installation.
  • The Windows accounts of the people who will configure the agent, to add to Omnilinker ERP Sync Operators.
  • Outbound HTTPS (port 443) to omnilinker.pl and releases.omnilinker.com from that computer.
  • Network access from that computer to the SQL Server port of your ERP database.
  • A SQL Server login with read access to the four tables and EXECUTE on dbo.Api_ProductPriceModify, and, to send orders, the rights for orders and customers, and, to read their status and invoices back, the rights for reading orders back, and, to change orders that are already in Wapro, the rights for changing orders. For Windows authentication, a login for the agent computer’s account.
  • The ERP database server name, database name and the company number.
Next, create a connection.