- What moves and what needs you. ERP Integration > Overview says in one sentence whether prices, stock and orders move between Omnilinker and your ERPs, and lists what needs a person, worst first.
- Whether the PC is alive. The ERP Sync agent sends Omnilinker a heartbeat every 60 seconds. Every page names the PC that serves a connection and says whether it is online, and the connection’s PC and connector tab shows what its connector reports.
- Whether the ERP’s lists, stock and prices arrived, and how old they are. The connection’s Overview tab has a Lists from ‹ERP› card with a line for each list, and the Price levels and Warehouses and products tabs show each read’s time. See Lists and mappings. The only notification about an old read is for the stock of a warehouse your ERP manages, after 6 hours; see When ERP stock is old.
- A summary on Home. The ERP card on Home counts the agents that are online and those that need an update.
Where to look
Everything is under ERP Integration in the main menu:
Commands lists every change Omnilinker asked an ERP to make, among them the prices you send with Send to ERP and
the prices sent automatically. See Prices to your ERP.
The ERP Integration menu appears only when the ERP Integration feature is enabled for your organization. See
Modules and feature availability. The old address
/ErpIntegration opens the overview.
Overview
ERP Integration > Overview answers first. One sentence says what moves, for example “Prices and stock move between Omnilinker and Wapro Mag.”, and adds what holds something up, such as a PC that has been off since a time. When price levels are sent automatically, it says so, for example “Prices of Detal go to Wapro Mag automatically.” Beside it, each PC shows whether it is online, and the last times prices and stock were read and a send was stored. As of shows when the page was read; click it to read it again. The page then has these parts:- Needs you: what needs a person, ordered worst first by what it holds up (Holds prices, Holds orders, Your decision, Needs attention, Can wait). Each item says what happened and has a link to where you fix it, for example Open the PC, Review the handover, Open price levels or Review the products. When nothing needs a person it says “Nothing needs you.” Prices of a level sent automatically that were not written show as one item per level under Needs attention, for example “3 prices of Detal not written to Wapro Mag”, and a PC that is off counts the prices that wait to be sent automatically among what it holds.
- What flows today: one card each for Prices from your ERPs, Prices to your ERPs, Stock and Orders, with a line per connection and a link to the page behind it. On Prices to your ERPs, a level sent automatically has its own line, for example “Detal to Wapro Mag automatically”, with “Sent automatically today: 312”, what waits (“3 waiting”, or “3 waiting for BIURO-SERWER” while the PC is off) and “1 not written”.
- Connections: each connection with its office PC, what it sets and its status, and Open.
- Today: what happened today, newest first, such as prices read, a Send to ERP and whether it was stored, prices sent automatically (“Sent automatically: 312 Detal prices to Wapro Mag”, “Sent with the whole level: …”, “Sent for the handover: …”), an owner change or a PC that went offline, with All commands.
- For your account: whether Read prices from the ERP is On for your organization (it is off until Omnilinker switches it on; ask support), the ERP Sync versions your PCs run, and a link to Supported ERPs. Whether Send prices to the ERP automatically is on is shown on a connection’s Overview tab, under Ready to send prices.
Connected systems
ERP Integration > Connected systems lists your connections:
The status words are:
Above the list, Systems shows each PC’s presence, when owners last changed and, while Read prices from the ERP
is off, that prices are not compared with the ERP. The page header has Download ERP Sync, which opens
Install the agent, and Connect an ERP.
Open opens the connection. The row’s menu has:
- Edit: the connection’s name and description (needs Edit ERP Connection).
- Connect a PC: a connection code for the agent; see Get a connection code.
- Switch off or Switch on (needs Edit ERP Connection). A switched-off connection accepts nothing from its agent until you switch it on again.
- Delete (needs Delete ERP Connection). A connection that still sets a price level, a warehouse’s stock or product data cannot be deleted, and the menu says why, for example “Not yet: it sets Detal PLN. Hand it back to Omnilinker first.” Give those back to Omnilinker first.
- Who sets what: one read-only table of every scope Omnilinker shares with an ERP, with its owner and flow: your price levels in Catalog, your warehouses in Inventory, and products and orders. A level whose prices were changed in the ERP says “Differs in ‹connection›: 6 · found 14:05”. A level Omnilinker sets says “Goes to ‹connection› automatically” when it is sent automatically, and “Goes to ‹connection› with Send to ERP” otherwise. An owner is changed on the row it governs: on the connection’s page, or in Catalog > Price Levels and Inventory > Warehouses.
- Connect another ERP: a tile per supported ERP, marked Available or Pilot, which starts its setup.
Connection details
Open a connection from Connected systems or Overview to see its page. The header names the connector, shows the status and says which PC serves it and when and by whom the connection was created, for example “Wapro Mag, through ERP Sync on BIURO-SERWER · created ‹date› by Anna Kowalczyk” (only “created ‹date›” when no person can be named). Connect a PC gets a connection code. The Connection health line shows the connector’s state and when it was last checked, and, when prices were changed in the ERP on levels Omnilinker sets, on how many levels; As of reads it again. Below the header are the tabs you have permission for. Each tab has its own address, so you can bookmark or share it. Price levels shows how many price levels are mapped, and Warehouses and products shows a count when warehouses wait to be mapped or products wait for a decision.
Older links with
?tab=mappings open Price levels (or Warehouses and products for a link to products), and
?tab=agent opens PC and connector.
Overview tab
The Overview tab only reads: an owner or a mapping is changed on its row on the Price levels or Warehouses and products tab, never here. It has these parts:- How ‹ERP› works now: Receives from ‹ERP› (for example a level’s prices or a warehouse’s stock), Sends to ‹ERP› (the price levels Send to ERP writes, a level sent automatically marked “Detal, sent automatically”, and orders) and Left to another system. “Directions follow the owner. To change one, change the owner on its row; this summary only reads them.”
- Prices: how many levels need a decision, what is received, what Send to ERP stored today, what was sent automatically today (“Sent automatically today: 312”), and Ready to send prices with a count such as “5 of 5”. It lists five items, each with who can fix it: an ERP user for writes, each price level mapped once, a connector that can write prices, reading prices from the ERP, and automatic sending. The first three are what sending prices needs; while one is missing, Send to ERP marks the connection as not ready with the same words. The last two are for information only, because Send to ERP needs neither, so they always count in the “5 of 5”. While reading is off it shows an info icon, “Reading prices from the ERP is off. Send to ERP does not need it.” and “Ask Omnilinker support to switch it on.”; while automatic sending is off, “Automatic sending is off for this account. Send to ERP does not need it.” with the same ask. A table lists the price levels by flow (Received from ‹ERP›, Sent to ‹ERP› automatically, Can be sent with Send to ERP, Left to another system, Neither received nor sent) with Open price levels.
- Stock: the warehouses and who changes their stock; Warehouses and products opens the tab.
- Orders: who imports orders into the ERP, reservations, what is read back and whether The order settings are complete, with a link to the Orders tab.
- Products: how many are in the ERP and how many are linked, where each product field comes from, how products link and how new ones are created.
- The PC: ERP Sync’s version, the connector’s state and since when, and the last check, for example “12 of 12 passed”, with Steps for your IT partner and all checks.
- Lists from ‹ERP›: a line per list with when Omnilinker received it, and Refresh lists. See Lists and mappings.
- Current answers: what the ERP sets, what Omnilinker sets, who sends orders into the ERP, the ERP user for writes, the Source warehouse and the description, with See the setup. A note says what stays only on the PC: the ERP database’s server and name, the sign-in and the Windows account ERP Sync runs as.
- Delete ‹connection›: deletes the connection, or says why it cannot yet, in the same sentence as the list’s row menu (“Not yet: it sets Detal PLN. Hand it back to Omnilinker first.”). When it sets nothing, it says “It sets nothing. Deleting removes its lists, mappings and settings from Omnilinker, and its PC can no longer serve it.”
ID_UZYTKOWNIKA) and click Save; you need Change the ERP user for writes. The agent picks the
change up within about a minute. Until a user is set, it reads “Not set — price writes are refused”, Ready to send
prices lists it as missing, and no order is sent. Choose a user with no more rights in Wapro than writing needs. For
prices, give the user Wapro’s ArtykCenSprz right (the dialog’s help names it); see
Sending prices to Wapro.
The source warehouse is changed the same way, with Change next to Source warehouse; see
The source warehouse.
Without access to price levels in Catalog, the price parts say “Price levels are not shown: you do not have access to
them in Catalog.”
PC and connector tab
The PC and connector tab shows what the PC last reported. It is Omnilinker’s view of the PC, so it works from any computer. Click Refresh to read it again.- The PC card names the PC, says whether it is online, which ERP Sync version it runs (and “an update is needed” when Omnilinker requires a newer one), the connector and its state since when, whether the PC has applied Omnilinker’s last change to its settings (“Applied · Omnilinker’s last change reached it” or “Waiting for the PC to apply Omnilinker’s last change”), and when it was paired. Until a PC is connected it says “No PC is connected to this connection yet.” and offers Connect a PC.
- What it can do, by flow: the connector’s operations under Prices, Stock, Orders, Products and Other, as the connector reported them, for example Read prices, Write prices, Read stock, Place orders or Change orders. An operation the last check switched off is marked switched off.
- Checks: how many passed and when, each check Passed, Failed or Couldn’t tell, and for one that failed, the steps and who fixes it: your IT partner on the PC, Omnilinker (for example Set it for a missing ERP user for writes), or Omnilinker support. Copy the steps copies them for your IT partner. ERP Sync checks about every 10 minutes.
- What your IT partner sees on ‹PC›: the words the tray app uses for the same things, so you and your IT partner talk about the same thing.
- Technical, for support (folded): the last heartbeat, ERP Sync’s version, the settings version, the connector’s version and protocol, and its report.
- Stop this PC: Switch off ‹connection› refuses its PC until you switch it on again, and Connect another PC gets a code for a new PC, which stops this PC’s key as soon as it is used.
omnilinker.pl, or refused by Omnilinker (a key replaced by
connecting another PC, or a switched-off connection). While it is off, the tab shows the last report with its time. See
Troubleshooting.
Same prices in every warehouse. For Wapro, the Checks can list Same prices in every warehouse. It appears
when your Wapro company has more than one active warehouse and Wapro does not keep an article’s price equal across them.
Its hint says that Omnilinker reads, and sends prices to, the article’s row in the main warehouse, and how to keep the
warehouses equal: set the company’s article synchronisation (SynchroArt) to “Wspólne dane i ceny podstawowe” and
turn synchronisation on for every price level. It is information only: no operation is switched off, the connector
stays Ready and the connection is not marked as failing. See
How prices are read.
When the agent needs an update. Omnilinker can require a minimum agent version. An older agent is still online, but
the tab shows ERP Sync on the PC needs an update, with the version it runs and the one Omnilinker requires. Until it
updates, the agent reads no lists from the ERP and writes nothing to it, so prices you
send from Omnilinker wait, or expire after 24 hours. It updates itself at night unless automatic
updates are turned off on that computer. See Troubleshooting.
When sync is paused. The tab also warns when someone paused sync in the tray app of the agent’s computer: “Sync is
paused in ERP Sync on the PC, so prices sent from Omnilinker wait until someone resumes it there, or expire after 24
hours.” See Pause.
While the agent waits for an update, or while sync is paused on its computer, prices sent from Omnilinker wait as
Waiting. A price that is not written within 24 hours expires and the ERP is not changed; see
Prices to your ERP.
Commands
ERP Integration > Commands (/erp-integration/commands), and a connection’s Commands tab, list every write
Omnilinker asked your ERPs to make, with its receipt: prices sent with Send to ERP or automatically, and orders and
customers sent to the ERP. You need the ERP commands permission.
Filter by connection, by What (Everything, Prices, Orders, Customers), by Status and by Day
(Today, Last 7 days or A date), or search by SKU, ERP product, key, correlation or command id. Times are in
your organization’s time zone, and the address keeps the filters, so you can share a view.
A price command is named by its product and price level, for example GRI-0077 · Allegro PLN → Internet, with the
amount and who asked. The prices of one Send to ERP are grouped: the first shows, and ‹n› more of the same send opens
the rest in place. The prices of one automatic pass are one group too, for example Sent automatically · Detal →
Detaliczna, Sent with the whole level · … or Sent for the handover · …; their first step says Sent automatically,
Sent with the whole level or Sent for the level’s handover instead of a person.
Open a command to see its detail. It starts with what was Asked and what was Stored in ‹ERP› (or that nothing
reached it), then What happened: each step with its time, from the request in Catalog to the PC that picked it up
and the receipt. A command that waits says why (for example that the PC has been off since a time) and when it expires;
a withdrawn one says why it was withdrawn, for example “Withdrawn: Wapro Mag sets this level now.” when an owner change
gave the level to the ERP, or “Withdrawn: Wapro Mag took over this level then.” when the level has changed owner again
since. A price replaced by a newer one says “Replaced by a newer price for the same product and level before it reached
the ERP.” and “The newer price was queued at ‹time›.”, with Open the newer send; one withdrawn because the level’s
mapping changed says “Withdrawn: ‹level›‘s mapping on ‹ERP› changed.”, with Open the price levels. It suggests
sending again only while that connection does not set the level; while it does, it says “Withdrawn
before it reached ‹connection›. ‹connection› sets this level now: its prices come from there, not from Omnilinker.”
Technical, for support holds the request, the receipt and the idempotency key.
A batch of prices
From the ERP Sync release that sends prices in batches, a PC whose ERP takes them gets up to 50 prices of one price level in one command. Wapro Mag takes them; with an older agent, or another ERP, every price is still its own command. Commands shows a batch as one row, for example Detal → Detaliczna · 50 prices, with the currency and basis and who asked, or how it was sent (for example sent automatically). Under its status the row counts the prices by outcome, for example 50 prices · 48 written · 2 failed: the status says what became of the command, and each price has its own outcome. Failed and Needs checking also list a batch that holds a failed price or a price to check, and say so above the list. Searching for a price’s key finds the batch that carries it. A batch can end without running at all, for example when an older ERP Sync connector does not know batches, or when the PC loses its connection to the ERP before it starts. Its prices then go on in later commands by themselves and are written there, so the batch shows Carried on instead of Failed, with “not run here; its prices went on in other commands”, for example 50 prices · 50 carried on. It is not listed under Failed or Needs checking and does not count among the commands that failed today. A batch shows Failed only when at least one of its prices failed, needs checking or expired. Open a batch to see its level, its amounts and outcomes, and its prices in a table with Product, Asked, Stored (net / gross), Written at (PC clock) and Outcome. A price’s outcome is Written, Failed, Needs checking, Expired, Withdrawn, Waiting or Carried on:- Carried on: the price did not run in this command, for example because the batch took too long or the PC lost its connection to the ERP, and went on in a later command (“went on in command ‹id›”). Omnilinker sends it on by itself, and the product’s ERP prices and the notifications show only how it ended. The later command says “carried on from command ‹id›”, with Open the earlier command.
- “replaced by a newer price”: a newer price for the same product and level was sent before this one could go on.
- “already held by ‹ERP›, nothing written”: the ERP already had exactly this price, so nothing was written. See Sending prices to Wapro.
How long commands are kept
Old commands are deleted every night. A line under the list gives your organization’s times, for example “Price commands are kept for 30 days; the latest send of each price is kept longer.” and “Order and customer commands are kept for 365 days; the command that placed an order is kept while the order is live in the ERP or shows as deleted there.” Change opens Administration > Settings if you have Change ERP integration settings.
A batch of prices is kept, whole, as long as any one of its prices is kept, and so is a command a price went on from to
another one.
A link to a command that was deleted says “This command was not found. Older commands are removed after the time set in
Settings, except the latest send of each price and the command of an order that is live in the ERP or shows as deleted
there.” See
ERP integration settings and
How long send records are kept.
Supported ERPs
ERP Integration > Supported ERPs lists the ERPs Omnilinker connects to, readable before you create any connection. Each card says whether the ERP is Available or a Pilot, what The PC needs, the ERP Sync checks it runs, which connections it is Used by, and Connect ‹ERP›, which starts its setup. What each can do shows, flow by flow, the operations each connector declares. A connection’s own report is on its PC and connector tab. Wapro Mag is available. Subiekt nexo is shown as a pilot: its connector is not in the ERP Sync package yet, so it is not available to connect yet.Home
The ERP card on Home shows, for your active connections, how long ago the slowest agent last reported, and a summary such as Agents online: 1 of 1 · need an update: 0. It names a connection whose agent is offline, has never reported, or needs an update. Open ERP integration opens the overview. See Home.Related pages
Tray app
Watch and control the agent on the machine it runs on.
Troubleshooting
Fix an offline agent, a refused key or lists that do not arrive.