Postman collection
Direct-Fulfillment Write

pixiDFSetSupplierNotifiedFlag

Sets or clears the notified flag (`ClientNotified`) on the latest `FUT` history entry of the order lines of a direct-fulfillment order or of a single order line.

Marks order lines as notified (or not notified) to the supplier in a direct-fulfillment (drop-shipping) process.

  1. Candidate order lines are selected from Orderlines where OrderlineKey = @OrderlineKey or OrderNr = @OrderNr. Lines with status HAL are excluded.
  2. Each candidate is checked for editability: a line is editable only if it has no entry in OrderHistory whose status is outside HAL, ANG, BES, FUT, NEW. Lines that already have any other history status are skipped.
  3. For every editable line, the OrderHistory entry with the highest OrderHistKey among its entries with status FUT is updated: ClientNotified is set to Y if @IsNotified = 1, otherwise to N.

Lines without a FUT history entry are not changed. The call returns no result set and no status row.

Notes

  • The two filter parameters are combined with OR: if both are passed, lines matching either the order line key or the order number are processed. If neither is passed, nothing is updated.
  • The check IF @IsNotified = NULL never evaluates to true under standard ANSI_NULLS settings. Passing IsNotified explicitly as NULL therefore does not fall back to 1; the flag is set to N. Omit the parameter to get the default 1.
  • Despite the call name, the column written is OrderHistory.ClientNotified.
  • No feedback is given about how many rows were updated (SET NOCOUNT ON, no result set); the caller cannot tell whether a line was skipped as not editable.
  • Candidate selection reads with NOLOCK; the update uses ROWLOCK. No explicit transaction.

Tables used

Orderlines · Read OrderHistory · Write
SQL object:
dbo.pipiDFSetSupplierNotifiedFlag
Updated at 2026-10-30