Postman collection
Suppliers Write

pixiSupplierOrderLineUpdate

Updates the supplier price, estimated delivery date and comment of one supplier order line.

Updates a single supplier order line identified by SupplierOrderLineId. The actual update is delegated to the internal procedure pixi.SupplierOrderLineUpdate, which is called with ReturnUpdatedIds = 1.

Steps:

  1. Opens a transaction, or sets a savepoint if the caller already has an open transaction.
  2. Resolves the user: if UserId is given it is used directly; otherwise the user is looked up by UserName via inf.UserGetByName. If that user name does not exist, the user pixiAdministration is used instead.
  3. Normalises the input values:
    • SupplierPrice: a value that equals an empty string is converted to NULL.
    • EstimatedDeliveryDate: the time part is removed, only the date is passed on.
    • Comment: an empty string is converted to NULL.
  4. Calls pixi.SupplierOrderLineUpdate with the user, the line ID and the three values.
  5. Commits the transaction it opened itself.

If any error occurs, the transaction or savepoint is rolled back and a single row with ReturnCode = ERROR and the SQL error message is returned.

Notes

  • The internal procedure pixi.SupplierOrderLineUpdate is not attached. Which tables it changes, how NULL values are handled (e.g. whether NULL means "leave unchanged") and the exact columns of the success result set (requested via ReturnUpdatedIds = 1) cannot be derived from this code.
  • Pitfall: SupplierPrice is a money value compared with an empty string; SQL Server converts the empty string to 0. A price of 0 is therefore turned into NULL and cannot be set explicitly.
  • Likewise an empty Comment becomes NULL, so it may not be possible to clear a comment with an empty string.
  • EstimatedDeliveryDate is truncated to the date; any time part is discarded.
  • AppName is required but not used by the code. UserName is required but only evaluated when UserId is not supplied.
  • Uses a named transaction or savepoint, so the call can safely run inside an outer transaction; on error only its own work is rolled back (unless the transaction is uncommittable).

Tables used

UCS_USERS · Read
SQL object:
dbo.pipiSupplierOrderLineUpdate
Updated at 2026-10-30