Postman collection
Items Read

pixiGetItemBundleDefinition

Returns the component items and quantities of a bundle item, identified by item key, internal item number, EAN/UPC or supplier item number.

Looks up the bundle definition stored in BundleItems for a bundle item and returns one row per component item. Master data for each component comes from Items.

Only one identifier is used. They are checked in this order of priority:

  1. ItemKey, if it is greater than 0.
  2. ItemNrInt, if it is not empty. The first item with this internal item number is used (TOP 1 without a sort order).
  3. EANUPC, if it is not empty. The first item with this EAN/UPC is used (TOP 1 without a sort order).
  4. ItemNrSuppl, if it is not empty. All items with this supplier item number are used. The components of all matching bundles are returned together in one result.

The other parameters are ignored as soon as one with higher priority is set.

The call returns no rows in these cases:

  • no identifier is given
  • the identifier does not match any item
  • the item is not a bundle

In all cases the result set has the same columns. No sort order is applied.

Notes

  • All reads use NOLOCK, so uncommitted data may be returned.
  • If several items share the same ItemNrInt or EANUPC, the item that is used is not deterministic.
  • With ItemNrSuppl the components of different bundles cannot be told apart, because the result has no column for the parent bundle item.
  • The component item data is joined with LEFT JOIN. If a component item no longer exists in Items, its item columns are empty (NULL), while BundleItemKey and Qty are still filled.

Tables used

BundleItems · Read Items · Read
SQL object:
dbo.pipiGetItemBundleDefinition
Updated at 2026-10-30