Wapro

​

What the connector reads

​

Product details

​

Which products are created automatically

​

How stock is read

• When. While at least one warehouse of the connection is mapped (see Lists and mappings), the agent reads the whole stock every 5 minutes, counted from the end of the previous read. With no warehouse mapped it reads it once a day.
• How little it disturbs Wapro. The agent reads in short pages and slows down when Wapro is busy: a page that takes more than about 2 seconds makes the next one smaller and is followed by a pause. It waits at most 5 seconds for a lock and then tries again later, and it never reads uncommitted data.
• What it sends. It compares each read with the last one it sent and uploads only the products and warehouses whose figures changed, so a quiet Wapro sends almost nothing. A stock line that disappears from Wapro is sent as 0. A complete set goes up once a day, which also corrects anything missed.
• Stock that Wapro does not list. A product that is not in Wapro’s last complete set in a warehouse shows 0 there, marked “not in the ERP’s last list”.
• Paused or updating. A paused agent reads no stock; see the tray app.

​

The company number

​

How products are identified

• Spaces at the start and end of the index are ignored. Nothing else is: abc-1 and ABC-1 are two products.
• An article whose index is empty, or only spaces or other white space, is not a product and is left out.
• The product’s code in Omnilinker is its index. By default, Omnilinker links an ERP product to the catalog product whose SKU equals that code; the connection can also link by EAN. See Link products.
• The product’s ERP key is the lowest article ID (ID_ARTYKULU) among its rows, removed rows included. It stays the same when you change the index on all of the product’s rows to one that no other product has, deactivate or remove a row, or add a warehouse, so a link survives those changes.
• A product is active when at least one of its rows is active for external systems (AKTYWNY_DLA_SYS_ZEW = 1) and not marked removed (FLAGA_STANU = 5).

• If the changed rows include the one that holds the key, the link follows the changed rows. It takes their new code, and the rows that kept the old index appear as a new product with no link.
• If the changed rows do not include it, the link stays where it was and the changed rows appear as a new product.

• A link whose key is still on the list stays with the product listed under that key and takes that product’s index as its code.
• A link whose key is no longer on the list moves to the product on the list that carries its code, but only when exactly one product does and that product has no link yet. Otherwise it stays, and it shows under Links to products that are no longer on the ERP’s product list until you unlink it (Unlink; see Products no longer in the ERP).

​

How prices are read

• Which row. An article has one row per warehouse (see How products are identified). The connector reads the price of the product’s main row: its active row in the connection’s source warehouse, or the active row with the lowest number when the source warehouse has none. It ignores the prices on the article’s other warehouse rows. This is also the row that a price you send is written to. See The source warehouse.
• What it sends. The net and the gross price as Wapro stores them, to four decimals, with the currency of the row. Wapro leaves the currency of a price in PLN blank, and the connector sends PLN for it. A price in another currency is sent in that currency: Wapro converts it only on a document, at that day’s rate, so Omnilinker converts nothing.
• What it skips. A row whose net and gross are both 0, a row with a missing amount, and a product with no active row. Omnilinker reads a skipped price as no price, and never as 0.
• Which unit. The price of the article’s base unit. A sale in another unit costs the price times the unit’s factor in Wapro, which the connector does not apply; prices for other units and quantity tiers are not read.
• How little it disturbs Wapro. As for stock: short pages, a pause when Wapro is slow, at most 5 seconds’ wait for a lock, and never uncommitted data. It compares each read with the last one it sent and uploads only the prices that changed. A price that disappears from Wapro is marked as gone, not set to 0.
• Paused or updating. A paused agent reads no prices; see the tray app.

​

Sending prices to Wapro

• The connection’s ERP user for writes (see Overview tab). Wapro checks that user’s right to change selling prices (ArtykCenSprz) in the warehouse of the row it writes. Choose a user with that right and no more rights than writing needs, not Wapro’s administrator.
• Execute rights on dbo.Api_ProductPriceModify and read rights on the price rows (CENA_ARTYKULU) for the agent’s SQL login; see SQL Server login.

• To the product’s one row described in How products are identified, net or gross as you sent it; Wapro’s other amount is calculated with the product’s sales VAT. The product must already have a price row on that level: the procedure changes a price and never creates one.
• Not to a level Wapro calculates from another level: Omnilinker refuses it before sending.
• Not for a unit other than the base unit or with a minimum quantity.
• In the row’s own currency; Wapro converts nothing.
• Wapro’s default price marker (Cena domyślna) never moves.

​

How product images are read

• Which images. A product’s images are the ARTYKUL_BLOB rows whose catalog index (INDEKS_KATALOGOWY) matches the index of one of the product’s rows in your company, ignoring upper and lower case, as Wapro itself shows them. So two products whose index differs only in case share their images. An image of another company is never read.
• The main image is the one marked as the default (DOMYSLNE). If several are marked, the oldest of them; if none is, the oldest image. The others follow in the order they were added, never by name. The image’s name (NAZWA) becomes its file name in Omnilinker.
• Shop and auction flags (DOSTEPNE_ABSTORE, DOSTEPNE_AUKCJE) are read, but filter nothing yet: every image of the product is taken.
• Changes. The agent compares the images about every hour and reads them in full once a day. A new, replaced or deleted image, a new name or a moved main mark is noticed at the next comparison. Wapro’s own image editor can replace an image’s contents while keeping its ID and, sometimes, its exact size; such a change is found by a daily check at 2:00 at night (the agent’s computer’s time), which fingerprints the images on the SQL Server. That check needs SQL Server 2016 or newer: on an older server the tray app’s Troubleshoot shows Daily check of image contents: Off (SQL Server older than 2016) as a warning, and only an image of exactly the same size goes unnoticed.
• Images kept in a folder. Wapro can keep the images added in its desktop program in a folder instead of the database (disk mode). Omnilinker does not read that folder: those images do not reach Omnilinker, are never treated as deleted, and Troubleshoot shows Where Wapro keeps product images: In an image folder (disk mode) as a warning. Images stored in the database still arrive, in either mode. To tell the mode, the connector reads WAPROERP_KONFIGURACJA (or INTERFIRMAPOZYCJA and POZYCJAKONFIG); without access to them it assumes database mode.
• Images without data. Wapro’s “reduce the database size” empties the images’ data but keeps the rows. Such an image is listed without data, and Omnilinker keeps the image it already has as it was.
• The load. Image data is read one image at a time, in pieces, and uploaded at most 30 MB a minute by default, so a first read of a large catalog takes hours. Nothing is read while the agent is paused. After every 50 images, while the agent is writing a price or an order to Wapro, the uploads wait for it to finish, up to 30 seconds.

​

What it writes to your database

• An order is a customer order, placed with Api_OrderDocumentHeaderAdd, Api_OrderDocumentPositionAdd and Api_OrderDocumentAccept, and RM_DodajZestawNaZam_Server for a set line, all in one transaction: either the whole order is saved, or nothing is. With Book a reservation in ‹connection› on (the default), it reserves stock in the warehouse of the order’s source. Omnilinker’s reference for the order (OMNI-…) is written to the order’s internet order id, and the channel order id and buyer login to the free field you chose on the Orders tab.
• A customer is created with Api_CustomerAddOrModify only when no existing customer matches. Omnilinker’s key goes to the free field you chose. It never changes an existing customer.
• A delivery place. The order’s delivery address is added to the customer’s delivery places as a place of its own with Api_DocumentDeliveryAddressessAddOrUpdate, after one plain INSERT into MIEJSCE_DOSTAWY; a matching place is reused. For a parcel locker the place is the locker’s own address, with InPost’s operator SHIPX, when Allegro gave the address. The customer’s default delivery place never changes.
• A cancel goes through RM_ZatwierdzStatusZamowienia, which also releases the reservation.
• A change to the products of an order already in Wapro (see Change an order that is in the ERP) goes through Api_OrderDocumentPrepareForModify, Api_OrderDocumentPositionDelete, Api_OrderDocumentPositionModify, Api_OrderDocumentPositionAdd and Api_OrderDocumentAccept, all in one transaction. Wapro itself refuses nothing for an order it has fulfilled, invoiced or closed, so the connector reads the order first and declines the change, writing nothing, when the order is fulfilled, partly fulfilled, invoiced, closed or cancelled, when someone changed its lines in Wapro since Omnilinker last sent them, or when it has a set line. It never edits a set line, and it leaves the delivery line and the order’s other data as they are.
• Exchange rates, if you leave Download NBP exchange rates on: before a foreign-currency order, the connector calls Wapro’s own Api_CurrencyImport, which fetches the National Bank of Poland’s tables the way Wapro does. It never writes a rate itself. The download needs the SQL Server to allow CLR, to trust Wapro’s download component and to reach api.nbp.pl over HTTPS. When any of it is missing the download fails with a warning in the order’s receipt (ERP Integration > Commands), and the order is placed on the tables Wapro already has, if they are recent enough (see Currencies).
• The free fields. POLE1 to POLE10 are saved by Wapro’s procedures with dynamic SQL; the connector fills the customer key and the channel order id, and leaves your other fields as they are. Fields 6 and 7 are never used, because Wapro stores them incorrectly.

​

Removing the old registration

-- Removes the change-tracking registration an earlier Omnilinker agent left in a Wapro database: the WFM_INT_SYSTEM
-- row whose Opis is OMNILINKER, its subscriptions and its unread change rows. Nothing else: another system's rows are
-- never touched, and no table, trigger or column is changed. Run it once, in the Wapro database, as a login that may
-- delete from the WFM_INT tables. It removes everything or nothing: if it finds no such registration, or more than
-- one, it stops with an error and changes nothing. While it runs, saves in Wapro wait (its triggers read the
-- subscription rows this script deletes), so run it when nobody works in Wapro, for example after hours.

SET XACT_ABORT ON;
SET NOCOUNT ON;

BEGIN TRANSACTION;

DECLARE @found TABLE (Id_Systemu bigint NOT NULL);

INSERT INTO @found (Id_Systemu)
SELECT Id_Systemu
FROM dbo.WFM_INT_SYSTEM WITH (UPDLOCK, HOLDLOCK)
WHERE CAST(RTRIM(LTRIM(Opis)) AS nvarchar(50)) COLLATE Latin1_General_BIN2 = N'OMNILINKER';

IF (SELECT COUNT(*) FROM @found) <> 1
BEGIN
    ROLLBACK TRANSACTION;
    THROW 50000, N'Expected exactly one Omnilinker registration (WFM_INT_SYSTEM.Opis = ''OMNILINKER''); found none or more than one. Nothing was removed.', 1;
END;

DECLARE @id bigint = (SELECT Id_Systemu FROM @found);

-- The tables whose changes it was subscribed to, and the ones earlier agents subscribed, in case a subscription was
-- already removed while its change rows were left behind.
DECLARE @tables TABLE (NazwaTablicy varchar(100) NOT NULL PRIMARY KEY);

INSERT INTO @tables (NazwaTablicy)
SELECT DISTINCT NazwaTablicy
FROM dbo.WFM_INT_SYSTEM_TABLICE
WHERE Id_Systemu = @id;

INSERT INTO @tables (NazwaTablicy)
SELECT t.NazwaTablicy
FROM (VALUES ('ARTYKUL'), ('CENA'), ('CENA_ARTYKULU'), ('MAGAZYN'), ('KOD_KRESKOWY'),
             ('KATEGORIA_ARTYKULU'), ('KATEGORIA_ARTYKULU_TREE')) t (NazwaTablicy)
WHERE NOT EXISTS (SELECT 1 FROM @tables x WHERE x.NazwaTablicy = t.NazwaTablicy);

-- 1. Its subscriptions first: from here on Wapro's triggers write no more change rows for it.
DELETE FROM dbo.WFM_INT_SYSTEM_TABLICE
WHERE Id_Systemu = @id;

-- 2. Its change rows, in each WFM_INT_<table> that exists.
DECLARE @table varchar(100), @sql nvarchar(max);

DECLARE subscribed CURSOR LOCAL FAST_FORWARD FOR
    SELECT NazwaTablicy FROM @tables ORDER BY NazwaTablicy;

OPEN subscribed;
FETCH NEXT FROM subscribed INTO @table;
WHILE @@FETCH_STATUS = 0
BEGIN
    IF OBJECT_ID(N'dbo.' + QUOTENAME(N'WFM_INT_' + @table), N'U') IS NOT NULL
    BEGIN
        SET @sql = N'DELETE FROM dbo.' + QUOTENAME(N'WFM_INT_' + @table) + N' WHERE Id_Systemu = @id;';
        EXEC sys.sp_executesql @sql, N'@id bigint', @id = @id;
    END;

    FETCH NEXT FROM subscribed INTO @table;
END;
CLOSE subscribed;
DEALLOCATE subscribed;

-- 3. The registration itself.
DELETE FROM dbo.WFM_INT_SYSTEM
WHERE Id_Systemu = @id;

COMMIT TRANSACTION;

​

SQL Server login

• SELECT on ARTYKUL, MAGAZYN, CENA and CENA_ARTYKULU, or membership of the db_datareader role (CENA_ARTYKULU holds the price rows; the connector reads it to read prices and to check a price it sends), and
• EXECUTE on dbo.Api_ProductPriceModify. The agent’s connection test checks it (Wapro price procedure installed) and does not pass without it.

• EXECUTE on the order, customer, delivery place and cancel procedures, and on three functions they use;
• INSERT on MIEJSCE_DOSTAWY;
• UPDATE on ZAMOWIENIE_INTERNETOWE_ID and on the free fields POLE1 to POLE10 of customers, orders and order lines, because Wapro saves those fields with dynamic SQL that runs with the caller’s rights;
• SELECT on the order, customer, delivery, country, VAT, currency and payment form tables;
• optionally EXECUTE on Api_CurrencyImport for the exchange rate download.

​

Known limitations

• Omnilinker takes from Wapro the lists above and the product details in the table. Stock is taken into an Omnilinker warehouse only when Wapro manages it; otherwise it is read for comparison. Selling prices are read to compare them with yours, and land in your catalog only on a price level you let Wapro set; categories and bundles are not imported.
• Omnilinker reads back an order’s status, its sale invoices and their KSeF numbers, and only shows them. A change made to the order’s lines in Omnilinker is sent to Wapro after you confirm it, but a change made to the lines in Wapro does not come back to Omnilinker (the next change from Omnilinker is then refused until you check the order), and neither does an order created in Wapro.
• A change to an order does not carry the delivery cost, buyer details, addresses, notes, payments or the status, and a set line (Zestaw) cannot be changed. See Change an order that is in the ERP.
• An order is not sent with a custom or discount line, with lines from more than one warehouse, with more than 150 lines, or as an intra-EU business sale or an export. A cross-border consumer sale (OSS) is sent only with goods at the 23% rate. See What is not sent yet.
• Prices are compared, and imported only on a price level you let Wapro set. Only the price of a product’s main row and of its base unit is read; the same article’s price in another warehouse, another unit or a quantity tier is not.
• Products are read as a complete list, about once a day or when you click Refresh lists, so a change in Wapro shows in Omnilinker after the next list. Stock is faster: normally within a few minutes of the change.
• A product whose index differs only in upper and lower case from another is a separate product in Omnilinker. Their images are shared: both products get the same images.
• Product images kept in Wapro’s image folder (disk mode) are not read, and Wapro’s shop and auction flags on images filter nothing. WMF and EMF images, which Wapro accepts, are not taken.
• A product’s key changes when the article row holding it is deleted outright or its index is emptied, and a new index on only some of a product’s rows can move its link to those rows. Giving rows an index that another product already has joins those rows with that product and can leave a link without a product (see above).

​

Related pages