Mirrors purchase orders placed with a supplier as sales orders in the head office, so head-office-to-store flows are reflected on both sides.
How to use the action
The action runs as a step in a SyncTool configuration. You configure the step's settings (e.g. server, login, path, format or SQL depending on the action) and run the configuration. The action fetches the data it needs from Sapera or the external source itself – you do not map source columns as you would for a regular import. Any parameters are described below.
How the action works
The action mirrors purchase orders placed with head office (where head office acts as the supplier, given by SupplierIdentifier) as sales orders at head office – so the goods flow between store and head office is reflected on both sides.
Each store department is linked to a customer via OrganizationalUnitToCustomerMapping. The sales-order type is chosen with SalesOrderTypeSystemName, and head office's department is given by HeadOfficeOrganizationalUnitDisplayName.
Only new purchase orders since the last run are processed (this is remembered between runs). Direction: creates sales orders in Sapera.
Key parameters
Parameter | Explanation |
HeadOfficeOrganizationalUnitDisplayName | Display name of the head office organizational unit in which the sales orders are created. |
OrganizationalUnitToCustomerMapping | Maps each store organizational unit to a customer identifier, formatted as 'StoreOu1=Customer1;StoreOu2=Customer2'. |
SalesOrderTypeSystemName | Optional system name of the sales order type to use for the created sales orders. |
SupplierIdentifier | Identifier of the supplier whose purchase orders should be mirrored. |
See also the overview SyncTool – actions.
Want to know more?
Read more in these related articles:
Standard parameters for all actions
The general parameters available on most SyncTool actions: step control, error handling, timeout, etc.