Postman collection
Items Read

pixiGetItemInfoPickList

Returns item master data for one or more items at a location, plus the open pick list lines and packed box quantities for these items and a combined status code.

Looks up one or more items and returns their master data together with information about pick lists and boxes in which they currently appear.

Validation

  • If ItemKey, EANUPC, ItemNrSuppl, ItemNrInt and ItemXML are all empty, the call returns a row with Status = 0 and a message, followed by the final status row 0000. LocID alone is not enough. ItemKey = 0 also counts as empty.

Item lookup

  • A single item is resolved from COALESCE(EANUPC, ItemNrInt, ItemNrSuppl) against the scannable item codes (pixi.ItemCode with a code type where Scannable = 1). The first matching item is used. If ItemKey is passed, it takes precedence over the code lookup.
  • In addition, ItemXML can list several items (/ITEMS/ITEM with child elements ITEMNRINT, ITEMNRSUPPL, ITEMKEY, EAN). Each entry matches items whose internal number, EAN, item key or supplier number equals one of the given values. These items are added to the single item from the parameters.

Result sets on success (in this order)

  1. Item data from items, joined with the location-specific values from ItemLocationSpecific for LocID (stock, minimum stock, minimum order quantity), category name, VAT level, tags, ABC class, estimated delivery and picture links.
  2. Pick list lines: for each item and pick list, the number of non-expired pick list items whose order line is not in status AUS, NLB, RET, STO or EIN. Filtered by the order line location if LocID is set.
  3. Box items: for each item, box and used pick list number, the summed quantity in boxes for order lines with status EIN. Filtered by the order line location if LocID is set.
  4. A status row with a four-digit code: access / item found / on pick list / in box. Possible values are 0000 (no parameter), 1000 (no item data found), 1100, 1101, 1110 and 1111.

Notes

  • The item data result set uses an INNER JOIN on ItemLocationSpecific with LocID = @LocID. If LocID is not passed (NULL), no item rows are returned and the status becomes 1000, although the pick list and box result sets are still filled for all locations.
  • The lookup uses COALESCE, so an empty string in EANUPC (instead of omitting it) prevents the lookup by ItemNrInt or ItemNrSuppl.
  • The XML matching uses OR conditions; one ITEM entry can match several different items.
  • If the same item is listed several times (e.g. via parameter and XML), the pick list and box result sets can contain duplicate rows; the item data set does not.
  • Sum_PickListItem, Sum_BoxItem, PickListNr and BoxNr are wrapped in ISNULL(..., ''); for numeric columns an empty value becomes 0.
  • All reads use NOLOCK, so uncommitted data may be returned. Pick list and box aggregates are computed for all items before they are filtered, which can be slow on large databases.
  • Invalid XML in ItemXML raises a SQL error from sp_xml_preparedocument.

Tables used

items · Read Item_EstimatedDelivery · Read TontrArten · Read ItemLocationSpecific · Read Orderlines · Read PLitem · Read boxitems · Read boxes · Read ItemCode · Read ItemCodeType · Read Tag · Read TagMatch · Read
SQL object:
dbo.pipiGetItemInfoPickList
Updated at 2026-10-30