Postman collection
Items Read

pixiGetItemInfo

Returns master data, stock, supplier, VAT, tag and customs information for one or more items found by item key, EAN, item numbers or an XML list.

Looks up items and returns one row per matching item with its master data.

Input normalisation

  • ItemKey = 0 and empty strings are treated as NULL.
  • If none of ItemKey, ItemNrInt, EANUPC, ItemNrSuppl, ItemXML or InternalItemNumber is set, a single error row is returned instead of item data. LocID alone is not enough.

Search criteria

The scalar parameters and every /ITEMS/ITEM entry of ItemXML form a list of search criteria. Each criterion is matched against pixi.ItemCode:

  • ItemKey / ITEMKEY: item id
  • EANUPC / EAN: code type 1 (EAN)
  • ItemNrInt / ITEMNRINT: code type 2 (internal item number)
  • InternalItemNumber / INTERNALITEMNUMBER: code type 3
  • ItemNrSuppl / ITEMNRSUPPL: code type 4 (supplier item number)

All matches are combined with OR semantics (union): an item is returned if it matches any of the given values. Duplicate matches are removed.

Output values

  • LocID selects location-specific values from ItemLocationSpecific: MinStockQty, Quantity, SafetyStock, TargetStock. Without a location (or without a location record) the global item values are used and SafetyStock/TargetStock are 0.
  • ConsiderFavouriteSupplier = 1 uses the active preferred supplier (AddItems.PreferredSupplier = 1, supplier not disabled) for SupplPrice, SupplNr, ItemNrSuppl, EANUPC and MinOrderQty. With the default 0, the item's own values and the AddItems record of the item's main supplier are used.
  • VATLevel is derived from the VAT rate: 2 = MwSt_Low, 3 = MwSt_Null, any other value = MwSt_High.
  • ItemTAGs lists all tags of the item separated by |. ABC contains only the system tags A, B or C.

The rows are returned without a defined sort order.

Notes

  • All tables are read WITH (NOLOCK); results may contain uncommitted data.
  • The code comment marks ConsiderFavouriteSupplier as "not used anymore", but the code still evaluates it: with 1 the preferred-supplier values are used and MinOrderQty becomes 0 if no active preferred supplier exists.
  • Lookup by ItemKey also goes through pixi.ItemCode. An item without any entry in pixi.ItemCode is not found, even with a valid key.
  • Combining several parameters widens the result (OR), it does not narrow it.
  • In ItemXML the EAN element is named EAN, not EANUPC. Tabs are removed from ITEMKEY. A non-numeric ITEMKEY or malformed XML raises a SQL error.
  • EANUPC is limited to 13 characters.
  • Because of the outer joins (e.g. several code-type-3 entries or several active preferred suppliers), an item can appear more than once in the result.
  • No data is changed; only temporary tables are used.

Tables used

ItemCode · Read AddItems · Read Suppliers · Read TagMatch · Read Tag · Read Items · Read TontrArten · Read ItemLocationSpecific · Read Item_EstimatedDelivery · Read
SQL object:
dbo.pipiGetItemInfo
Updated at 2026-10-30