Lumiya Purchase Order Updates User Guide — SAP

First published on: 03/20/2026/10:42 pm

Overview

Introduction

This document overviews the Lumiya processes for updating approved purchase orders.

The Lumiya, powered by Saltbox, synchronisation process between Lumiya and SAP Business One lets you adjust already synchronised purchase orders.

For example, if users change a purchase order in Lumiya that's already been synced to SAP Business One, the changes will be applied during the next sync.

Purchase Order Updates From Lumiya

Users can modify the purchase order lines within Lumiya, and the changes will be transferred to SAP Business One during the next sync. 

This is for modifying or adding to existing lines only—NOT for removing lines.

Users can edit purchase orders with lines that:

• Haven't been marked as closed for receipting
• Haven't been receipted
• Have been partially receipted

Users can edit the Line fields.

Edited documents are submitted for approval using the Smart Edit button and are given a Submitted status for routing for approval.

Admin users can use specific settings to manage purchase order changes made by creators or approvers.

If admin users want to allow users to modify synced purchase orders in Lumiya, they must enable the "Can Users Recall Created Purchase Orders" company setting and activate the editable field for the Approved stage.

Admin > Business Rules > Editable Fields

To enable the modification of required fields, admin users can select the Editable Fields feature.

E.g., if selected at the 'approved' stage, selected fields can be altered when users open a previously synced purchase order.

The header delivery date can also be edited, but when a line is selected by double-clicking, the editable line fields can also be updated. 

Note: Users should remember to validate any price/tax details when changes are made.

In the example below:

• The item code was changed on the first line
• The quantity was changed on the second line

Users must click on the "Save" button after making changes. 

This saves the changes and sends the document for further approval, and sets the status to 'submitted', if required.

After approval, the modifications will be synced into SAP Business One, and users will see the updated purchase order.

Purchase order updates from SAP Business One

If users modify an already-synced purchase order in SAP Business One that affects the total value, such as changing the quantity, unit price, or adding a new line, the 'UpdateIDocs' user-defined field (UDF) will automatically be marked as "Y" to indicate that Lumiya should be updated.

The example below shows two modifications:

• A new line was added
• The quantity on the second line was changed.

These changes will be updated in Lumiya on the next synchronisation.

After the purchase order goes to "Update" mode, users will notice that the "Y" is displayed in the "UpdateIDocs" user-defined field located on the right-hand side of the purchase order.

To locate the user-defined field, select "User-Defined Fields" under the "View" option on SAP Business One's header toolbar.

Once users update the purchase order and run the synchronisation, the modifications will appear in Lumiya, and the "UpdateIDocs" value field will be updated to "N".

Important Notes

Users should consider these points when processing purchase orders and goods receipt purchase orders in SAP:

• Users must wait for the changes to be synchronised before copying the purchase order into a goods receipt purchase order after updating it.
  • When the value of the “UpdateIDocs” is updated to “N”, the changes are synced, and users can copy the purchase order into a goods receipt purchase order.
• If the goods receipt purchase order differs from the purchase order, the changes must be made to the purchase order first and then be receipted only after the changes are synchronised.
  • If users close the purchase order before the synchronisation is completed, the changes will not be synchronised with Lumiya.
• Users should not remove lines and only add or edit them, as deletions are not synchronised.

Previous

Next